SolarWinds seems to get a fair amount of love here whenever someone asks about monitoring solutions. I started at a medium sized company with an existing SolarWinds install (less than 1000 nodes). I didn't see any obvious way to bring snmptrap or syslog bases alerts into the active alarms console.
I have experience with CA spectrum in a much larger environment (20k nodes) and some experience with OpenNMS. Typically you can map traps to alarms including what trap might clear a previous.
From researching SolarWinds it seems you can send emails based on traps, but not bring them into the alarm dashboard. Only that which can be polled can be brought to the alarms dashboard (or by DB query). The hack provided on the forum is to tag traps and write some sql for alerting and clearing. That seems fine for 1 or 2 traps, but unsustainable for many. Also the tag table is not indexed by default so queries are slow (this can be fixed I guess).
So to my questions: How can SolarWinds be recommended without trap handling (or am I missing something)? Are trap based alarms not relevant to the average network operator?
No comments:
Post a Comment