That would be great. In the CA NSM Event Console, traps are simple sent
to the console in the raw format, then when you want to create logic,
input into another event, parse the event trap for keywords or character
positions you simple created a logic routine to do all of that. I think
the way Spectrum handles traps and events is good out of the box, but
when you want to go beyond it takes too much in my opinion to customize
events into something meaningful to you.

 

From: Karen Kedda [mailto:[email protected]] 
Sent: Thursday, March 11, 2010 11:23 AM
To: spectrum
Cc: spectrum
Subject: Re: [spectrum] Tracking Event Management - Spectrum

 


Andy,

Some time ago, internally at Aprisma, there was a TrapInventoryTool.pl
script that you could run from the $SPECROOT/SS/CsVendor directory.
When running the script, you put in the OID string you were interested
in reporting on and it would find the OID string in the AlertMap and
list the EventID associated and the EvFormat file and PCause File.  When
Event Rules were added to Spectrum event handling, the script recognized
an Event Rule, but didn't display any information about the rule.  The
reports generated were in .html and .csv format.  Below is a screenshot
of an html report on OID 1.3.6.1.4.1.9.  

I would love to see CA update the TrapInventoryTool to handle
EventRules, EventProcedures, and report on information from the
$SPECROOT/custom/Events directory too.  It would be extremely helpful to
be able to run a report and document event handling, especially the
changes/customizations made.

 


Karen Kedda
Enterprise Monitoring Solutions
Berkley Technology Services LLC
405 Silverside Rd., Suite 205
Wilmington, DE 19809
302.746.2113
[email protected]



From:

Andrew Stein <[email protected]>

To:

"spectrum" <[email protected]>

Date:

03/11/2010 11:52 AM

Subject:

[spectrum] Tracking Event Management - Spectrum

 

________________________________





Something that has alway's given me a problem with any version of
Spectrum is overall event/alarm management. It's bad enough that
everything is controlled by a series of different text files (which is
even more difficult then using a opensource NMS platform) but there is
really nothing that comes with the product to really track/display all
of these related configurations. The new "ECE editor" for me (which
support has told me is not to be trusted) on good day was nothing but
fluff it only shows you the logic for one event at a time and does not
reference the related alertmap files involved. 

For instance... 

You see an new alarm in Spectrum pop up for the first time. There is no
GUI or any kind of interface that traces all the logic behind what
Spectrum did behind the scenes to activate that alarm. You have to
manually figure out what event(s) are coupled to the alarm. What (if any
event rules were in place tied to any number of alarms and/or downstream
events) and then go search for the alermap file to figure out what trap
the device sent to kick the whole thing off to begin with. 

Has anyone out there come up with better way to address this (perhaps
some kind of perl script, VB event management front end...etc)


Thanks for any feedback or suggestions in advance.

Andy Stein

Duke Medicine
Network and System Management Technologies
[email protected]
Office (919) 681-2739
Mobile (919) 402-7627 

*       --To unsubscribe from spectrum, send email to 
[email protected] the body: unsubscribe spectrum [email protected]

*        




*************
CONFIDENTIALITY NOTICE: This e-mail and the transmitted documents
contain private, privileged and confidential information belonging to
the sender. The information therein is solely for the use of the
addressee. If your receipt of this transmission has occurred as the
result of an error, please immediately notify us so we can arrange for
the return of the documents. In such circumstances, you are advised that
you may not disclose, copy, distribute or take any other action in
reliance on the information transmitted.

*       --To unsubscribe from spectrum, send email to [email protected]
with the body: unsubscribe spectrum [email protected] 

-----------------------------------------------------------------
This message may contain DynCorp International Privileged/Proprietary 
information. If this email is not intended for you, and you are not responsible 
for the delivery of this email message to the addressee, do not keep, copy or 
deliver this email message to anyone. Please destroy this email in its entirety 
and notify the sender by reply email. Your cooperation is appreciated. 
-----------------------------------------------------------------

---
To unsubscribe from spectrum, send email to [email protected] with the body: 
unsubscribe spectrum [email protected]

<<image001.gif>>

Reply via email to