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
Separating parser plugins from input plugins was a great start.
The new JSON Parser looks good and has flexibility to specify Tags keys.
However during my integration of DeviceHive json messages I found that more options are needed:
Ability to extract MetricName from json message
Ability to extract Timestamp from json message
Choose json object containing metric values
To be clear, here's example of the json message produced by DeviceHive:
Let me know if there is anything I missed in existing parser that would cover that. And if these features would make sense in the overall picture of telegraf.
Another way to handle these kind of issues could be introduction of transformers that would allow to shape/strip data. Kind of how logstash does it.
The text was updated successfully, but these errors were encountered:
This constitutes a large change in how we will parse different data
formats going forward (for the plugins that support it)
This is working off @henrypfhu's changes.
Separating parser plugins from input plugins was a great start.
The new JSON Parser looks good and has flexibility to specify Tags keys.
However during my integration of DeviceHive json messages I found that more options are needed:
To be clear, here's example of the json message produced by DeviceHive:
You can also see my
patch
on a previous version of kafka plugin to handle this format here: 0120940b27a26f59c6005acf8cb329422d912879Let me know if there is anything I missed in existing parser that would cover that. And if these features would make sense in the overall picture of telegraf.
Another way to handle these kind of issues could be introduction of transformers that would allow to shape/strip data. Kind of how logstash does it.
The text was updated successfully, but these errors were encountered: