|
|
| Subject: | zencommand events and data for multiple components |
| Author: | Jay Stanley |
| Posted: | 2016-03-10 16:23 |
I know you can setup zencommand to run once and collect data for multiple components. But I am running into several issues.
zencommand over parses results when running it once per device for many components. Which means, if I have zencommand output json with data and events, the events get parsed once for each component on the device. So, if I create 2 events for 2 of the 10 components, then 2 events will come in, but with a count of 10.
This can get quickly out of hand when a device has a lot of these components, especially when you throw in clear events.
I can get around this by creating a device level template. But then i cannot write to the component datapoints.
I am wondering what is the proper way I should go about this
I had a few ideas, but they all seem ghetto...
| Subject: | I actually realized that |
| Author: | Jay Stanley |
| Posted: | 2016-04-06 10:48 |
I actually realized that parsers will run through the output for each component. It will do it for both events and rrd data. but the parsers will actually filter out the data based on the component defined.
I ended up making a new parser that would filter both rrd data and events based on the component. It would still leave the challenge of dropping events that did not have a component, but I can always plan for that in my scripts.
| < |
Previous Zenoss 5.0.9 timezone |
Next Zenoss 5.1.1 upgrade issues |
> |