{"action":"created","issue":{"url":"https://api.github.com/repos/influxdata/telegraf/issues/1363","repository_url":"https://api.github.com/repos/influxdata/telegraf","labels_url":"https://api.github.com/repos/influxdata/telegraf/issues/1363/labels{/name}","comments_url":"https://api.github.com/repos/influxdata/telegraf/issues/1363/comments","events_url":"https://api.github.com/repos/influxdata/telegraf/issues/1363/events","html_url":"https://github.com/influxdata/telegraf/issues/1363","id":159673670,"number":1363,"title":"Support JSON Path-like json parsing","user":{"login":"sparrc","id":7155926,"avatar_url":"https://avatars.githubusercontent.com/u/7155926?v=3","gravatar_id":"","url":"https://api.github.com/users/sparrc","html_url":"https://github.com/sparrc","followers_url":"https://api.github.com/users/sparrc/followers","following_url":"https://api.github.com/users/sparrc/following{/other_user}","gists_url":"https://api.github.com/users/sparrc/gists{/gist_id}","starred_url":"https://api.github.com/users/sparrc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sparrc/subscriptions","organizations_url":"https://api.github.com/users/sparrc/orgs","repos_url":"https://api.github.com/users/sparrc/repos","events_url":"https://api.github.com/users/sparrc/events{/privacy}","received_events_url":"https://api.github.com/users/sparrc/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-06-10T16:30:59Z","updated_at":"2016-09-16T16:10:45Z","closed_at":null,"body":"## Feature Request\r\n\r\n### Proposal:\r\n\r\nSupport something similar to JSONPath for customizing which fields/paths of json get picked up as tags/fields/types/etc.\r\n\r\nDoesn'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.\r\n\r\n### Current behavior:\r\n\r\nflattens json into numerical fields only, grabs tags only from the top level.\r\n\r\n### Desired behavior:\r\n\r\nmore customization to deal better with diverse range of different json formats.\r\n\r\n### Use case: [Why is this important (helps with prioritizing requests)]\r\n\r\nTelegraf 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.\r\n"},"comment":{"url":"https://api.github.com/repos/influxdata/telegraf/issues/comments/247641337","html_url":"https://github.com/influxdata/telegraf/issues/1363#issuecomment-247641337","issue_url":"https://api.github.com/repos/influxdata/telegraf/issues/1363","id":247641337,"user":{"login":"fromanator","id":2934948,"avatar_url":"https://avatars.githubusercontent.com/u/2934948?v=3","gravatar_id":"","url":"https://api.github.com/users/fromanator","html_url":"https://github.com/fromanator","followers_url":"https://api.github.com/users/fromanator/followers","following_url":"https://api.github.com/users/fromanator/following{/other_user}","gists_url":"https://api.github.com/users/fromanator/gists{/gist_id}","starred_url":"https://api.github.com/users/fromanator/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fromanator/subscriptions","organizations_url":"https://api.github.com/users/fromanator/orgs","repos_url":"https://api.github.com/users/fromanator/repos","events_url":"https://api.github.com/users/fromanator/events{/privacy}","received_events_url":"https://api.github.com/users/fromanator/received_events","type":"User","site_admin":false},"created_at":"2016-09-16T16:10:44Z","updated_at":"2016-09-16T16:10:44Z","body":"@sparrc response to your question in #1554 :\r\nQ: \"can you talk more about the drawbacks of using line-protocol? This protocol is ideal for working with influxdb and is able to be encoded & decoded much faster than JSON.\"\r\n\r\nA: This is great for use cases where there's not a telegraf instance loading the data to a kafka topic for ingestion, hence it's not trivial to load the data with the influx line protocol. For my specific use case we are getting a stream of syslog lines from and external server. The syslog line is grokked into JSON and loaded into a Kafka topic. Then we have Telegraf read that kafka topic to load the metrics into a metric storage backend (influx, graphite, etc)."}}
{"actor":{"display_login":"fromanator"}}