#zenoss

Being in IT Industry from past 9 Years .. I started my career with IT Infrastructure Monitoring . This opportunity gave me insight to all aspects of IT Infrastructure layers.

There are various Monitoring tools available in the market , few of them are :-

Zenoss

SolarWinds

Nagios

DataDog .. and many more ….

My favorite is Zenoss , reason is simple got the opportunity to work with this fantastic tool.

So what is Infrastructure Monitoring ??

It is the process to capture the metrics of all components of IT Infra. Be it Servers , Network , Data Storage or Application . It capture the metrics to make sure everything is working in healthy state . Alerting is a mechanism , which alerts the specific teams about the event which occurred. That alerting is , what is configured once we implement a Monitoring tool….

Zenoss delivers the quickest and most precise insight into potentially affected services so you can fix the problem before your business and users are impacted. You’ll know more and be able to act faster than you could with device-centric unified monitoring tools, and without the rigidness and hefty price tag.       

Resolved: How do I remotely install, configure and maintain SNMP? #answer #development #fix

How do I remotely install, configure and maintain SNMP?

I’m looking to remotely install the SNMP and SNMP WMI Provider services on Windows Server 2008 R2, configure specific options for the Agent, Traps, and Security tabs, then make sure these services and settings aren’t removed or turned off. This goal is precipitated by the desire to remotely monitor server health with Zenoss.

Through my…

New Post has been published on http://www.eventenrichment.org/fixing-zenoss-zenpack-zenactiond-error/

How to fix the Zenoss/Pagerduty ZenPack error: zenactiond - Action:pagerduty Status:FAIL

PagerDuty ZenPack pre zenactiond restart

2014-03-04 10:00:58,786 INFO zen.zenactiond: Event:’pd01|apache|/App/Apache|5|TESTEVENT’ Trigger:TestEvents Action:pagerduty Status:FAIL Target:3cbade96-3863-41ac-8e75-96fcac1ac695 Info:

Have you run into this error after installing the PagerDuty APINotification ZenPack (ZenPacks.PagerDuty.APINotification)?

If so, the fix is simple. In addition to restarting Zope (zopectl restart) after installing the ZenPack, you will also need to restart zenactiond (as the Zenoss user) by issuing ‘zenactiond restart’.

PagerDuty ZenPack post zenactiond restart

2014-03-04 10:02:09,596 INFO zen.zenactiond: Event:’pd999|apache|/App/Apache|5|TESTEVENT’ Trigger:TestEvents Action:pagerduty Status:SUCCESS Target:3cbade96-3863-41ac-8e75-96fcac1ac695 Info:

New Post has been published on http://www.eventenrichment.org/enrich-zenoss-events-embedding-details/

How the heck do I get Zenoss event details into the event message?

  Fix it with Event Enrichment

Have you ever been frustrated by seeing an event like this? In the example used below, of an SNMP trap from the Monyog system, the message “snmp trap monitorTrap” has zero value, as it is completely generic. You would need to dig deeper into the event details, in order to discover pertinent information.

Event details, such as ‘Monitor.13.0‘ and ‘Status‘, provide relevant and critical information associated with the problem. In order to have this critical information included in future events, we would enrich this event through the use of an event transform.

Event Enrichment Transform

We begin by navigating to the appropriate event class, in this case, /Traps. Click on the “Events” tab and choose the “Event Classes” option. Then, scroll down and click on “Traps”.

Finally, click on the Gear icon and choose “Transform”.

Once you click on “Transform”, the transform creation page will appear. <INSERT TRANSFORM CREATION PAGE>

Transform Creation

In many cases, critical information can be difficult to find as amongst less relevant event details. The transform detailed below updates the event summary and message fields with this critical information. In order to provide you with a deeper understanding of transform creation, we will deconstruct and review the following sample line by line.

# Let's grab the details from the Monyog traps for d in evt.details._map.keys(): if d == 'monitor.13.0': query = evt.details.get(d) evt.message = "The following query is taking longer than the allocated interval:\n" + query if d == 'status.1.0': evt.summary = evt.summary + ": " + evt.details.get(d) if d == 'monitor.20.0': evt.component = evt.details.get(d) if d == 'monitor.19.0': evt.summary = evt.details.get(d) if d == 'monitor.8.0': evt._action = 'history'

We begin by iterating through the event details. We access these details by reading the values of evt.details through the use of the _map.keys() function.

for d in evt.details._map.keys():

