mirror of
https://github.com/prometheus-community/windows_exporter.git
synced 2026-10-18 10:39:05 +02:00
Jan-Otto Kröpke
018ec75223
kubernetes/ moves to docs/kubernetes/, dashboard/ to contrib/dashboard/, and the rendered Prometheus rules and alerts to contrib/monitoring/ with a README that says how to use and regenerate them. Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de>
26 lines
989 B
Markdown
26 lines
989 B
Markdown
# Prometheus rules for windows_exporter
|
|
|
|
Ready-to-use Prometheus rule files, rendered from the
|
|
[mixin](../mixin/README.md) with its default configuration:
|
|
|
|
- [`windows_rules.yaml`](windows_rules.yaml): recording rules.
|
|
- [`windows_alerts.yaml`](windows_alerts.yaml): alerting rules for the default
|
|
collectors.
|
|
|
|
The alerts build on the recording rules, so load both files:
|
|
|
|
```yaml
|
|
rule_files:
|
|
- /etc/prometheus/rules/windows_rules.yaml
|
|
- /etc/prometheus/rules/windows_alerts.yaml
|
|
```
|
|
|
|
The files expect the exporter under the job name `windows_exporter`. For other
|
|
job names, thresholds, selectors or the alerts of opt-in collectors, render
|
|
the mixin with your own configuration as the
|
|
[mixin README](../mixin/README.md#customize-or-compose) describes. Every alert links
|
|
to its [runbook](https://prometheus-community.github.io/windows_exporter/runbooks/).
|
|
|
|
Do not edit these files by hand: `mise run rules` in `contrib/mixin`
|
|
regenerates them, and CI fails when they are out of date.
|