{"action":"created","issue":{"url":"https://api.github.com/repos/firehol/netdata/issues/3599","repository_url":"https://api.github.com/repos/firehol/netdata","labels_url":"https://api.github.com/repos/firehol/netdata/issues/3599/labels{/name}","comments_url":"https://api.github.com/repos/firehol/netdata/issues/3599/comments","events_url":"https://api.github.com/repos/firehol/netdata/issues/3599/events","html_url":"https://github.com/firehol/netdata/pull/3599","id":310852331,"number":3599,"title":"Add syslog support to alarm-notify.sh.","user":{"login":"Ferroin","id":905151,"avatar_url":"https://avatars2.githubusercontent.com/u/905151?v=4","gravatar_id":"","url":"https://api.github.com/users/Ferroin","html_url":"https://github.com/Ferroin","followers_url":"https://api.github.com/users/Ferroin/followers","following_url":"https://api.github.com/users/Ferroin/following{/other_user}","gists_url":"https://api.github.com/users/Ferroin/gists{/gist_id}","starred_url":"https://api.github.com/users/Ferroin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Ferroin/subscriptions","organizations_url":"https://api.github.com/users/Ferroin/orgs","repos_url":"https://api.github.com/users/Ferroin/repos","events_url":"https://api.github.com/users/Ferroin/events{/privacy}","received_events_url":"https://api.github.com/users/Ferroin/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":23,"created_at":"2018-04-03T14:07:44Z","updated_at":"2018-05-10T19:50:32Z","closed_at":"2018-05-10T15:21:54Z","author_association":"CONTRIBUTOR","pull_request":{"url":"https://api.github.com/repos/firehol/netdata/pulls/3599","html_url":"https://github.com/firehol/netdata/pull/3599","diff_url":"https://github.com/firehol/netdata/pull/3599.diff","patch_url":"https://github.com/firehol/netdata/pull/3599.patch"},"body":"This uses the `logger` command (found on all modern Linux and BSD systems)\r\nto allow `alarm-notify.sh` to send netdata alarm messages to a local\r\nor remote syslog server.  By default, logging is done to the local6\r\nfacility at a warning log level, with critical alarms being logged at\r\nthe err level.\r\n\r\nThis provides a mechanism of easily generating a running log of all\r\nnetdata alarm events on most standard UNIX systems, and when used with\r\nfull-featured logging daemons like rsyslog or syslong-ng can be used to\r\narchive such messages in a wide variety of alternative formats.\r\n\r\nThere are a few limitations currently:\r\n\r\n * It can only log to one location.  This can be easily worked around in\r\n most syslog daemon's configurations, as almost all of them support some\r\n form of output multiplexing.\r\n * The default settings will usually not get the results most people\r\n would want, but because of the sometimes very significant differences\r\n in default syslog configurations from distribution to distribution,\r\n there's not really any way to make the defaults any saner.\r\n * While it is possible to log directly to a remote syslog server, there\r\n is no quick and easy set up for this, it requires the user to manually\r\n compose the extra options that need to be passed to `logger`.\r\n\r\nSyslog messages generated by this will look something like this:\r\n\r\n    Apr  3 09:00:30 localhost netdata: Netdata notification on wild-karde at Tue Apr 3 09:00:00 EDT 2018: WARNING, out of disk space time = 5h\r\n\r\nLightly tested on Linux, no testing on BSD yet but based on FreeBSD documentation it should work there as-is.\r\n\r\nAs mentioned in the limitations above, the default settings are almost certainly not what most people will want (depending on the distribution, you'll either get all the notifications in the main syslog log file (`/var/log/syslog` or `/var/log/messages` in most cases), or you won't get any at all), so it won't send messages unless explicitly enabled (which is extra important as the necessary command is present in the default install of all major Linux distributions, as well as FreeBSD and it's derivatives).\r\n\r\nI've been using a custom notification mechanism similar to this for a while now on my VPS nodes so that I have an easy way to correlate netdata alarms with other log entries (for example, making it easier to correlate data collection alarms for my web servers with specific sets of requests).   I've found this to be extremely useful on a couple of occasions, and would much rather not need to go through custom alert notifiers for it, and I expect other people may find it useful too."},"comment":{"url":"https://api.github.com/repos/firehol/netdata/issues/comments/388165421","html_url":"https://github.com/firehol/netdata/pull/3599#issuecomment-388165421","issue_url":"https://api.github.com/repos/firehol/netdata/issues/3599","id":388165421,"user":{"login":"ktsaou","id":2662304,"avatar_url":"https://avatars3.githubusercontent.com/u/2662304?v=4","gravatar_id":"","url":"https://api.github.com/users/ktsaou","html_url":"https://github.com/ktsaou","followers_url":"https://api.github.com/users/ktsaou/followers","following_url":"https://api.github.com/users/ktsaou/following{/other_user}","gists_url":"https://api.github.com/users/ktsaou/gists{/gist_id}","starred_url":"https://api.github.com/users/ktsaou/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ktsaou/subscriptions","organizations_url":"https://api.github.com/users/ktsaou/orgs","repos_url":"https://api.github.com/users/ktsaou/repos","events_url":"https://api.github.com/users/ktsaou/events{/privacy}","received_events_url":"https://api.github.com/users/ktsaou/received_events","type":"User","site_admin":false},"created_at":"2018-05-10T19:50:32Z","updated_at":"2018-05-10T19:50:32Z","author_association":"OWNER","body":"perfect! thank you!"}}
{"actor":{"display_login":"ktsaou"}}