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
Describe the bug
The metric timestamp always reuses the first timestamp when inserting a label using metrics processor and then selecting the netdev metric after. If label is inserted after metrics_selector it updates the timestamp as expected.
To Reproduce
Minimal config:
service:
flush: 5
daemon: off
log_level: info
pipeline:
inputs:
- name: node_exporter_metrics
tag: metrics.node_metrics
scrape_interval: 10s
metrics: netdev
processors:
metrics:
- name: labels
insert: foo bar
- name: metrics_selector
metric_name: /node_network_(transmit|receive)_bytes_total/
action: include
outputs:
- name: stdout
match: '*'
Bug Report
Describe the bug
The metric timestamp always reuses the first timestamp when inserting a label using metrics processor and then selecting the netdev metric after. If label is inserted after metrics_selector it updates the timestamp as expected.
To Reproduce
Minimal config:
Output:
If we swap the order of "labels" and "metrics_selector" it works as expected:
Output:
Expected behavior
Expect the timestamp to update with every scrape.
Your Environment
The text was updated successfully, but these errors were encountered: