mirror of
https://github.com/healthchecks/healthchecks.git
synced 2026-04-25 23:15:49 +03:00
[GH-ISSUE #55] Feature Request: Logging #32
Labels
No labels
bug
bug
bug
feature
good-first-issue
new integration
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/healthchecks#32
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @stevenmcastano on GitHub (Apr 29, 2016).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/55
I use graylog to capture all of my application logs at the debug level almost and also use it to ensure certain things are still running.
So, for instance, it looks like the "sendalerts" process has failed on my a few time, once or twice I'm not exactly sure why, the other time because the MySQL connection went away while I was doing an upgrade and I didn't notice.
Usually in graylog I would capture all the logs and baseline the rate. So I have health checks pinging a few every minute and the check for alert sending runs basically once every minute which I can see from the
-- MARK 2016-04-29T15:28:36.779584+00:00 --line, I should be able to have graylog send me an alert if the rate of those lines drops below say 8 times in a given 10 minute window.Would it be possible to add a disk logging, syslog, or even better the option to use the python logging module so I could use something like the GELF library or AMPQ GELF library and send logs direct to my local RabbitMQ server?
P.S. Awesome job on the variable in webhooks, I moved that into production today and so far my tests show that it's working perfectly. Now I've got that much LESS email clutter! Thanks!!
@cuu508 commented on GitHub (Aug 13, 2016):
Management commands log to console, and I think it would be nice to keep it simple like that.
You can redirect console output to a file or pipe it into a different program.
For example, if you run sendalerts with supervisord, you can use
stdout_logfilesetting in your supervisor configuration.