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
This part of codes filters them out. However, I need all data, including those out of period. Whether or drop the metrics out of period should be configurable.
Proposal:
Whether or drop the metrics out of period for aggregators should be configurable.
Current behavior:
drop.
Desired behavior:
I can config drop/not drop in telegraf.conf.
Use case: [Why is this important (helps with prioritizing requests)]
Use telegraf inside data pipeline. (not a sensor)
Some data always come later than the others. Thus the timestamp of that particular kind of data is always before the periodStart. That kind of data is always dropped, which is not supposed to be.
The text was updated successfully, but these errors were encountered:
zhang8473
changed the title
Feature Request: Aggregator is dropping metrics which are out of period. This must be configurable
Feature Request: Aggregator is dropping metrics which are out of period. Whether drop or not should be configurable
Jan 7, 2017
System info:
Telegraf 1.1.0
Feature Request
I wrote a telegraf aggregator to clean my Kafka data. However, some of the metrics are dropped mysteriously. After digging into the code, I found out that
https://github.com/influxdata/telegraf/blob/master/internal/models/running_aggregator.go#L152-L157
This part of codes filters them out. However, I need all data, including those out of period. Whether or drop the metrics out of period should be configurable.
Proposal:
Whether or drop the metrics out of period for aggregators should be configurable.
Current behavior:
drop.
Desired behavior:
I can config drop/not drop in telegraf.conf.
Use case: [Why is this important (helps with prioritizing requests)]
Use telegraf inside data pipeline. (not a sensor)
Some data always come later than the others. Thus the timestamp of that particular kind of data is always before the periodStart. That kind of data is always dropped, which is not supposed to be.
The text was updated successfully, but these errors were encountered: