Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature request...tweak timeouts #282

Open
dougsyer opened this issue Dec 9, 2014 · 0 comments
Open

feature request...tweak timeouts #282

dougsyer opened this issue Dec 9, 2014 · 0 comments

Comments

@dougsyer
Copy link

dougsyer commented Dec 9, 2014

Today on the old zenpack I have a fairly complex set of transforms that does counting escalation based on type of WMI error and count.

I suspect the timeouts will be less now with this zp but one thing I realized is that without the timeout/limiter(ie ease off on collection like max oids) zproperties you have with zencommand or zenperfsnmp you are forced to expose your system to huge bursts of load due to waves of counting transforms going off when there are connectivity issues or windows issues that prevent the processing of monitoring data..

If you have timeouts / limiters you can push that work away from the core and onto the collectors (where it should be) and you can customize them per device/site etc based on connectivity /health of the system if you need to.

If I remove the /status/wmi count transforms (and we have /command ones but they dont get hit nearly as much because wmi is more of a challenge) ...the issue is that our NOC gets exposed to alot of non/actionable events. which eventually they become numb to.

for more detail see parature case # 27296

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant