Re: Re-2: [dev] Nagios-filter / Nagios integration

Hi, Stefan Tröndle / EDV:Systemhaus Tröndle schrieb:

Hello together,

I would like to see (and would possibly help developing) an RSS-Add-On to OTRS. It would be possible (as bb suggested) to pass a search template as request-string and get an rss-xml-stream returned which could in turn be displayed by every RSS-reader imaginable. This would solve the need for having a webbrowser open all the time and be platform-independent.

I already posted this feature-request in bugzilla, see http://bugs.otrs.org/show_bug.cgi?id=1582 Perhaps, I could also help developing within the OTRS-API, I don't have know-how on rss-xml-streams. I could supply the ticket-data, if someone else realizes the RSS-perl-stuff. Bye, Alex

Best regards

Stefan Tröndle Dipl.-Inform. (FH) s.troendle@troendle.de

--------------------------------------------- EDV:Systemhaus Tröndle - providing solutions! Marianne Tröndle Josef-Schüttler-Straße 53 78224 Singen

Fon +49 (0)7731 64433 Fax +49 (0)7731 68559 Internet http://www.troendle.de

-------- Original Message -------- Subject: Re: [dev] Nagios-filter / Nagios integration (22-Mrz-2007 15:30) From: Bodo Bauer To: stefan

...

On Thu, 2007-03-22 at 14:51 +0100, Rico Barth wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi OTRS-Team,

based on the recent discussion with bb I want to explain my ideas and codings for an Nagios-Integration in OTRS.

A few months ago I needed a PostMaster-Filter to put nagios messages in a predefined queue. However, this filter does a little more than putting the message in a queue. The filter features are:

- - check mail to see if it's a nagios mail - - check if it's a host or service request - - put mail in defined queue as a ticket - - set configurable freetext fields with host/ip/service... - - whenever there are already tickets for a certain nagios message/incident, following nagios messages for this incident are appended to this ticket as new articles - - if the arriving message is a recovery alert the corresponding ticket is closed - - configuration for nagios filter is developed as sysconfig-xml This pretty much sums up what I am working at right now. :)

I didn't distinguish between host and service requests however. If no service can be identified, service is set to 'Host' (or whatever you configure it to be) and from that point on 'Host' is treated as any other service.

...

To Dos/ideas

A pop-up (or whatever) should be used to inform agents of current nagios incidents without searching for those tickets or accessing the nagios web interface. This little display contains a report something like that:

Host IP Service comment ... ... .... .........

It refreshes every x minutes so IT-service agents have up to date information and may help customers with a first qualified response.

If you are interested in completing or developing the idea or as a first step to create a package out of it, I'm looking forward for your response. If you are interested in the code just contact me. I like the idea of what I would call a real-time-ticket-watcher. I see this as an independent functionality however. Why restrict it to special tickets? Wouldn't it be cooler to select a search template and have all ticket matched by that search to be monitored?

BB -- ((otrs)) :: OTRS GmbH :: Norsk-Data-Strasse 1 :: D - 61352 Bad Homburg Fon: +49 (0) 6172 681988 0 :: Fax: +49 (0) 9421 56818 18 http://www.otrs.com/ :: Communication with success!

Geschäftsführer: André Mindermann, Martin Edenhofer Handelsregister: HRB 9452 Bad Homburg Steuernummer: 003/240/97521

------------------------------------------------------------------------

_______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev