{"action":"created","issue":{"url":"https://api.github.com/repos/influxdata/telegraf/issues/3883","repository_url":"https://api.github.com/repos/influxdata/telegraf","labels_url":"https://api.github.com/repos/influxdata/telegraf/issues/3883/labels{/name}","comments_url":"https://api.github.com/repos/influxdata/telegraf/issues/3883/comments","events_url":"https://api.github.com/repos/influxdata/telegraf/issues/3883/events","html_url":"https://github.com/influxdata/telegraf/issues/3883","id":304707652,"number":3883,"title":"Input to read and parse a file every interval","user":{"login":"mjf","id":54104,"avatar_url":"https://avatars3.githubusercontent.com/u/54104?v=4","gravatar_id":"","url":"https://api.github.com/users/mjf","html_url":"https://github.com/mjf","followers_url":"https://api.github.com/users/mjf/followers","following_url":"https://api.github.com/users/mjf/following{/other_user}","gists_url":"https://api.github.com/users/mjf/gists{/gist_id}","starred_url":"https://api.github.com/users/mjf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mjf/subscriptions","organizations_url":"https://api.github.com/users/mjf/orgs","repos_url":"https://api.github.com/users/mjf/repos","events_url":"https://api.github.com/users/mjf/events{/privacy}","received_events_url":"https://api.github.com/users/mjf/received_events","type":"User","site_admin":false},"labels":[{"id":435014499,"url":"https://api.github.com/repos/influxdata/telegraf/labels/feature%20request","name":"feature request","color":"513cc6","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2018-03-13T10:31:18Z","updated_at":"2018-05-02T21:11:52Z","closed_at":null,"author_association":"NONE","body":"Hello.\r\n\r\nI would like to propose new input plugin to **read and parse** (*Grok*) a file every interval, preferably called `[[inputs.parser]]` (or `[[inputs.reader]]` in case #3479 is planned to be done one day).\r\n\r\n-----\r\n- Also see #3878 for reference and some random thoughts and\r\n- it may have connection to #3479 too."},"comment":{"url":"https://api.github.com/repos/influxdata/telegraf/issues/comments/386122828","html_url":"https://github.com/influxdata/telegraf/issues/3883#issuecomment-386122828","issue_url":"https://api.github.com/repos/influxdata/telegraf/issues/3883","id":386122828,"user":{"login":"danielnelson","id":1048079,"avatar_url":"https://avatars3.githubusercontent.com/u/1048079?v=4","gravatar_id":"","url":"https://api.github.com/users/danielnelson","html_url":"https://github.com/danielnelson","followers_url":"https://api.github.com/users/danielnelson/followers","following_url":"https://api.github.com/users/danielnelson/following{/other_user}","gists_url":"https://api.github.com/users/danielnelson/gists{/gist_id}","starred_url":"https://api.github.com/users/danielnelson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danielnelson/subscriptions","organizations_url":"https://api.github.com/users/danielnelson/orgs","repos_url":"https://api.github.com/users/danielnelson/repos","events_url":"https://api.github.com/users/danielnelson/events{/privacy}","received_events_url":"https://api.github.com/users/danielnelson/received_events","type":"User","site_admin":false},"created_at":"2018-05-02T21:11:52Z","updated_at":"2018-05-02T21:11:52Z","author_association":"CONTRIBUTOR","body":"> In case you would not decide to go the way of merging logparser and tail plugins into single and more general reader (or whatever name you liked)\r\n\r\nMy plan is to merge logparser into tail, we will just have the tail plugin and this separate plugin.  It turns out following a file is tricky, and the library we have been using has some issues, so I want to keep that type of logic out of this plugin.\r\n\r\n> please add the support for the Grok parser to the exec plugin so that people could at least \"somehow\" get their statistics from /proc\r\n\r\nThis is #3479, you will be able to use Grok in any input that has a `data_format` option.\r\n\r\n>> Other changes to the configuration capabilities to reduce config verbosity and normalize the config need to be introduced as separate issues.\r\n>\r\n>OK. But I am not sure whether I understand properly what this means.\r\n\r\nIt sounded like you have some ideas around changes to the general config file syntax, we can open new issues to discuss these but I don't want to tie the idea to this plugin, because it would delay the plugin unnecessarily.\r\n\r\n> Well, then the socket_listener is yet another plugin that needs support for parsers, right?\r\n\r\nIt's in there now"}}
{"actor":{"display_login":"danielnelson"}}