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
added features to request version and license informations #142
Conversation
Only a lock file is used when actually updating the session, which happens when: * there is no session file * the session is no longer valid Parallel jobs will try to use the old session, if that fails every process will re-login, but the session file will only be written once. The scripts checks if the session file has been changed since their own program start time.
This allows Github to render Markdown.
This allows the plugin to run on any distribution in a yet better way.
…erience - Add About section which explains the purpose of this plugin - Explain two installation modes - Move specific explanations into FAQ chapter - Add a note on VMware API timeouts - Add some examples and references to Icinga 2 configuration and CheckCommands - Add chapters similar to known Icinga projects - Reformat everything as proper Markdown
otherwise cookies may not match with LWP
$host_state cannot equal to UP and "Maintenance Mode" at the same time
Compare the api returned url and the given url2connect less error prone. Using --sslport=443 results in a url2connect https://vcenter:443/... while get_option returns https://vcenter/... Also it seems like some api returns .../sdk while others return .../sdk/webService so just ignore that part. Both leads to not resuing the existing session files. this should fix #115
Feature/rewrite readme
Use Perl from env instead of a fixed path
make session file usage more robust
…k_vmware_esx into lazyfrosch-locking-behavior Conflicts: README.md
Instead of calling Vim::get_view for each datastore call Vim::get_views with all of them at once.
…panda-fix-bad-OUM
only write warning if host runtime is checked with no subselect
merge recent additions to master
Sometimes not all hardware components are correctly reported via CIM interface which leads to check errors when checking runtime status all. This option ignores the health status and prevents the the plugin from failing to report the overall status of the host. IMPORTENT: make sure to monitor the host health status separately! Most likely via ILO/ILOM interface.
Also command_reference has been updated Missing history entry in check_vmware_esx.pl from last comit added
Next release
Next release
declare all file handles as UTF-8
fxing minor typos
minor typo fix ... might be in more modules ?
Update dc_runtime_info.pm
Update vm_runtime_info.pm
Hi, So give me a feedback why I should add it. Maybe there is something useful I haven't thought about. For now I will close this request but I have the code to implement it. Martin |
Hi, well it's about if you licensed your environment properly or not. 2 examples:
And I wanted to reduce the amount of esxi icinga plugins to use for monitoring. |
Ok - that's an argument. I will implement this evening. |
I will add as much as possible this weekend because I will have a presentation next Monday about monitoring VMware next Monday on Monitoring Workshop here in Munich. |
I will prepare another pull request this afternoon |
About what? Only to know that we won't run in conficts. Regards |
This feauture |
added two new features to last PR: