There's no real solution for you creating a syntax error which crashes php ;p
Thanks Adam.
Sent from BlueMail
On 11 Aug 2016, 03:50, at 03:50, Laszlo Nemeth laszlo.nemeth@emarsys.com wrote:
Dear Adam,
Thank you for the infos!
I tried the test_alert, and I got this:
o Notifying [pagerduty] NOC Standby Alerting: {"service_key":"5a73c37ca5d44511a1eb3333b1226185"} PHP Parse error: syntax error, unexpected T_SL, expecting ')' in /opt/observium/includes/alerting/pagerduty.inc.php on line 25
This file is that I patched earlier but yesterday when I ran the “svn update” the svn asked me and it looks like I made an user error, the svn saved the new file but wrote the diff between the patched and the original INTO the saved new file. There are some non PHP compatible line in the .php file…. That is why the PHP didn’t run…
Now I deleted this DIFF message from the .inc.php, and the test_alert run and I got the message via Pager Duty.
After that I created again the CPU problem manually, and now it alerted via PD and I see that “Alert notification sent”.
So it looks like if the PD alerting file (or I think any other alerting file) doesn’t run if an alert event would like to use it can lock all of the alering and the status of this alert message never change to ALERT_NOTIFY. Yes I know, don’t touch this files… but may be this locking is a problem because in this case I didn’t receive this alert via email too, so if an alert contact (pagerduty) doesn’t work, any other (email) doesn’t work too!
Thank You!
BR Laszlo
From: observium observium-bounces@observium.org on behalf of Adam Armstrong adama@memetic.org Reply-To: Observium Network Observation System observium@observium.org Date: Wednesday 10 August 2016 at 18:20 To: "observium@observium.org" observium@observium.org Subject: Re: [Observium] alerting problem
Hi Laszlo,
Nothing has changed on the sending of alerts.
You can force sending an alert or recovery notice with ./test_alert.php -a <alert_id>
The alert_id is the id on the page with the alert entry availability graphs (click the cog on the right hand side of the alert table entry)
If you also use -d, you'll get some debugging output.
Thanks, adam.
On 10/08/2016 09:01:50, Laszlo Nemeth laszlo.nemeth@emarsys.com wrote: Hello,
At the morning I was on the 7933 but 2 hours ago I updated to 8039.
I used a CPU alert for my routers. In the older version it is worked, I got the alerts via mail and PagerDuty as I set up.
Now after the upgrade I would like to test the alerting because on 7933 i “pached” the pagerduty.inc.php for more info in the PD message (the default file just send like “something wrong somewhere” :)
So. After the upgrade with the original (nor pached) PD file I would like a test to see how looks out a PD message now. I set a lower value for the CPU alerting (from 50% to 15%) to generate alerting (now the cpu load is 18-25%)
After a few minutes I see in the Alers / Processor that my deviced appear and show that the status is FAILED. It is ok. In the Alert Logging I get the “Checks failed” so it is great.
But. I never get “Alert notification sent” messages. (I get “Alert notification sent” for other events, so the alerting is working for other services).
I see in the Alerts that the router’s status is Failed, Checked 18s Changed 20m 36s, Alerted: never.
What I have to do for send the alerts? Or for the debug?
Thanks
BR Laszlo
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