···11+# Sonar
22+Sonar is an AT Proto Firehose Montioring tool
33+44+Sonar connects to an AT Proto Firehose (either from a PDS or a Relay) following the semantics of `com.atproto.sync.subscribeRepos`.
55+66+Sonar monitors the throughput of events, producing prometheus metrics on the frequency of different kinds of events.
77+88+Sonar additionally walks through repo operations and tracks the frequency of creation/update/deletion of different record collections.
99+1010+Sonar's main use is to provide an operational dashboard of activity on the network, allowing us to view changes in event rate over time and understand what kinds of traffic flow through the firehose over time.
1111+1212+## Running Sonar
1313+1414+To run sonar in Docker locally, you can run: `make sonar-up` from the root of the `indigo` directory.
1515+1616+This will start a sonar instance that connects to the Bluesky-operated Relay firehose at `bsky.network` and will expose metrics at `http://localhost:8345`
1717+1818+Feel free to modify the `docker-compose.yml` in this directory to change any settings via environment variables i.e. to change the firehose host `SONAR_WS_URL` or the listen port `SONAR_PORT`.
1919+2020+## Dashboard
2121+2222+Sonar emits Prometheus metrics which you can scrape and then visualize with the Grafana dashboard (JSON template provided in this directory) shown below:
2323+2424+