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
some ideas for improvement #10
Comments
Hi, thanks for the feedback. Most of that seems doable I think, but I have to double check. Do you want to open a PR? Otherwise I cannot say when stuff will be implemented |
It was just a brainstorming on how to improve the script. I haven't implemented the check in Icinga yet and I'm not sure if/which of the above features I need, so I can't say if I will implement any of them |
No problem, feedback is always welcome. |
@sklaes Could you elaborate what you mean with the "--noproxy" option? |
If there is an environment variable defined such as http_proxy, HTTP_PROXY, https_proxy or HTTPS_PROXY, python will use the proxy instead of a direct connection.
|
I see. Woudn't unsetting the variable on specific nodes be an option? I'm not sure yet if this is something that should be included in the code. |
@sklaes I'm not a user of the Plugin, can you give some details on this point?
|
You could set your check interval and the time filter to e.g. 5 min, so you will only get new alerts. The check will automatically reset to green on the next check. (You also need to mark the check as volatile in Icinga to get a notification on the first state change) |
Thanks again. If need arises we could still do that, for now I'm not sure about implementing this. |
We implemented a couple of the suggestions in the new release. We'll update the Icinga Exchange soon. |
and by the way, the releases page on exchange.icinga.com lists v0.1.0 as latest
https://exchange.icinga.com/netways/check_vmware_nsxt/releases
The text was updated successfully, but these errors were encountered: