feat(monitoring): add remoteWrite to Prometheus and Prometheus Agent mode #228
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…monitoring type This is a set of changes that allow the monitoring stack to be configured to send metrics to a remote Prometheus receiver, both with our current Prometheus monitoring type and with a new PrometheusAgent type that deploys a more minimal Prometheus intallation only for scraping and sending metrics. - Add `remoteWrite` section to prometheus' configuration in the scheam, so Prometheus can be set up to send metrics to a remote receiver. - Add prometheusAgent as monitoring type, as an alternative to prometheus+remoteWrite, allowing to have a "minimal" monitoring stack capable of sending metrics to a remote Prometheus receiver. Notice that this mode does not allow for querying the local Prometheus instance (so no local Grafana dashboards) or having local alerting set up. - Add migrations for switching between Prometheus and Prometheus Agent, and to and from `none`. - Update documentation with the new features
- update schema docs with md-gen - update go models
ralgozino
force-pushed
the
feature-prometheus-agent
branch
from
11e2d63
to
f863a40
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Intro
This is a set of changes that allow the monitoring stack to be configured to send metrics to a remote Prometheus receiver, both with our current Prometheus monitoring type and with a new PrometheusAgent type that deploys a more minimal Prometheus installation only for scraping and sending metrics.
Prometheus Agent mode
The Agent mode optimizes Prometheus for the remote write use case. It disables querying, alerting, and local storage, and replaces it with a customized TSDB WAL. Everything else stays the same: scraping logic, service discovery and related configuration. It can be used as a drop-in replacement for Prometheus if you want to just forward your data to a remote Prometheus server or any other Remote-Write-compliant project.
Notice that with Agent mode:
kubectl topand similar won't show resources usage, becauseprometheus-adapterdoes not work with agent mode (it can't query prometheus for the metrics).If any of the previous points is a blocker for a particular use-case, say you want to be able to see resources usage with
kubectl top, you can fallback to the regularprometheusmonitoring type and configure theremoteWritesection setting a low retention to minimise resource usage instead of using theprometheusAgenttype.Changes in this PR
remoteWritesection to prometheus' configuration in the schema, so Prometheus can be set up to send metrics to a remote receiver.none.Refs
fixes https://github.com/sighupio/product-management/issues/484