Bug #77796 for Zenoss:

Wed Jun 13 06:17:56 2012 iblair [...] messagelabs.com - Ticket created

In Zenoss 4.x, the Zenoss::Router::Events module does not work. This is because the Zenoss JSON API does not recognise the 'history' parameter for the events_query call (line 41). Please could you update the module to either check the version of Zenoss, or make this parameter optional? I've tried setting it to undef/0/etc, but no difference. Thanks, Ian

Tue Jun 26 23:28:03 2012 patricksbaker [...] gmail.com - Taken

Tue Jun 26 23:33:17 2012 patricksbaker [...] gmail.com - Correspondence added

On Wed Jun 13 06:17:56 2012, iblair wrote:
Show quoted text

> In Zenoss 4.x, the Zenoss::Router::Events module does not work. This
> is because the Zenoss JSON API does not recognise the 'history'
> parameter for the events_query call (line 41).
>
> Please could you update the module to either check the version of
> Zenoss, or make this parameter optional? I've tried setting it to
> undef/0/etc, but no difference.
>
> Thanks,
> Ian

Thanks for the bug report Ian. Given that my organization will be rolling out 4.x soonish, I will be reviewing this module to lay the ground work for the 4.x API integration; with 3.x backwards compatibility. With that said I'm thinking I will be making this a bit less confined and more abstract. Meaning the Zenoss module can be used to construct any known API calls per the Zenoss documentation without it being coded on the Perl side; IE more meta. With that model the burden will be on the implementor of the module to know what the Zenoss API can do.

I'm not sure when I will be getting to this, but it will be sometime soon in the future.

Sincerely,

Patrick

Tue Jun 26 23:33:18 2012 The RT System itself - Status changed from 'new' to 'open'