sourcegraph/monitoring
Erik Seliger 58fe87f6b5
enterprise: Move last directory out (#57392)
This is the end of the PR train to remove the enterprise directory from out repo since we have consolidated to use a single license.

Bye rough code split :)
2023-10-05 20:15:40 +00:00
..
command bazel: introduce build files for Go (#46770) 2023-01-23 14:00:01 +01:00
definitions enterprise: Move last directory out (#57392) 2023-10-05 20:15:40 +00:00
grafanaclient bazel: introduce build files for Go (#46770) 2023-01-23 14:00:01 +01:00
monitoring sg: ease transition to bazel handled go:generate (#55200) 2023-08-14 23:17:25 +02:00
.gitattributes Add missing .gitattributes files for various generated files (#30092) 2022-01-25 16:36:21 +05:30
BUILD.bazel bzl: fix ownership of generated monitoring config (#57380) 2023-10-05 16:08:08 +02:00
CODENOTIFY codenotify: dr. fritz is kil (#57313) 2023-10-03 16:19:55 +00:00
generate_config_test.sh shell: /bin/bash -> /usr/bin/env bash (#53000) 2023-06-06 13:51:55 +01:00
go.mod chore: Run go mod tidy in monitoring dir (#57208) 2023-09-29 20:46:27 +00:00
go.sum chore: Run go mod tidy in monitoring dir (#57208) 2023-09-29 20:46:27 +00:00
main.go bazel: monitoring docs gen (#54965) 2023-07-19 12:20:24 +00:00
README.md Update handbook links in doc (#26848) 2021-11-02 00:09:49 +08:00

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:

All features and capabilities for developed for the generator should align with the Sourcegraph monitoring pillars.