The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
grafana/contribute/backend
Marcus Efraimsson 0b1aec6767
Tracing: Various improvements (#88308)
1 year ago
..
README.md Docs: Update references in `contribute/` dir (#69564) 2 years ago
communication.md Docs: Update backend contribution guidelines (#63034) 2 years ago
database.md
errors.md Сorrection of spelling errors (#83565) 1 year ago
instrumentation.md Tracing: Various improvements (#88308) 1 year ago
package-hierarchy.md
recommended-practices.md Docs: Update backend contribution guidelines (#63034) 2 years ago
services.md Chore: Move backgroundsvcs and usagestatssvcs to registry (#72692) 2 years ago
style-guide.md Сorrection of spelling errors (#83565) 1 year ago
support-bundles.md SupportBundles: Add support bundle documentation (#61855) 2 years ago
upgrading-dependencies.md Chore: Migrate to use buf for protobuf generation (#87407) 1 year ago
upgrading-go-version.md ci: use go.mod as source of truth for actions/setup-go action (#87574) 1 year ago

README.md

Backend

First read the backend style guide to get a sense for how we work to ensure that the Grafana codebase is consistent and accessible. The rest of the backend contributor documentation is more relevant to reviewers and contributors looking to make larger changes.

For anyone reviewing code for Grafana's backend, a basic understanding of content of the following files is expected:

Reviewers who review large changes should additionally make a habit out of familiarizing themselves with the content of /contribute/backend from time to time.

Dependency management

Refer to: