sendnrw/windows_exporter
2
0
Fork 0
mirror of https://github.com/prometheus-community/windows_exporter.git synced 2026-10-17 01:59:04 +02:00
Code Issues Packages Projects Releases Wiki Activity

fix: registry, update, file duplicate series, config key and error reporting (#2509)

Browse Source 
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de>
This commit is contained in:
Jan-Otto Kröpke
2026-10-07 17:24:23 +02:00
committed by GitHub
co-authored by Claude Opus 5.5
parent 7b20daa9ac
commit 71b4ba80ed
9 changed files with 259 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/collector.file.md
+4
View File
@@ -15,6 +15,10 @@ Enabled by default? | No
Comma-separated list of file patterns. Each pattern is a glob pattern that can contain `*`, `?`, and `**` (recursive).
See https://github.com/bmatcuk/doublestar#patterns for an extended description of the pattern syntax.
A pattern that matches nothing, including one whose directory does not exist, is not an error. If a directory
cannot be read, for example because access is denied, the walk of that pattern stops and the collector is reported
as failed (`windows_exporter_collector_success{collector="file"} 0`). Metrics of the other patterns are still exported.
## Metrics
| Name | Description | Type | Labels |
docs/collector.registry.md
+4 -4
View File
@@ -24,7 +24,7 @@ of a JSON array of objects. YAML is supported.
> [!CAUTION]
> If you are using a configuration file, the value must be kept as a string.
>
>
> Use a `|-` to keep the value as a string.
#### Example
@@ -93,7 +93,7 @@ JSON:
#### name
Required, unique id for the key group. It is used as the `name` label on
Required, unique ID for the key group. It is used as the `name` label on
`windows_registry_key_success`, to identify the key in logs, and to seed
auto-generated metric names (see [Metric naming](#metric-naming)). Each key must
have a distinct `name`; duplicates are rejected at build time.
@@ -141,8 +141,8 @@ examples.
The combination of metric name and labels must be unique across all configured
keys and values. Two values may deliberately share a `metric` name when their
labels differ (a common way to aggregate the same measurement from several keys).
A true duplicate — the same name *and* identical labels — is dropped and logged at
scrape time.
A true duplicate — the same name *and* identical labels — is rejected at build
time.
##### help