Deleting Acknowledgement comments

[Andreas Ericsson]

It would help the debate immensely if you could reply inline. Scrolling 
up and down to find the original text and guess what part of the reply 
is in response to what is a bit tiresome.

Andrew Laden wrote:
> Persistent comments, according to the docs, control if the comment survives
> a nagios restart. This has nothing to do with the comment surviving the Ack
> being cleared. 
>

Umm.. I'm fairly certain that's wrong. I might be mistaken though. I 
rarely dabble with the gui myself.

> 	Speaking of Documentation, I am having trouble finding documentation
> for end users. (ie, how to operate the GUI. What the difference between
> disabling notification, disabling checks, ack'ing a problem, etc. ) You have
> to infer a lot of it from the code. It would be nice to have a "helpdesk"
> level of documentation for the GUI. 
> 

Feel free to write one. Noone else has felt the need to be so great so 
as to want to take the trouble to jot it down and publish it.

> The "if there is only one" is useless without the search feature in front of
> it.

The search feature is there.

> I think the search feature is pretty important. I have hundreds of
> machines. I know that one of them is going to go down, so I want to schedule
> it for downtime (via the gui) Right now, I have to click through screens to
> find the host.

You won't have to do that with Nagios 2.x. I thought I made this clear, 
but perhaps it wasn't clear enough.

> Either look at the very long detail or overview pages, or
> else try to guess what hostgroup it might be in.  Having a place that I could
> just type in the name would be a big help. (I know I can bring up the URL
> and type it in directly, but this isnt user friendly, especially since the
> page is in frames so you cant see the URL.
> 
> What is the ETA on the New GUI? 
> 

As soon as someone feels the need to be so pressing that they can't wait 
longer, they'll hack it up. Ethan has expressed a desire to have this 
new gui in place in 3.0 at the very latest. There's no such thing as ETA 
when no money changes hands, because the people writing the code might 
well go off on a two-year vacation without bothering to finish what they 
were doing at the time. Feel free to contribute though; Money, code or 
hardware is well received.

> 
> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net
> [mailto:nagios-users-admin at lists.sourceforge.net] On Behalf Of Andreas
> Ericsson
> Sent: Thursday, June 16, 2005 1:57 PM
> To: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] Deleting Acknowledgement comments
> 
> Andrew Laden wrote:
> 
>>Can Nagios be automatically set up to delete Comments associated with 
>>Acknowledgements? IE. There is a problem. I ack the problem and 
>>include a comment.
>>
>> The problem goes away. The Ack clears but the comment remains. I'd 
>>like the comment to clear as well, Else I have to go in manually, look 
>>at all the comments, see which ones are on services that are no longer 
>>problems, and clear them manually one at at time.
>> 
> 
> 
> This is called "Persistent Comments" and can be defined through the GUI with
> a checkbox when acking the problem (at least in nagios 2.x, although I'm
> fairly sure this was in 1.x as well).
> 
> 
>>As a side note, for some enhancement requests.
>>1: Ability to apply delete multiple comments from a single web page. 
>>(ie, a checkbox for each comment, and an apply to all button.
>>2: A search field, so I can type in the name of a host, and have 
>>nagios list the hosts, or if there is only one, list the service 
>>details for the one host. Makes it much easier to find hosts.
> 
> 
> The part after the 'or if there is only one' is already implemented in
> Nagios 2.x.
> 
> 
>>3: Combine 1 and 2, so I can search for a set of hosts, and apply a 
>>comment/downtime/etc to all of them. This way, I don't have to set up 
>>hostgroups for every possible combinations of hosts that I would like 
>>to work on.
>>
>>I am running Nagios 1.1
> 
> 
> While these functions are all good and well, the current GUI will be dropped
> for something else entirely. This new GUI will most likely keep comments in
> a database by itself and only let Nagios know of acknowledgements (for
> notification purposes). No new features are planned for the current GUI,
> although patches implementing obviously desirable features are often
> accepted.
> 
> Obviously desirable in this case means that no sane person can have anything
> to object to them, or they are optional and unobtrusive if unused. Patches
> that depend on the mood or opinion of the user are usually ignored.
> 

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null