[INUG-Users] Saving severity set by users

[John Blake]

Then don't "update at Severity" in the rules.



-----Original Message-----
From: users-bounces at netcoolusers.org
[mailto:users-bounces at netcoolusers.org] On Behalf Of Michael Mikhlin
Sent: Wednesday, July 11, 2007 7:34 PM
To: users at netcoolusers.org
Subject: Re: [INUG-Users] Saving severity set by users

My goal is to save severity changed by user.
If an event happens with severity 5 and user changes the severity of
event
to 3,
then, if the event happens again, I don't want to change the severity to
5,
but leave it 3 as was changed by user.

The problem we have is mainly with SSM alerts. We configured almost all
genalarms as risingContinous
or fallingContinous and handle different severities according to lookup
tables in rule files.
The main issue we have is that help desk want to lower the severity of
some
events, but
since they are sent all the time, the severity can't be changed (it is
changed by help desk and then reset when the alarm is sent again from
SSM).

Michael

-----Original Message-----
From: users-bounces at netcoolusers.org
[mailto:users-bounces at netcoolusers.org]
On Behalf Of Jacob Steinberger
Sent: Wednesday, July 11, 2007 11:18 PM
To: users at netcoolusers.org
Subject: Re: [INUG-Users] Saving severity set by users

After reading all the emails, I still am not certain to your goal. If  
you're trying to catch the original severity of the event as its  
inserted into the object server, "new.OriginalSeverity = new.Severity"  
in the new_row automation is enough.

What are you trying to accomplish with @Severity? If you don't want  
anyone to change the severity, how are you going to process generic  
clears and have problem/resolutions? Are you going to make a third  
severity field to store resolved events for deleting? A fourth  
severity field to track user changes?

I am not following your goal.

Jacob


Quoting Michael Mikhlin <m.mikhlin at gmail.com>:

> Hi,
>
> I have the following statement in some of my rule files:
>
> updates(@Severity)
>
>
>
> I tried to modify the default deduplication  and newrow triggers.
>
> I added a new field, called OriginalSeverity and added the row:
>
> new.OriginalSeverity = new.Severity
>
> to newrow trigger.
>
>
>
> And added the following to deduplication trigger:
>
> If (new.Severity <> old.OriginalSeverity)
>
> Then
>
>                 old.Severity = new.Severity
>
>                 old.OriginalSeverity  = new.Severity
>
> else
>
>                 old.Severity = old.Severity
>
> end if
>
>
>
> Anyway, I see that when some event gets deduplicated, the severity is
> changed to event's severity even if it's changed by the user.
>
> After debugging the deduplication trigger I saw that it enters the
"else"
> statement, but somehow the severity is changed anyway.
>
>
>
> Any clues?
>
>
>
>
>
> From: users-bounces at netcoolusers.org
[mailto:users-bounces at netcoolusers.org]
> On Behalf Of Don Wildman
> Sent: Monday, July 09, 2007 7:25 PM
> To: users at netcoolusers.org
> Cc: users at netcoolusers.org; users-bounces at netcoolusers.org
> Subject: Re: [INUG-Users] Saving severity set by users
>
>
>
>
> update at the probe level is a 3.x function designed to modify the
effect
of
> the deduplication.  It is supported in v7, but its effect is overriden
if
> the field is set in the deduplication trigger.  Look at the default
reinsert
> trigger and you will see that Severity has a conditional setting.
Make
your
> alterations there.
>
> You may also need to look at the update trigger if a user tool or
command
> line is used to set Severity.  In that case you probably want the
change
to
> be allowed.
>
> Regards
> Don W
> ___________
> Don Wildman
> Senior Product Manager - Tivoli Netcool/OMNIbus
>
> IBM Software Group, Tivoli - Network Management
> IBM United Kingdom Limited
> email: wildman at uk.ibm.com
> Mobile: +44 (0) 7879 841569  -  Office/DDI: +44 (0) 20 7021 8144  -
T/L:
> 438144  -  ITN: 37438144
>
>
>
>
> "Michael Mikhlin" <m.mikhlin at gmail.com>
> Sent by: users-bounces at netcoolusers.org
>
> 09/07/2007 17:30
>
>
> Please respond to
> users at netcoolusers.org
>
>
> To
>
> <users at netcoolusers.org>
>
>
> cc
>
>
>
> Subject
>
> [INUG-Users] Saving severity set by users
>
>
>
>
>
>
>
>
> Hi all,
> I want to make the following change: when some user manually changes
the
> severity of some event,
> I want to leave this severity unchanged, even after deduplications.
The
only
> exception is when
> event reoccurs with higher severity.
>
> We have Omnibus 7.01, so I thought adding a new field, called
> OriginalSeverity to save the severity
> that was set by rule file, and use triggers to block severity changes,
if
> the severity was manually changed by user (from Webtop).
> The only thing I can't understand is which event should I catch:
reinsert
or
> update?
> If the rule file has a line that instructs to update Severity field,
> shouldn't it trigger the update trigger or only reinsert is triggered?
> And how can I block this change?
>
> Thanks in advance,
> Michael_______________________________________________
> Sent by the netcoolusers.org "users" mailing list
> Post: users at netcoolusers.org
> Unsubscribe: users-unsubscribe at netcoolusers.org
> Search: http://lists.netcoolusers.org/archives/users/
>
>
>
>
>
>   _____
>
>
>
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with
number
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
>
>
>
>
>
>
>
>


_______________________________________________
Sent by the netcoolusers.org "users" mailing list
Post: users at netcoolusers.org
Unsubscribe: users-unsubscribe at netcoolusers.org
Search: http://lists.netcoolusers.org/archives/users/

_______________________________________________
Sent by the netcoolusers.org "users" mailing list
Post: users at netcoolusers.org
Unsubscribe: users-unsubscribe at netcoolusers.org
Search: http://lists.netcoolusers.org/archives/users/