Different acknowledgement states

[local.coder]

Tomas,

I don't think it will fully meet your needs but also take a look at 
using the ack color changes.

In /share/stylesheets/status.css you can change the displayed color of 
an item once they are acknowledged. By default problems and ack are all 
the same. Change these values and the displayed color will be different 
once an issue has been acknowledged.

While this doesn't meet the multi levels you are looking for it could 
be a good first step while you work on your ticket system integration.

Derrick

.statusHOSTDOWNACK { font-family: arial,serif;  font-size: 8pt;  
background-color: #FF9900; }
.statusHOSTUNREACHABLEACK { font-family: arial,serif;  font-size: 8pt;  
background-color: #F83838; }
.statusBGUNKNOWNACK { font-family: arial,serif;  font-size: 8pt;  
background-color: #FFDA9F; }
.statusBGWARNINGACK { font-family: arial,serif;  font-size: 8pt;  
background-color: #FEFFC1; }
.statusBGCRITICALACK { font-family: arial,serif;  font-size: 8pt;  
background-color: #FFBBBB; }
.statusBGDOWNACK { font-family: arial,serif;  font-size: 8pt;  
background-color: #FFBBBB; }
.statusBGUNREACHABLEACK { font-family: arial,serif;  font-size: 8pt;  
background-color: #FFBBBB; }




Quoting Ethan Galstad <nagios at nagios.org>:

> Tómas Edwardsson wrote:
>> Hi
>>
>> I have a question regarding acknowledgment of service failures. We have
>> service desk employees that monitor service failures and delegate
>> service calls to technicians. The standard way we have is to acknowledge
>> a problem as soon as someone is working on it. We would like to see
>> different (customizable?) acknowledgment levels.
>>
>> Simple flow would be:
>> 1. Service state becoming hard (critical/warning)
>> 2. Service desk flags the service as "spotted" or "awaiting technician"
>> 3. Service desk calls the relevant technician
>> 4. As soon as the technician starts working on the problem he
>> acknowledges the problem as "being worked on"
>>
>> I would love to be able to create a list of different acknowledgement
>> levels that staff can then set on a service.
>>
>> Is this an idea that has been floated before, worked on?
>> Is there an acceptable way of implementing this if we get someone to
>> work on it? (I would like this included in the Nagios source, I hate
>> maintaining patches for every upgrade).
>>
>> - Tómas Edwardsson
>>
>
> This sounds like it might be easier to implement by integration Nagios
> with a helpdesk/trouble ticket application.  (1) A new service problem
> in Nagios generates a new ticket, (2) the first action in the ticket
> system sends and acknowledgment to Nagios and (3) further actions to the
> problem are tracked in the ticket system.
>
>
>
> Ethan Galstad
> Nagios Developer
> ___
> Email: nagios at nagios.org
> Web:   www.nagios.org
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Nagios-devel mailing list
> Nagios-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-devel
>



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/