<mr. burns> Excellent … We now have access to the fields in the event details through our looping of the returned keys. In the Monyog case, the additional information is returned in the “monitor.#” details. as seen in the Zenoss event above. In order to enrich the event with the additional information, we walk through the detail keys and, upon match, update the relevant Zenoss event field (e.g. evt.summary, evt.message, evt.component). The event’s relevant fields can be manipulated by prefixing “evt.” to the names of the event fields. evt.status: Note this query has take more than ’30′ seconds. Add this status notification to the Zenoss event summary:

if d == 'status.1.0': evt.summary = evt.summary + ": " + evt.details.get(d)

evt.monitor.13: SELECT_SQL_CALC_FOUND… Add the specifics of the slow SQL query to the event message field:

if d == 'monitor.13.0': query = evt.details.get(d) evt.message = "The following query is taking longer than the allocated interval:\n" + query

evt.monitor.20: Host having the issue Add the host to the event component field:

if d == 'monitor.20.0': evt.component = evt.details.get(d)

evt.monitor.8: Informational (NOISE) Monyog Trap – move to history:

if d == 'monitor.8.0': evt._action = 'history'

add screen shot of event with evt prefix here Note: for the list of field options, double click on the summary column of any event in the Zenoss Event Console. There you have it! All subsequent Monyog traps of this type will be enriched with these important event details. For a deeper insight into Zenoss Events and Zenoss overall, I highly recommend reading Jane Curry’s book; Event Management for Zenoss Core 4.

What are some of your favorite transforms?

Share!

New Post has been published on http://www.eventenrichment.org/enrich-zenoss-events-embedding-details/

How the heck do I get Zenoss event details into the event message?

  Fix it with Event Enrichment

Have you ever been frustrated by seeing an event like this? In the example used below, of an SNMP trap from the Monyog system, the message “snmp trap monitorTrap” has zero value, as it is completely generic. You would need to dig deeper into the event details, in order to discover pertinent information.

Event details, such as ‘Monitor.13.0‘ and ‘Status‘, provide relevant and critical information associated with the problem. In order to have this critical information included in future events, we would enrich this event through the use of an event transform.

Event Enrichment Transform

We begin by navigating to the appropriate event class, in this case, /Traps. Click on the “Events” tab and choose the “Event Classes” option. Then, scroll down and click on “Traps”.

Finally, click on the Gear icon and choose “Transform”.

Once you click on “Transform”, the transform creation page will appear. <INSERT TRANSFORM CREATION PAGE>

Transform Creation

In many cases, critical information can be difficult to find as amongst less relevant event details. The transform detailed below updates the event summary and message fields with this critical information. In order to provide you with a deeper understanding of transform creation, we will deconstruct and review the following sample line by line.

# Let's grab the details from the Monyog traps for d in evt.details._map.keys(): if d == 'monitor.13.0': query = evt.details.get(d) evt.message = "The following query is taking longer than the allocated interval:\n" + query if d == 'status.1.0': evt.summary = evt.summary + ": " + evt.details.get(d) if d == 'monitor.20.0': evt.component = evt.details.get(d) if d == 'monitor.19.0': evt.summary = evt.details.get(d) if d == 'monitor.8.0': evt._action = 'history'

We begin by iterating through the event details. We access these details by reading the values of evt.details through the use of the _map.keys() function.

for d in evt.details._map.keys():

<mr. burns> Excellent … We now have access to the fields in the event details through our looping of the returned keys. In the Monyog case, the additional information is returned in the “monitor.#” details. as seen in the Zenoss event above. In order to enrich the event with the additional information, we walk through the detail keys and, upon match, update the relevant Zenoss event field (e.g. evt.summary, evt.message, evt.component). The event’s relevant fields can be manipulated by prefixing “evt.” to the names of the event fields. evt.status: Note this query has take more than ’30′ seconds. Add this status notification to the Zenoss event summary:

if d == 'status.1.0': evt.summary = evt.summary + ": " + evt.details.get(d)

evt.monitor.13: SELECT_SQL_CALC_FOUND… Add the specifics of the slow SQL query to the event message field:

if d == 'monitor.13.0': query = evt.details.get(d) evt.message = "The following query is taking longer than the allocated interval:\n" + query

evt.monitor.20: Host having the issue Add the host to the event component field:

if d == 'monitor.20.0': evt.component = evt.details.get(d)

evt.monitor.8: Informational (NOISE) Monyog Trap – move to history:

if d == 'monitor.8.0': evt._action = 'history'

add screen shot of event with evt prefix here Note: for the list of field options, double click on the summary column of any event in the Zenoss Event Console. There you have it! All subsequent Monyog traps of this type will be enriched with these important event details. For a deeper insight into Zenoss Events and Zenoss overall, I highly recommend reading Jane Curry’s book; Event Management for Zenoss Core 4.

What are some your favorite transforms?

Share!