Button for "Put on maintenance immediately"

Bug #305441 reported by macrom
2
Affects Status Importance Assigned to Milestone
Network Administration Visualized
Fix Released
Wishlist
Trond Kandal

Bug Description

Several of our users has requested "i dont bother" button.
What they mean is basicly the option the cancel og ignore alerts. Dont know if this is possible to do, but I promised
to request it.

NAV version : 3.4.4

Revision history for this message
Thomas Adamcik (adamcik) wrote :

Is the idea here that users should be able to flush all pending alerts from alertengine via a button in alertprofile?

Revision history for this message
macrom (a-l-prois) wrote : Re: [Bug 305441] Re: Ignore alert button

On Fri, 5 Dec 2008, Thomas Adamcik wrote:

> Is the idea here that users should be able to flush all pending alerts
> from alertengine via a button in alertprofile?

This is the answer I got (in norsk, hope thats ok) :)

--- snip ---
Jeg tror det er en ignore-knapp for en enkelt alarm vi er på jakt etter.

Typisk bruk:

* En ubetydelig boks stopper og gir alarm
* Lokal IT kopler om brukerne i påvente av ny boks
* Vi sier "ignore" slik at alarmen forsvinner
* Ny boks på plass, alt vel
* Ny alarm på samme boks -> Ny alarm i NAV

Alternativet er at "ignore" knappen setter alarmen i en slag
"OK, vi har sett den og jobber med den" modus.
--- /snip ---

-Asbjørn-

>
> --
> Ignore alert button
> https://bugs.launchpad.net/bugs/305441
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Network Administration Visualized: New
>
> Bug description:
> Several of our users has requested "i dont bother" button.
> What they mean is basicly the option the cancel og ignore alerts. Dont know if this is possible to do, but I promised
> to request it.
>
> NAV version : 3.4.4
>

Revision history for this message
Vidar Faltinsen (faltin-uninett) wrote : Re: Ignore alert button

This sounds very much like maintenance? Put the box on maintenance and all alarms are ignored.
This will then go for all users. Is that what you are looking for? This is an implemented feature.

An alternative could be to in the first place except the given box/set of boxes from your alert profile,
given it is insignificant... or have alarms of this kind be send as email (not sms) or as queued email or...

- Vidar

Revision history for this message
Morten Brekkevold (mbrekkevold) wrote : Re: [Bug 305441] Re: Ignore alert button

> This sounds very much like maintenance? Put the box on maintenance and all alarms are ignored.
> This will then go for all users. Is that what you are looking for? This is an implemented feature.
>
> An alternative could be to in the first place except the given box/set of boxes from your alert profile,
> given it is insignificant... or have alarms of this kind be send as email (not sms) or as queued email or...

As I understand it, MacroM is asking for a feature to allow individual
users to remove alert states from their personal status page, a sort
of "I acknowledge this alert and don't want to see it in my list any
more". It has nothing to do with the actual dispatch of alerts via
email or SMS.

This scenario is not really covered by maintenance either, since
maintenance is a global thing for a NAV installation, which will also
prevent the dispatch of alerts.

Changed in nav:
importance: Undecided → Wishlist
Revision history for this message
macrom (a-l-prois) wrote : Re: Ignore alert button

Here is a new explanation from Kjetil Otter, allso in Norwegian (sorry about that) :)

--- snip ---
Ulempen med å benytte maintainance er at da får vi ikke alarmer på
boksen sålenge maintainence-vinduet varer. Det vi kunne tenke oss er
et slags maintainence-valg som har slutt-tid når boksen kommer
opp igjen. Eller egentlig en ekstra status-verdi som er "i arbeid"
eller noe slik (ikke bare up, down og shadow)

Det betyr at NAV må fortsette å se etter boksen, men ikke skal
gi alarm over at den ikke er der. Og så når NAV finner boksen igjen,
så går alt tilbake til det normale slik at om boksen igjen feiler,
så kommer det en alarm.

Det blir omtrent som følger:
* Boks går ned, status i NAV blir "down"
* Noen trykker på "knappen", status for boksen blir "i arbeid" e.l.
* NAV fortsetter å polle boksen hvert 5. minutter (eller hva det er)
* Når boksen er fikset og NAV ser boksen så settes status til "up"
* Ved senere feil er det tilbake til "down" som status
--- /snip ---

-Asbjørn-

Changed in nav:
assignee: nobody → Trond Kandal (trond-kandal)
Revision history for this message
Morten Brekkevold (mbrekkevold) wrote :

Bug 922793 is more or less a duplicate of this one, and has recently been fixed.

But, I imangine this report describes a feature where one can create the maintenance task directly from the "IP Devices Down" list in the Status page.

Revision history for this message
Morten Brekkevold (mbrekkevold) wrote :

John-Magne, Trond and I have been discussing an implementation for this in the office.

Our suggestion is to add a button to the Status page's "Ip Devices Down" listing. This would automatically create a new maintenance task for the IP device in the same row, with end_time set to "when up again" (or infinity, which is the actual representation of this concept), adding a description template like this: "On maintenance till up again; set from status page by user <loginname>"

One issue that it may take 5 minutes for a maintenance task to take effect, due the the maintengine being run from cron. As user would likely expect the box to disappear immediately from the list for boxes down. This would require some modifications to the maintengine to make its functionality reusable in library form. This way it could be called from a view handler running under the Apache/Django process.

Changed in nav:
status: New → In Progress
Revision history for this message
Morten Brekkevold (mbrekkevold) wrote :
summary: - Ignore alert button
+ Button for "Put on maintenance immediately"
Changed in nav:
status: In Progress → Fix Committed
milestone: none → 3.13.0
Changed in nav:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.