You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the windows_exporter_metrics plugin, the windows_logical_disk_free_megabytes{volume="C:"} metric seems to stop updating a few minutes after starting fluent-bit. From that moment on, this metric is always reported with the same timestamp. This looks then for example like this (see middle line):
When pushing these metrics to prometheus, it starts rejected them with out of bounds error after some time.
To Reproduce
Use the following configuration:
[SERVICE]
flush 1
daemon Off
log_level trace
log_file C:\fluent-bit\log.txt
parsers_file parsers.conf
plugins_file plugins.conf
http_server Off
http_listen 0.0.0.0
http_port 2020
storage.metrics on
[INPUT]
name windows_exporter_metrics
tag node_metrics
scrape_interval 15
[OUTPUT]
Name file
Match node_metrics
File C:\fluent-bit\metrics.txt
Start fluent-bit and wait a couple of minutes and check the metrics.txt file.
Bug Report
Describe the bug
When using the
windows_exporter_metrics
plugin, thewindows_logical_disk_free_megabytes{volume="C:"}
metric seems to stop updating a few minutes after starting fluent-bit. From that moment on, this metric is always reported with the same timestamp. This looks then for example like this (see middle line):When pushing these metrics to prometheus, it starts rejected them with
out of bounds
error after some time.To Reproduce
Use the following configuration:
Start fluent-bit and wait a couple of minutes and check the
metrics.txt
file.Expected behavior
All metrics have a current timestamp.
Your Environment
The text was updated successfully, but these errors were encountered: