I have been unable to make any headway on this with the CE.
I have exactly the same behaviour on a second CE (Observium Community Edition 0.16.1.7533) server in my lab. Clean install, no modifications, simple config:
<?php
## Check http://www.observium.org/docs/config_options/ for documentation of possible settings
// Database config --- This MUST be configured $config['db_extension'] = 'mysqli'; $config['db_host'] = 'localhost'; $config['db_user'] = 'observium'; $config['db_pass'] = ‘XXXXXXXXX'; $config['db_name'] = 'observium';
// Base directory #$config['install_dir'] = "/opt/observium";
// Default community list to use when adding/discovering $config['snmp']['community'] = array("public");
// Authentication Model $config['auth_mechanism'] = "mysql"; // default, other options: ldap, http-auth, please see documentation for config help
// Enable alerter (not available in CE) // $config['poller-wrapper']['alerter'] = TRUE;
// Set up a default alerter (email to a single address) $config['email']['default'] = "dan@horth.com.au"; $config['email']['from'] = "Observium observium@lab.local"; $config['email']['default_only'] = TRUE;
$config['fping'] = "/sbin/fping";
// End config.php
Even adding $config['alerts']['interval'] = 86400; has no effect.
The lab setup is a Centos 7 core server
Dev box (the one that first started spamming me) is RHEL 6
Am going to get the subscription edition set up in my lab to see if that makes a difference.
Thanks
On 21 Jul 2016, at 10:17 AM, Daniel Horth dan@horth.com.au wrote:
Nope, I inherited this setup so have altered nothing :)
But - checking config.php there is no $config['alerts']['interval’] setting - which is surely not a good thing.
Changing now to see if that helps.
On 21 Jul 2016, at 10:09 AM, Michael obslist@smarsz.com wrote:
Have you altered the default value in config.php for the following
$config['alerts']['interval'] = 86400;
That is the value for time between resending an alert notification if there is no status change. Default is 24hr.
Michael
On 21 July 2016 10:01:19 am AEST, Daniel Horth dan@horth.com.au wrote:
The spam from Observium is ongoing. :(
It’s not just this alert checker - any failed one causes repeated notifications
Can someone confirm my assumption that an alert notification should only be sent when the alert status changes - not each time the polling cycle runs.
In the mean time I’m going to have a dig through the code to work out what is triggering the notifications and why the spam.
Thanks
On 19 Jul 2016, at 5:38 PM, Daniel Horth dan@horth.com.au wrote:
If it helps I can send sample DB data for that device_id when back at
work tomorrow
On 19 Jul 2016, at 5:33 PM, Daniel Horth <dan@horth.com.au
mailto:dan@horth.com.au> wrote:
yes - has a timestamp in it
Interface shows last alerted time also, e.g.:
https://www.dropbox.com/s/ldmradc2plzsekd/Screenshot%202016-07-19%2010.43.20... https://www.dropbox.com/s/ldmradc2plzsekd/Screenshot%202016-07-19%2010.43.20.png?dl=0
On 19 Jul 2016, at 4:54 PM, Adam Armstrong <adama@memetic.org
mailto:adama@memetic.org> wrote:
Is the last_alerted field set in the database?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 19 Jul 2016, at 02:36, Daniel Horth <dan@horth.com.au
mailto:dan@horth.com.au> wrote:
Hi all
I have an odd alerting issue where I am receiving email alerts
about a failed check each time a polling interval passes.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium