|
|
| Subject: | Zenoss v4 traps visualization on event details |
| Author: | ValeruS |
| Posted: | 2014-01-18 01:56 |
Hi All.
I use zenoss core 4.2.4 on test env.
We have some dev from Liebert. This dev send trap when problem occurs.
Zenoss core v4 received trapt and displayed in format
---------------------------------------------------------------------------------
Resource: Liebert-Dev
Event Class: /Status/Class
Status: Aged
Message: snmp trap lgpEventConditionEntryAdded
Event Management...
agent zentrap
dedupid IP||/Status/Class|3|snmp trap lgpEventConditionEntryAdded
eventClass /Status/Class
eventClassKey lgpEventConditionEntryAdded
eventClassMapping lgpEventConditionEntryAdded
eventGroup trap
eventState Aged
message snmp trap lgpEventConditionEntryAdded
severity 3
summary snmp trap lgpEventConditionEntryAdded
Device State...
count 1
firstTime 2014-01-16 17:22:32
lastTime 2014-01-16 17:22:32
stateChange 2014-01-16 21:23:29
Event Details...
eventClassMapping lgpEventConditionEntryAdded
lgpConditionDescr 1
lgpConditionDescr 3
lgpConditionDescr 6
lgpConditionDescr 1
lgpConditionDescr 4
lgpConditionDescr 1
lgpConditionDescr 476
lgpConditionDescr 1
lgpConditionDescr 42
lgpConditionDescr 3
lgpConditionDescr 2
lgpConditionDescr 1
lgpConditionDescr 23
lgpConditionDescr 1
lgpConditionDescr.3 1
lgpConditionDescr.3 3
lgpConditionDescr.3 6
lgpConditionDescr.3 1
lgpConditionDescr.3 4
...........
lgpConditionId 3
lgpConditionId.3 3
lgpConditionTime 1264999
lgpConditionTime.3 1264999
oid 1.3.6.1.4.1.476.1.42.3.3.0.1
zenoss.device.priority 3
zenoss.device.production_state 1000
----------------------------------------------------------------------
But zenoss core v3 received this trap and displaed in format
----------------------------------------------------------------------------------
Device: Liebert-Dev
Component:
Event Class: /Status/Class
Status: 0
Count: 1
Message: snmp trap lgpEventConditionEntryAdded
Production State: Production
Device Priority: Normal
Hide details
agent zentrap
clearid 737e8da4-8ec2-4875-83b2-121a51bcc630
component
count 1
dedupid IP||/Status/Class||5|Liebert lgpEventConditionEntryAdded : lgpConditionCompressor1LowPressure
DevicePriority 3
eventClassKey lgpEventConditionEntryAdded
manager localhost
message snmp trap lgpEventConditionEntryAdded
monitor localhost
severity 5
summary Liebert lgpEventConditionEntryAdded : lgpConditionCompressor1LowPressure
suppid
Systems
Event Details
lgpConditionDescr (1, 3, 6, 1, 4, 1, 476, 1, 42, 3, 2, 1, 23, 1)
lgpConditionDescr.4 (1, 3, 6, 1, 4, 1, 476, 1, 42, 3, 2, 1, 23, 1)
lgpConditionId 4
lgpConditionId.4 4
lgpConditionTime 104274024
lgpConditionTime.4 104274024
oid 1.3.6.1.4.1.476.1.42.3.3.0.1
----------------------------------------------------------------------------------
Need help for zenoss core v4
I need to consolidate all lgpConditionDescr in OID format
or how to be appear in old zenoss format like zenos v3
Thanks
| Subject: | Do you really need that |
| Author: | Jane Curry |
| Posted: | 2014-01-20 12:30 |
Do you really need that lgpConditionDescr OID string Do you have some clever transform in the lgpEventConditionEntryAdded mapping that translates that lgpConditionDescr OID string (I can't see any other way that you could get useful intelligence out of the lgpConditionDescr OID string).
If so, you will need to cycle around the new format lgpConditionDescr event attributes and create a tuple that matches your old string. In fact, I don't see how you can have multiple, identical event attributes called lgpConditionDescr so I would start with a transform that simply creates a new event attribute, say, mylgpConditionDescr and assign it to lgpConditionDescr, and see if you get one extra attribute or lots like the lgpConditionDescr.
Cheers,
Jane
Email: jane.curry@skills-1st.co.uk Web: https://www.skills-1st.co.uk
| Subject: | In Zenoss v3 |
| Author: | ValeruS |
| Posted: | 2014-01-22 01:32 |
In Zenoss v3 lgpConditionDescr appear in format (1, 3, 6, 1, 4, 1, 476, 1, 42, 3, 2, 1, 23, 1) and we transform in oid format by replacing ", " with "."(dot) and then transform oid2name. In message appear description like "lgpConditionCompressor1LowPressure" . Then its alerting via sms.
Would be better to be possible to do for zenoss v4
| < |
Previous Question on how zenoss handles incoming events(Zenoss on Ubuntu) |
Next graph traffic volume |
> |