{"action":"created","issue":{"url":"https://api.github.com/repos/logsearch/logsearch-boshrelease/issues/226","repository_url":"https://api.github.com/repos/logsearch/logsearch-boshrelease","labels_url":"https://api.github.com/repos/logsearch/logsearch-boshrelease/issues/226/labels{/name}","comments_url":"https://api.github.com/repos/logsearch/logsearch-boshrelease/issues/226/comments","events_url":"https://api.github.com/repos/logsearch/logsearch-boshrelease/issues/226/events","html_url":"https://github.com/logsearch/logsearch-boshrelease/issues/226","id":149507591,"number":226,"title":"Rename haproxy job","user":{"login":"hannayurkevich","id":13866048,"avatar_url":"https://avatars.githubusercontent.com/u/13866048?v=3","gravatar_id":"","url":"https://api.github.com/users/hannayurkevich","html_url":"https://github.com/hannayurkevich","followers_url":"https://api.github.com/users/hannayurkevich/followers","following_url":"https://api.github.com/users/hannayurkevich/following{/other_user}","gists_url":"https://api.github.com/users/hannayurkevich/gists{/gist_id}","starred_url":"https://api.github.com/users/hannayurkevich/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hannayurkevich/subscriptions","organizations_url":"https://api.github.com/users/hannayurkevich/orgs","repos_url":"https://api.github.com/users/hannayurkevich/repos","events_url":"https://api.github.com/users/hannayurkevich/events{/privacy}","received_events_url":"https://api.github.com/users/hannayurkevich/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2016-04-19T16:07:48Z","updated_at":"2016-04-27T11:35:00Z","closed_at":"2016-04-27T11:35:00Z","body":"Hi guys,\r\n\r\nI think it makes sense to use more specific name for `haproxy` job. Something like e.g. `logsearch-haproxy`. Then use this specific name when parsing logs from the job:\r\n\r\n`if [syslog_program] == \"haproxy\" { ` //  **use more specific name here** \r\n ` <%= File.read('src/logstash-filters/snippets/haproxy.conf').gsub(/^/, '  ') %>`\r\n`}`\r\n(see https://github.com/logsearch/logsearch-boshrelease/blob/develop/src/logsearch-config/src/logstash-filters/default.conf.erb)\r\n\r\nWhy this is a problem? I can explain it on example of our project where we set both **logsearch-boshrelease + logsearch-for-cloudfoundry**. We also have a **haproxy** job.\r\nAnd logs from our **haproxy** are parsed by the code I mentioned above. As the result we have no control on parsing of these logs and unable to customize the rules.\r\n\r\nI think that name **haproxy** is too generic to use it as a discriminating value when defining a special parsing. Please rename the **haproxy** job in your code to make related special parsing more \"specific\"."},"comment":{"url":"https://api.github.com/repos/logsearch/logsearch-boshrelease/issues/comments/215056117","html_url":"https://github.com/logsearch/logsearch-boshrelease/issues/226#issuecomment-215056117","issue_url":"https://api.github.com/repos/logsearch/logsearch-boshrelease/issues/226","id":215056117,"user":{"login":"mrdavidlaing","id":227505,"avatar_url":"https://avatars.githubusercontent.com/u/227505?v=3","gravatar_id":"","url":"https://api.github.com/users/mrdavidlaing","html_url":"https://github.com/mrdavidlaing","followers_url":"https://api.github.com/users/mrdavidlaing/followers","following_url":"https://api.github.com/users/mrdavidlaing/following{/other_user}","gists_url":"https://api.github.com/users/mrdavidlaing/gists{/gist_id}","starred_url":"https://api.github.com/users/mrdavidlaing/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mrdavidlaing/subscriptions","organizations_url":"https://api.github.com/users/mrdavidlaing/orgs","repos_url":"https://api.github.com/users/mrdavidlaing/repos","events_url":"https://api.github.com/users/mrdavidlaing/events{/privacy}","received_events_url":"https://api.github.com/users/mrdavidlaing/received_events","type":"User","site_admin":false},"created_at":"2016-04-27T11:35:00Z","updated_at":"2016-04-27T11:35:00Z","body":"@hannayurkevich - Glad we've reached a point that solves your issue.\r\n\r\nI'll schedule a release to bosh.io for the end of this week."}}