{"action":"created","issue":{"url":"https://api.github.com/repos/BaldMansMojo/check_vmware_esx/issues/90","repository_url":"https://api.github.com/repos/BaldMansMojo/check_vmware_esx","labels_url":"https://api.github.com/repos/BaldMansMojo/check_vmware_esx/issues/90/labels{/name}","comments_url":"https://api.github.com/repos/BaldMansMojo/check_vmware_esx/issues/90/comments","events_url":"https://api.github.com/repos/BaldMansMojo/check_vmware_esx/issues/90/events","html_url":"https://github.com/BaldMansMojo/check_vmware_esx/issues/90","id":150824796,"node_id":"MDU6SXNzdWUxNTA4MjQ3OTY=","number":90,"title":"mem usage =  -0.01 %","user":{"login":"banholzer","id":14129089,"node_id":"MDQ6VXNlcjE0MTI5MDg5","avatar_url":"https://avatars2.githubusercontent.com/u/14129089?v=4","gravatar_id":"","url":"https://api.github.com/users/banholzer","html_url":"https://github.com/banholzer","followers_url":"https://api.github.com/users/banholzer/followers","following_url":"https://api.github.com/users/banholzer/following{/other_user}","gists_url":"https://api.github.com/users/banholzer/gists{/gist_id}","starred_url":"https://api.github.com/users/banholzer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/banholzer/subscriptions","organizations_url":"https://api.github.com/users/banholzer/orgs","repos_url":"https://api.github.com/users/banholzer/repos","events_url":"https://api.github.com/users/banholzer/events{/privacy}","received_events_url":"https://api.github.com/users/banholzer/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2016-04-25T11:10:17Z","updated_at":"2018-09-14T14:26:55Z","closed_at":null,"author_association":"NONE","body":"Hi, since we updated to vsphere 6.0 we have the problem, that sometimes mem usage and cpu usage are critical with -0.01 %\n\nDo you know the reason for this? I remember that I had the same issue some years ago with the \"old\" esxi nagios check. As far as I remember it had to do with timeouts.\n\nDo you have any suggestions to get rid of these messages? (The ESXi servers are still at 5.5.)\n\nThanks\n\n> Notification Type: PROBLEM\n> \n> Service: check_esx3_dc_host_mem_usage\n> Host: <esxi-server-name> (ESXi Host)\n> Address: <esxi-server-address>\n> State: CRITICAL\n> \n> Date/Time: Sun Apr 24 15:04:43 CEST 2016\n> \n> Additional Info:\n> P1.PL CRITICAL - mem usage=-0.01 %\n"},"comment":{"url":"https://api.github.com/repos/BaldMansMojo/check_vmware_esx/issues/comments/421375615","html_url":"https://github.com/BaldMansMojo/check_vmware_esx/issues/90#issuecomment-421375615","issue_url":"https://api.github.com/repos/BaldMansMojo/check_vmware_esx/issues/90","id":421375615,"node_id":"MDEyOklzc3VlQ29tbWVudDQyMTM3NTYxNQ==","user":{"login":"banholzer","id":14129089,"node_id":"MDQ6VXNlcjE0MTI5MDg5","avatar_url":"https://avatars2.githubusercontent.com/u/14129089?v=4","gravatar_id":"","url":"https://api.github.com/users/banholzer","html_url":"https://github.com/banholzer","followers_url":"https://api.github.com/users/banholzer/followers","following_url":"https://api.github.com/users/banholzer/following{/other_user}","gists_url":"https://api.github.com/users/banholzer/gists{/gist_id}","starred_url":"https://api.github.com/users/banholzer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/banholzer/subscriptions","organizations_url":"https://api.github.com/users/banholzer/orgs","repos_url":"https://api.github.com/users/banholzer/repos","events_url":"https://api.github.com/users/banholzer/events{/privacy}","received_events_url":"https://api.github.com/users/banholzer/received_events","type":"User","site_admin":false},"created_at":"2018-09-14T14:26:55Z","updated_at":"2018-09-14T14:26:55Z","author_association":"NONE","body":"I din't remember this issue was still open. The hint not to use the internal Perl interpreter helped that time. Shouldn't an0nwax's problem be a new issue? Should this be closed?"}}
{"actor":{"display_login":"banholzer"}}