mirror of
https://github.com/sourcegraph/sourcegraph.git
synced 2026-02-06 19:21:50 +00:00
29b2dd8323
To better track latencies and future performance improvements, adding some lightweight observability layer on top of the existing backend implementation. I'm really no prometheus expert, this might be very wrong. I do get somewhat okay looking timing information though. I'd love to get some additional eyes on the monitoring dashboards. ## Test plan Ran monitoring stack locally and verified the graphs show something. |
||
|---|---|---|
| .. | ||
| command | ||
| definitions | ||
| grafanaclient | ||
| monitoring | ||
| .gitattributes | ||
| BUILD.bazel | ||
| CODENOTIFY | ||
| generate_config_test.sh | ||
| go.mod | ||
| go.sum | ||
| main.go | ||
| README.md | ||
Sourcegraph monitoring generator
This page documents usage (running the generator) and development (of the generator itself). For background and feature documentation, see the generator overview. To learn about how to find, add, and use monitoring, see the Sourcegraph observability developer guide.
Usage
From this directory:
go generate ./...
Logging output supports the Sourcegraph log level flags.
Other configuration options can be customized via flags declared in main.go.
Development
The Sourcegraph monitoring generator consists of three components:
- The main program - this is the primary entrypoint to the generator.
- Definitions, defined in the top-level
monitoring/definitionspackage. This is where the all service monitoring definitions lives. If you are editing monitoring, this is probably where you want to look - see the Sourcegraph observability developer guide. - Generator, defined in the nested
monitoring/monitoringpackage package. This is where the API for service monitoring definitions is defined, as well as the generator code that provides its features.
All features and capabilities for developed for the generator should align with the Sourcegraph monitoring pillars.