mwcotton wrote:
> I don't think the mapping mechanism can access anything in the events 
> database its business happens before the events database comes into play.
Unfortunately if this is correct, I guess I can't use ZenOSS for traps from 
this device.  The only way to differentiate these events is by information that 
is in the "Details" tab.

Phonegi,
I can't access the variable name directly because it's in an array of tuples 
(provided my Python lingo is appropriate).  Since it's an array and not a tree 
I believe I have to use numeric subscripts.  Here's what zendmd looks like:

Code:
>>> evt=dmd.ZenEventManager.getEventDetailFromStatusOrHistory("DF6BCC0ef44a2fc821fff0d9a")
>>> print evt._details
(('community', 'public'), ('enterprises', '1'), 
('enterprises.19444.6.2.1.1.10', '(1, 2, 826, 0, 1, 1578918, 6, 2, 1, 2, 40, 
213, 16, 1, 698622552)'), ('enterprises.19444.6.2.1.1.11', '(1, 2, 826, 0, 1, 
1578918, 6, 1282, 1, 1, 16, 7, 100, 101, 102, 97, 117, 108, 116, 1, 10, 57, 50, 
56, 56, 53, 53, 55, 49, 52, 52)'), ('enterprises.19444.6.2.1.1.2', 
'BOOMetaSwitchConnSE.16/BOOMetaSwitchSE.default/BOOCallAgentSE.1/BOOSubscriberConfigContainerSE/BOOIndividualLineContainerSE/BOOIndividualLineSE.9288557144'),
 ('enterprises.19444.6.2.1.1.20', '50'), ('enterprises.19444.6.2.1.1.21', '3'), 
('enterprises.19444.6.2.1.1.23', "A problem with the subscriber configuration, 
or the specified Access \nDevice, is preventing a subscriber from making or 
receiving calls.\nSubscriber's Directory Number   = 9285551234\nSignaling type 
(1 - Line, 2 - ISDN PRI, 3 - ISDN BRI, 4 - SIP) = 1\n\n"), 
('enterprises.19444.6.2.1.1.24', 'The subscriber may be configured to use the 
same Access Line as\nan existin
 g subscriber on the same Access Device, or to use an\nAccess Line that is not 
valid on this Access Device.\nIf an additional log is specified for this 
subscriber, this\nwill contain mo'), ('enterprises.19444.6.2.1.1.25', 'The 
subscriber indicated is unable to make or receive phone\ncalls.\n'), 
('enterprises.19444.6.2.1.1.26', 'If an additional log is specified for this 
subscriber, check it\nfor further information about the problem.\nIf the 
problem is related to the Access Line selected for the\nsubscriber, disable the 
subscriber, reconfigure with a valid,\nunused Access Line, and '), 
('enterprises.19444.6.2.1.1.27', ''), ('enterprises.19444.6.2.1.1.28', 
'18446744073709551615'), ('enterprises.19444.6.2.1.1.29', '838926537'), 
('enterprises.19444.6.2.1.1.3', '0'), ('enterprises.19444.6.2.1.1.4', 
'Individual Line'), ('enterprises.19444.6.2.1.1.5', '213'), 
('enterprises.19444.6.2.1.1.50', '214d6807'), ('enterprises.19444.6.2.1.1.51', 
'MeEMS1'), ('enterprises.19444.6.2.1.1.52', '
 172.16.1.34'), ('enterprises.19444.6.2.1.1.53', '1'), 
('enterprises.19444.6.2.1.1.54', 
'c0:4a:73:a3:b7:8d:5b:90:94:01:9d:9a:4f:a3:de:bf'), 
('enterprises.19444.6.2.1.1.55', 'MeCA1'), ('enterprises.19444.6.2.1.1.56', 
'172.16.1.3'), ('enterprises.19444.6.2.1.1.57', '100728832'), 
('enterprises.19444.6.2.1.1.58', 'V6.1.00'), ('enterprises.19444.6.2.1.1.6', 
'Individual Line 9288557144 (c5121.dphone.domain.com, Line 1)'), 
('enterprises.19444.6.2.1.1.7', '/Subscriber Attention Required Maintenance 
List/Individual Line 9288557144 (c5121.dphone.domain.com, Line 1)'), 
('enterprises.19444.6.2.1.1.8', 'Subscribers'), 
('enterprises.19444.6.2.1.1.80', 'Customer business\n\nRobert Jones'), 
('enterprises.19444.6.2.1.1.81', 'None'), ('enterprises.19444.6.2.1.1.82', 
'-2147483648'), ('enterprises.19444.6.2.1.1.83', '0'), 
('enterprises.19444.6.2.1.1.84', '-1430488544'), 
('enterprises.19444.6.2.1.1.9', '40'), ('enterprises.19444.6.2.1.1.90', '1'), 
('sysUpTime', '793323013'), ('sysUpTime.0', '7933
 23013'))
>>> print evt.enterprises.19444.6.2.1.1.23
  File "<stdin>", line 1
    print evt.enterprises.19444.6.2.1.1.23
                              ^
SyntaxError: invalid syntax

[/code]




-------------------- m2f --------------------

Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=35851#35851

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to