{"action":"opened","issue":{"url":"https://api.github.com/repos/Microsoft/IIS.Administration/issues/206","repository_url":"https://api.github.com/repos/Microsoft/IIS.Administration","labels_url":"https://api.github.com/repos/Microsoft/IIS.Administration/issues/206/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/IIS.Administration/issues/206/comments","events_url":"https://api.github.com/repos/Microsoft/IIS.Administration/issues/206/events","html_url":"https://github.com/Microsoft/IIS.Administration/issues/206","id":376740380,"node_id":"MDU6SXNzdWUzNzY3NDAzODA=","number":206,"title":"api/webserver/websites/monitoring returns responses with invalid values","user":{"login":"tomekkolo","id":38069337,"node_id":"MDQ6VXNlcjM4MDY5MzM3","avatar_url":"https://avatars3.githubusercontent.com/u/38069337?v=4","gravatar_id":"","url":"https://api.github.com/users/tomekkolo","html_url":"https://github.com/tomekkolo","followers_url":"https://api.github.com/users/tomekkolo/followers","following_url":"https://api.github.com/users/tomekkolo/following{/other_user}","gists_url":"https://api.github.com/users/tomekkolo/gists{/gist_id}","starred_url":"https://api.github.com/users/tomekkolo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tomekkolo/subscriptions","organizations_url":"https://api.github.com/users/tomekkolo/orgs","repos_url":"https://api.github.com/users/tomekkolo/repos","events_url":"https://api.github.com/users/tomekkolo/events{/privacy}","received_events_url":"https://api.github.com/users/tomekkolo/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-11-02T09:51:24Z","updated_at":"2018-11-02T09:51:24Z","closed_at":null,"author_association":"NONE","body":"When invoking https://localhost:55539/api/webserver/websites/monitoring very often response contains invalid data, i.e. uptime. After requesting data few more times, counters start to be filled properly. This makes hard to write proper monitoring that is using REST API, as we cannot be sure that values are correct. \r\n\r\nBelow few subsequent invocations using PS. uptime for the first time is 0, then with next invocations API starts to return correct value. \r\n\r\n> Invoke-WebRequest -SkipCertificateCheck -Headers @{\"Access-Token\"=\"Bearer xMOPoc2Lga2U4xpVg2pLHbPmounEwetPyOWwknW16znHmkQ9ZP9xEA\"} -Method GET https://localhost:55539/api/webserver/websites/monitoring | ConvertFrom-Json\r\n                                                                                                                                                                                                                  websites                                                                                                                                                                                                          --------                                                                                                                                                                                                          {@{id=4XNV5K0aqDi2frsjKxiYhA; uptime=6124; network=; requests=; memory=; cpu=; disk=; cache=; website=}, @{id=OHV066wpU28dz6bqFznRsg; uptime=0; network=; requests=; memory=; cpu=; disk=; cache=; website=}, ... \r\n\r\n\r\n> Invoke-WebRequest -SkipCertificateCheck -Headers @{\"Access-Token\"=\"Bearer xMOPoc2Lga2U4xpVg2pLHbPmounEwetPyOWwknW16znHmkQ9ZP9xEA\"} -Method GET https://localhost:55539/api/webserver/websites/monitoring | ConvertFrom-Json\r\n                                                                                                                                                                                                                  websites                                                                                                                                                                                                          --------                                                                                                                                                                                                          {@{id=4XNV5K0aqDi2frsjKxiYhA; uptime=6124; network=; requests=; memory=; cpu=; disk=; cache=; website=}, @{id=OHV066wpU28dz6bqFznRsg; uptime=1205; network=; requests=; memory=; cpu=; disk=; cache=; website=... \r\n\r\n\r\n> Invoke-WebRequest -SkipCertificateCheck -Headers @{\"Access-Token\"=\"Bearer xMOPoc2Lga2U4xpVg2pLHbPmounEwetPyOWwknW16znHmkQ9ZP9xEA\"} -Method GET https://localhost:55539/api/webserver/websites/monitoring | ConvertFrom-Json\r\n                                                                                                                                                                                                                  websites                                                                                                                                                                                                          --------                                                                                                                                                                                                          {@{id=4XNV5K0aqDi2frsjKxiYhA; uptime=6129; network=; requests=; memory=; cpu=; disk=; cache=; website=}, @{id=OHV066wpU28dz6bqFznRsg; uptime=1210; network=; requests=; memory=; cpu=; disk=; cache=; website=... \r\n\r\n\r\nps. I could not find if there are any debug kind of logs that would help to investigate this issue."}}
{"actor":{"display_login":"tomekkolo"}}