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

Zabbix Module Return - Catch vSphere outage #254

Open
rockaut opened this issue Aug 21, 2018 · 1 comment · May be fixed by #255
Open

Zabbix Module Return - Catch vSphere outage #254

rockaut opened this issue Aug 21, 2018 · 1 comment · May be fixed by #255

Comments

@rockaut
Copy link
Contributor

rockaut commented Aug 21, 2018

I recently updated my vCenters and forgot to switch the zabbix items in maintenance without data collection. It resulted in an Problem-Storm as nearly all triggers for the hosts kicked in.

Problem is, that vPoller/vConnector cant get data from vCenter and returns some string for all requested data. For zabbix text items this string then triggers false-positives and for zabbix numeric items it states the wrong value type.

I think the correct way to handle that should be something like here:
https://www.zabbix.com/documentation/3.2/manual/appendix/items/activepassive

Like so:
<HEADER><DATALEN>ZBX_NOTSUPPORTED\0Cannot obtain vSphere data

A great thing would be an "virtual" zabbix item where vPoller stores if data could get fetched - if something failes this item then reports an error. With such an item we can make all triggers of other items depending and no problem storms can happen. It's basically the same mechanism as the Zabbix Agent itself is using.

Any ideas?

@rockaut
Copy link
Contributor Author

rockaut commented Aug 21, 2018

The resulting string currently is "Task host.get failed"

rockaut added a commit to rockaut/py-vpoller that referenced this issue Sep 1, 2018
Currently as in dnaeon#254 described if vcenter or host is not available the returned zabbix result is still OK instead of FAIL.

It should be FAIL as then we can define an nodata() trigger on an host status or directly vcenter status and make other triggers dependent. A little bit like with Zabbix Agent Status.

I'm not into C so if might done it false? It compiled and seamed to work for me.
@rockaut rockaut linked a pull request Sep 1, 2018 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant