Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disk free metric of windows_exporter_metrics stops updating #7493

Closed
HerrBlauwasser opened this issue May 29, 2023 · 1 comment · Fixed by #7495
Closed

Disk free metric of windows_exporter_metrics stops updating #7493

HerrBlauwasser opened this issue May 29, 2023 · 1 comment · Fixed by #7495

Comments

@HerrBlauwasser
Copy link

Bug Report

Describe the bug

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):

[...]
2023-05-29T10:05:49.084438000Z windows_logical_disk_read_seconds_total{volume="HarddiskVolume1"} = 1.3329828349090552e+17
2023-05-29T10:05:49.084438000Z windows_logical_disk_write_seconds_total{volume="C:"} = 1.3329828349090552e+17
2023-05-29T10:05:49.084438000Z windows_logical_disk_write_seconds_total{volume="HarddiskVolume1"} = 1.3329828349090552e+17
2023-05-29T06:59:49.177702100Z windows_logical_disk_free_megabytes{volume="C:"} = 89258
2023-05-29T10:05:49.084438000Z windows_logical_disk_free_megabytes{volume="HarddiskVolume1"} = 130
2023-05-29T10:05:49.084438000Z windows_logical_disk_idle_seconds_total{volume="C:"} = 1.3329828349090552e+17
2023-05-29T10:05:49.084438000Z windows_logical_disk_idle_seconds_total{volume="HarddiskVolume1"} = 1.3329828349090552e+17
[...]

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.

PS C:\fluent-bit> .\bin\fluent-bit.exe -c .\conf\fluent-bit.conf

Expected behavior
All metrics have a current timestamp.

Your Environment

  • Version used: fluent-bit-2.1.4-win64.exe (same for 2.1.0)
  • Configuration: See above
  • Server type and version: Virtualbox 6.1 on Ubuntu 22.04.2 LTS
  • Operating System and version: Windows Server 2019, latest patches applied
  • Filters and plugins: windows_exporter_metrics,
@HerrBlauwasser
Copy link
Author

I could reproduce the issue on the following configurations using fluent-bit 2.1.4 (64bit):

  • Windows 10 Pro running on Virtualbox 6.1 on Ubuntu 22.04.2 LTS
  • Windows 11 (22H2, latest patches applied) running on ThinkPad E14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants