-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add log file for important notifications #1982
Conversation
Can this be made catchable by AlarmBot plugin (maybe publish some kind of event to stream)? This use case fits it like a glove. |
Yes definitely. I planned on creating an event, but wasn't sure how it would be used. |
Yes. |
25b0a2d
to
30c9bd7
Compare
Codecov Report
@@ Coverage Diff @@
## master #1982 +/- ##
==========================================
- Coverage 87.73% 87.63% -0.10%
==========================================
Files 159 159
Lines 12455 12471 +16
Branches 522 545 +23
==========================================
+ Hits 10927 10929 +2
- Misses 1528 1542 +14
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should also send a notification when we detect bitcoin may be eclipsed.
c8fa2cb
to
78efe48
Compare
Done in 78efe48 |
Needs rebase, otherwise LGTM. |
Add a new log file for important notifications that require an action from the node operator. Using a separate log file makes it easier than grepping specific messages from the standard logs, and lets us use a different style of messaging, where we provide more information about what steps to take to resolve the issue. We rely on an event sent to the event stream so that plugins can also pick it up and connect with notification systems (push, messages, mails, etc).
78efe48
to
72ba251
Compare
Rebased |
Add a new log file for important notifications that require an action from the node operator.
Using a separate log file makes it easier than grepping specific messages from the standard logs, and lets us use a different style of messaging, where we provide more information about what steps to take to resolve the issue.
We rely on an event sent to the event stream so that plugins can also pick it up and connect with notification systems (push, messages, mails, etc).