artin/sourcegraph
1
0
Fork 0
mirror of https://github.com/sourcegraph/sourcegraph.git synced 2026-02-06 15:12:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc/admin/observability/metrics: add FAQ entries (#9617)

Browse Source
This commit is contained in:
Stephen Gutekanst 2020-04-06 17:20:22 -07:00 committed by GitHub
parent 500ff4bb8d
commit eafb0e892c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/admin/observability/metrics.md
View File

@ -101,4 +101,13 @@ automatically while Grafana is running.
More behavior can be controlled with
[environmental variables](https://grafana.com/docs/installation/configuration/).
### FAQ
#### Can I consume Sourcegraph's Prometheus metrics in my own monitoring system (Datadog, New Relic, etc.)?
It is technically possible to consume all of Sourcegraph's Prometheus metrics in any external monitoring system that supports Prometheus scraping (both Datadog and New Relic support this). With that said, we would advise against it because Sourcegraph is a very complex system and defining all of the thresholds and alerting rules that you will need to ensure Sourcegraph is healthy would be tedious and difficult.
One of the primary benefits of using Sourcegraph's builtin Prometheus and Grafana monitoring is that you get builtin dashboards and alerting thresholds out-of-the-box, and as Sourcegraph's internals change with each update you can rest assured the metrics and information you are monitoring is up-to-date.
What we usually see people do instead is either [configure Sourcegraph's Grafana monitoring to send alerts to your own PagerDuty, Slack, email, etc.](alerting.md) or sometimes [query Sourcegraph's monitoring via HTTP to find out what alerts are firing in order to pipe that into your own custom monitoring solution](alerting_custom_consumption.md).