-
Notifications
You must be signed in to change notification settings - Fork 348
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
How to troubleshoot "direct" email alerts? #25
Comments
Hi Brian, You've got it right: the OC daemon isn't intended to send the emails (or even alerts) directly. It logs events to the Correlator which condenses multiple events into an single alert that it can send off. The default OC config file includes a directive log to the Correlator, which will be able to send off an email. https://github.com/thinkst/opencanary/blob/master/opencanary/data/settings.json#L57 |
Ok thanks much, I can make email alerts work pretty well with |
Hi, Just looking at OpenCanary, sorry to comment on a closed issue, but email alerts do seem to work from the OC daemon as @braimee was attempting to do.
|
Hi there,
I've got my canary up and running and used the readthedocs PDF to setup authenticated email alerts similar to your example:
At this point, should connection attempts that get logged in
/var/tmp/opencanary.log
send alerts to me? The FTP/telnet/etc. attempts are definitely getting logged, but I wasn't understanding if I also needed Correlator to actually send the alerts, or if the alerts should be sending "direct" now?Thanks,
Brian
The text was updated successfully, but these errors were encountered: