Docker Compose(metrics): Metric Ingestion via Labels #49
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.
Added support for ingesting metrics and controlling the behavior of their ingestion through labels.
The following docker compose service labels are supported:
Metrics
The following service labels are supported for gathering of metrics for docker compose services:
metrics.agent.grafana.com/scrape
or
prometheus.io/scrape
true
).metrics.agent.grafana.com/scheme
or
prometheus.io/scheme
http
, only supporthttp
now.metrics.agent.grafana.com/path
or
prometheus.io/path
/metrics
, this can be specified as a single value which would override, the scrape path being used for all ports attached to the targetmetrics.agent.grafana.com/port
or
prometheus.io/port
port
to scrape is the target port, this can be specified as a single value which would override the scrape port being used for all ports attached to the target, note that even if an target had multiple targets, the relabel_config targets are deduped before scrapingmetrics.agent.grafana.com/tenant
metrics.agent.grafana.com/job
or
prometheus.io/job
...{job="integrations/kubernetes/cadvisor"...}
or...{job="minio-job"...}
setting this annotation to that value will allow the provided asset to work out of the box.metrics.agent.grafana.com/interval
or
prometheus.io/interval
15s
, this can be override.metrics.agent.grafana.com/timeout
or
prometheus.io/timeout
10s
, this can be override.Logs
See: #47