mirror of
https://github.com/prometheus/prometheus.git
synced 2024-12-26 22:19:40 -08:00
371ca9ff46
There is certainly a potential to add more of these. This is mostly meant to introduce the concept and cover a few critical parts. Signed-off-by: beorn7 <beorn@grafana.com>
32 lines
1.3 KiB
Plaintext
32 lines
1.3 KiB
Plaintext
{
|
|
_config+:: {
|
|
// prometheusSelector is inserted as part of the label selector in
|
|
// PromQL queries to identify metrics collected from Prometheus
|
|
// servers.
|
|
prometheusSelector: 'job="prometheus"',
|
|
|
|
// prometheusHAGroupLabels is a string with comma-separated labels
|
|
// that are common labels of instances belonging to the same
|
|
// high-availability group of Prometheus servers, i.e. identically
|
|
// configured Prometheus servers. Include not only enough labels
|
|
// to identify the members of the HA group, but also all common
|
|
// labels you want to keep for resulting HA-group-level alerts.
|
|
//
|
|
// If this is set to an empty string, no HA-related alerts are applied.
|
|
prometheusHAGroupLabels: '',
|
|
|
|
// prometheusName is inserted into annotations to name the Prometheus
|
|
// instance affected by the alert.
|
|
prometheusName: '{{$labels.instance}}',
|
|
// If you run Prometheus on Kubernetes with the Prometheus
|
|
// Operator, you can make use of the configured target labels for
|
|
// nicer naming:
|
|
// prometheusNameTemplate: '{{$labels.namespace}}/{{$labels.pod}}'
|
|
|
|
// prometheusHAGroupName is inserted into annotations to name an
|
|
// HA group. All labels used here must also be present in
|
|
// prometheusHAGroupLabels above.
|
|
prometheusHAGroupName: '{{$labels.job}}',
|
|
},
|
|
}
|