6 Replies Latest reply on Dec 2, 2009 9:01 AM by byrona

    sysname variable in trap alerts

      I see this in a few posts but I ddin't see an "official" answer. Is there a way for the server to lookup the Sysname of the source of a trap that is already in the Nodes table? That way in my alerting email I can use the SysName that matches the source of the trap. 


        • Re: sysname variable in trap alerts

          I have been waiting patiently for this app to allow the same level of functionality as the syslog viewer.  The syslog viewer makes up for a lot by being able to both do message tylpe variables as well as key word variables in the message content.


          Unfortunately the trap viewer has neither capability. Without which it really doesn’t have a lot of value.Neither application will recognize IP addresses of existing nodes within Orion and allow custom alerts utilizing the node variables used within the performance monitor.


          It would be nice to see these items get some attention. I know they are working hard to pull the suite together lets hope these are on the list.
            • Re: sysname variable in trap alerts

               Ah the sound of silence.... Sigh I was half hoping to get zinged for not knowing about some forth coming developments that would resolve these issues..

                • Re: sysname variable in trap alerts

                   I think what you're asking for are more variables in Syslog and Traps.  Our roadmap has work on both Syslog and Trap alerts to make them more like Advanced Alerts, but I don't have a timeline yet.

                    • Re: sysname variable in trap alerts

                      I'd like to see this too.  The alerting to the log file would be much more useful if I could fashion the file with only specific information from the trap.   The whole message regurgitated into the log makes parsing difficult. 

                      • Re: sysname variable in trap alerts

                        When we will see some movement on this request?  Trap alerts are messy.  Here's what I would like:

                        1) No separate traps alert configuration - put them in the Advanced alerts.  Ditto for Syslog events.  Three separate alert consoles is dumb.

                        2) Full set of macros so we can get ${Nodes.Caption}, special properties, etc.  Today I have to manually create host records for approx 1000 network devices in Active Directory just so Orion can populate ${Hostname} on a trap alert.  This is silly since the Traps table already has the NodeID.

                        3) Ability to reference individual VARBINDS records using the index field so I can avoid clutter created by the vendor.  Usually the useful content is in 1-3 of the VARBINDS records.  Or better yet, let us define a trap template for our devices along with the mapping to OIDs so we can stop storing denormalized raw VARBINDS data.  This would also allow us to discard unnecessary data and keep the TRAP table size under better control.

                        4) Some self monitoring/alerting by Orion when trap service fails or is getting overloaded.  I realize I can do my own independent monitoring for trap warnings in the window event log but I think the monitoring tool should provide some built in proactive information for the administrator.

                        5) Expand the Trigger Threshold to include the entity in VARBIND records.  If you have a device with multiple components, say fans or drives then you really want to fire traps based on IP-Drive ID or IP-Fan ID not just IP.  You naturally need to monitor the more complex and expensive equipment and these have many components.  In our shop, one storage raid head contains 125 individually monitored components.