Feature Request
Proposal:
Support something similar to JSONPath for customizing which fields/paths of json get picked up as tags/fields/types/etc.
Doesn't need to be JSONPath specifically, since TBH the official json path spec is fairly ugly. Something more simple like https://github.com/jmoiron/jsonq would work as well.
Current behavior:
flattens json into numerical fields only, grabs tags only from the top level.
Desired behavior:
more customization to deal better with diverse range of different json formats.
Use case: [Why is this important (helps with prioritizing requests)]
Telegraf frequently gets issues opened for users who want specific changes & modifications to the json parser for their particular use-case. These cannot all be satisfied without a truly generic solution.
Feature Request
Proposal:
Support something similar to JSONPath for customizing which fields/paths of json get picked up as tags/fields/types/etc.
Doesn't need to be JSONPath specifically, since TBH the official json path spec is fairly ugly. Something more simple like https://github.com/jmoiron/jsonq would work as well.
Current behavior:
flattens json into numerical fields only, grabs tags only from the top level.
Desired behavior:
more customization to deal better with diverse range of different json formats.
Use case: [Why is this important (helps with prioritizing requests)]
Telegraf frequently gets issues opened for users who want specific changes & modifications to the json parser for their particular use-case. These cannot all be satisfied without a truly generic solution.