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

Discovered hypervisors agent interface is mapped to the controller hosts interface #8

Open
jord-bh opened this issue Nov 30, 2017 · 3 comments

Comments

@jord-bh
Copy link

jord-bh commented Nov 30, 2017

Perhaps this is a limitation of the script in some way, but it doesn't feel correct that the automatically discovered hypervisors has their agent interfaced mapped towards the controller host which initiated the discovery?

To my understanding, the agent interface is the definition of where zabbix connects to poll for information. In my case, on the discovered hypervisor this is the same as the configured zabbix controller host item.

@jord-bh
Copy link
Author

jord-bh commented Dec 8, 2017

Could this be due to Zabbix limitations?

https://support.zabbix.com/browse/ZBXNEXT-2072

@cloudowski
Copy link
Owner

Yes, it looks like it is. Actually I'm still waiting for this issue to be resolved in Zabbix, but it doesn't seem to be an interesting topics for its developers :(

@jord-bh
Copy link
Author

jord-bh commented Aug 3, 2018

Too bad, it definitely hinders the usefulness of the setup. iirc from back then, I tried toying around with modifying it afterwards so that the agent interface field would be populated with the correct string, but discovered rules are supposed to stay the way they were created upon discovery. I even went as far as hacking straight in the database but without any luck, so an actual fix from the developers is the only solution as I see it.

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

2 participants