| Summary | NAGIOS Integration |
| Queue | Nic |
| Type | Enhancement |
| State | No Feedback |
| Priority | 2. Medium |
| Owners | |
| Requester | jrestivo (at) unitedforensics (dot) com |
| Created | 04/16/2006 (7147 days ago) |
| Due | |
| Updated | 11/15/2006 (6934 days ago) |
| Assigned | |
| Resolved | 11/15/2006 (6934 days ago) |
| Milestone | |
| Patch | No |
install locally to play with, and I have a few questions:
- what version of Nagios are you using/do you expect integration with?
- you say "full Nagios funtionality is required". The CGIs for Nagios
provide a _very_ broad range of options and data. Any chance you can
narrow things down a bit?
If we can narrow the scope a little bit, I still might be able to make
the timeline you mentioned. If not, it can stay around as a todo, but
I'll have to pass on the bounty.
feasible. I should be able to give you a yes/no and what I think the
basic requirements would be (if yes) in a few days or so.
However, if you look at the nagios code and feel that a working horde
module is possible within 4-5 weeks (ie, by May 23), then I'm
interested in moving forward and willing to provide a downpayment of
$250 toward the work.
State ⇒ Feedback
complex, or do you mean by a certain timeline? If so, what's the
timeline?
implementation of the FR.
Priority ⇒ 2. Medium
Type ⇒ Enhancement
Summary ⇒ NAGIOS Integration
Queue ⇒ Nic
State ⇒ New
as part of Nic or as a module of its own. They're currently moving
toward a php-based environment which should make horde integration
somehwat easier. Full Nagios functionality is required.
Ideally, no changes would be necessary to the nagios code, ensuring
flexibility in upgrades or feature implementation. Rather, the
horde/nagios module would be a wrapper system that calls nagios
scripts directly and shoehorns the returned html to fit cleanly within
the horde environment.