Using API to pull all triggers over last 24hrs

[obrienmd]

I'm attempting to build a script which will automatically e-mail all Zabbix triggers over the last 24 hours to a predefined group (IE: hosts going up/down, etc, etc). We already have immediate e-mail from the Zabbix interface to predefined groups upon important triggers.

It seems that what I 'get' 'trigger' items using the API, I don't actually get trigger "events", I just get a list of triggers that are available. Is there a different object I can use to grab an array w/ all instances of trigger events, and associated data (host, status, etc, etc, etc)?

Thanks!

[nelsonab]

Try the events class. I haven't managed to work with it much yet but I think it might get you closer to where you want to go.

A few things to note, keep track of the API version number, Right now when the number increases expect your code to break until things settle out. :-) Also be sure to submit bugs when you find them.

If you want I can prioritize adding it to my base API library.

[obrienmd]

I'm using the PHP class for the API - I will keep an eye out for changes, though.

Will try to work with the events class, and let you know how it works out... hopefully in the next hour or two

[obrienmd]

OK, when I use the following code after loading the PHP library:
ZabbixAPI::fetch_array('event','get',array())

And print_r the results, I get "Array ( [0] => )"

The execution time of the fetch_array is LONG, and CPU is pegged.

[nelsonab]

That looks like a bug to me!

[obrienmd]

Best place to post bug? I've added in php class dev's original blog post, and Zabbix forum thread.

[nelsonab]

https://support.zabbix.com

I don't think it's a bug with the API interface, but with the API itself.

[obrienmd]

Posted bug: https://support.zabbix.com/browse/ZBX-2732

Please let me know if you think there's any more relevant info I need to put in there!

[nelsonab]

Looks to be about the right minimum. I have a hunch there's a loop in the API code or other race condition preventing it from returning.

[obrienmd]

Would you be interested in adding a comment to the linked ticket with your thoughts?

[obrienmd]

Ticket was closed, stating 1.8.3 fixed this, but I upgraded to 1.8.3 (built from source) and the problem persisted. Script returned same result fairly quickly, but the apache process pegged the CPU until PHP maximum execution time had been reached.

[nelsonab]

If you did download the latest trunk and the bug still exists then I'd reopen the ticket. However if you downloaded the nightly build then it's likely the fix hasn't made it in. In my experience the team is pretty good at fixing the pretty straight forward bugs when someone draws attention to them, and I'm willing to bet this was a straight forward bug. As for arrays vs hashes... well that's another story... :-)

[obrienmd]

Hrm, will pull trunk later today and try again.

[obrienmd]

Latest trunk wouldn't build for me, but I'm running this build (latest nightly 1.8.3):

Zabbix Server v1.8.3 (revision 13392) (29 March 2010)
Compilation time: Jul 21 2010 09:35:53

[obrienmd]

Hrm, so ticket was closed, closer noted that fix was not in trunk, but in dev branch... I was able to checkout/build most branches, but dev branch is a mystery to me... any tips on how to apply patches / merge the api work in dev that addresses this?