{"action":"opened","issue":{"url":"https://api.github.com/repos/syepes/VSphere2Metrics/issues/7","repository_url":"https://api.github.com/repos/syepes/VSphere2Metrics","labels_url":"https://api.github.com/repos/syepes/VSphere2Metrics/issues/7/labels{/name}","comments_url":"https://api.github.com/repos/syepes/VSphere2Metrics/issues/7/comments","events_url":"https://api.github.com/repos/syepes/VSphere2Metrics/issues/7/events","html_url":"https://github.com/syepes/VSphere2Metrics/issues/7","id":151197914,"number":7,"title":"datastore instance has no type","user":{"login":"exbane","id":12447405,"avatar_url":"https://avatars.githubusercontent.com/u/12447405?v=3","gravatar_id":"","url":"https://api.github.com/users/exbane","html_url":"https://github.com/exbane","followers_url":"https://api.github.com/users/exbane/followers","following_url":"https://api.github.com/users/exbane/following{/other_user}","gists_url":"https://api.github.com/users/exbane/gists{/gist_id}","starred_url":"https://api.github.com/users/exbane/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/exbane/subscriptions","organizations_url":"https://api.github.com/users/exbane/orgs","repos_url":"https://api.github.com/users/exbane/repos","events_url":"https://api.github.com/users/exbane/events{/privacy}","received_events_url":"https://api.github.com/users/exbane/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-26T17:53:02Z","updated_at":"2016-04-26T17:53:02Z","closed_at":null,"body":"the collector has been running great for the past few days.. i was checking the logs though and found many of these types of entries. \r\n\r\n26-04-2016 - 13:44:01.067 [graf-vm201] 19492:[vcenter202] WARN  com.allthingsmonitoring.vmware.VSphere2Metrics - The datastore Instance: 82b929f0-4f070b62 has no type\r\n\r\nIs this something that's a bottleneck or just benign? I have 3 very large vSphere infrastructure's that i'm pulling from and the logs say that it takes just a couple minutes to gather all metrics needed and ships them off to influxdb - but when i look at the metrics for a particular virtual machine it doesn't refresh the information for upto 10-15 minutes.. It's not an IO/Memory/CPU issue that i can tell on either my collector of influxdb.. influxdb is running on EMC xtreme-io storage and is hosted on a pair of DL980 servers each with 512TB of RAM. I can tell when i started the collectors for all 3 vcenters that the IO went through the roof (about 8-10k IOPs) but all with lower then 2ms of latency so i'm not too worried about that.. should i split the collectors up between 3 different collector VMs? \r\n\r\ni also altered the java heap max size from the default to 12GB for each service - i ran out of heap space with the defaults. \r\n\r\nthoughts? \r\n\r\nthank you,\r\n\r\nexbane"}}