{"action":"created","issue":{"url":"https://api.github.com/repos/scalyr/scalyr-agent-2/issues/24","labels_url":"https://api.github.com/repos/scalyr/scalyr-agent-2/issues/24/labels{/name}","comments_url":"https://api.github.com/repos/scalyr/scalyr-agent-2/issues/24/comments","events_url":"https://api.github.com/repos/scalyr/scalyr-agent-2/issues/24/events","html_url":"https://github.com/scalyr/scalyr-agent-2/issues/24","id":68850770,"number":24,"title":"Use different parser for syslog monitor","user":{"login":"czerwingithub","id":2567051,"avatar_url":"https://avatars.githubusercontent.com/u/2567051?v=3","gravatar_id":"","url":"https://api.github.com/users/czerwingithub","html_url":"https://github.com/czerwingithub","followers_url":"https://api.github.com/users/czerwingithub/followers","following_url":"https://api.github.com/users/czerwingithub/following{/other_user}","gists_url":"https://api.github.com/users/czerwingithub/gists{/gist_id}","starred_url":"https://api.github.com/users/czerwingithub/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/czerwingithub/subscriptions","organizations_url":"https://api.github.com/users/czerwingithub/orgs","repos_url":"https://api.github.com/users/czerwingithub/repos","events_url":"https://api.github.com/users/czerwingithub/events{/privacy}","received_events_url":"https://api.github.com/users/czerwingithub/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2015-04-16T05:46:57Z","updated_at":"2015-04-21T23:51:12Z","closed_at":"2015-04-16T06:29:04Z","body":"Right now, the parser for the syslog monitor's log is \"systemLog\".  Let's change this to something unique just for the syslog monitor so that we can change it how it is parsed server side in Scalyr.  Let's just change it to \"syslogServer\""},"comment":{"url":"https://api.github.com/repos/scalyr/scalyr-agent-2/issues/comments/94976503","html_url":"https://github.com/scalyr/scalyr-agent-2/issues/24#issuecomment-94976503","issue_url":"https://api.github.com/repos/scalyr/scalyr-agent-2/issues/24","id":94976503,"user":{"login":"steve-scalyr","id":1100154,"avatar_url":"https://avatars.githubusercontent.com/u/1100154?v=3","gravatar_id":"","url":"https://api.github.com/users/steve-scalyr","html_url":"https://github.com/steve-scalyr","followers_url":"https://api.github.com/users/steve-scalyr/followers","following_url":"https://api.github.com/users/steve-scalyr/following{/other_user}","gists_url":"https://api.github.com/users/steve-scalyr/gists{/gist_id}","starred_url":"https://api.github.com/users/steve-scalyr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/steve-scalyr/subscriptions","organizations_url":"https://api.github.com/users/steve-scalyr/orgs","repos_url":"https://api.github.com/users/steve-scalyr/repos","events_url":"https://api.github.com/users/steve-scalyr/events{/privacy}","received_events_url":"https://api.github.com/users/steve-scalyr/received_events","type":"User","site_admin":false},"created_at":"2015-04-21T23:51:12Z","updated_at":"2015-04-21T23:51:12Z","body":"One advantage of client-based configuration is that you can do it as part\nof the same process you're using to provision / deploy / configure the rest\nof the software on that client. If we move to server-based configuration,\nwe'll need to preserve some way of driving the configuration from the\nclient (perhaps via an API). A few scenarios to consider:\n\n1. Already today, I believe we have customers using Scalyr on auto-scaling\nserver pools. Their server template includes an agent configuration file,\nso when the autoscaler adds a new server, it comes up already configured\nand reporting data.\n\n2. A user might use Chef or Puppet or whatever to add or remove an\napplication from a server. They'll likely want to update the agent\nconfiguration at the same time. Chef or Puppet can easily add or remove a\nmodular configuration file to do this.\n\nSteve\n"}}