{"id":1307,"date":"2021-10-26T10:01:15","date_gmt":"2021-10-26T08:01:15","guid":{"rendered":"https:\/\/nine30.info\/?p=1307"},"modified":"2021-10-26T10:01:15","modified_gmt":"2021-10-26T08:01:15","slug":"credential-less-service-discovery-with-vrops","status":"publish","type":"post","link":"https:\/\/nine30.nxt70.com\/index.php\/2021\/10\/26\/credential-less-service-discovery-with-vrops\/","title":{"rendered":"Credential-less Service Discovery with vROps"},"content":{"rendered":"\n

vRealize Operations (On-Premise and SaaS) allows you to discover services running in each VM and then builds relationship or dependency between the services from different VMs. In addition to that you are provided with basic metrics and properties for discovered services. \u200bvROps Service Discovery supports some services, but not any service, the supported services are listed here<\/a>. <\/p>\n\n\n\n

To discover applications\/services and their relationships and to access basic metrics\/properties, you can either provide guest operating system credentials with appropriate privileges or use the credential-less approach to discover services. To me the first option, provide guest operating system credentials, is a viable option only when default accounts for guest operating systems are in use and this is a quite rare situation in real life. For this reason I am focusing here on the credential-less approach which requires little efforts and no credentials for the managed guest operating systems.<\/p>\n\n\n\n

Requirements<\/h2>\n\n\n\n

Here I am assuming you have an instance of vROps On-Premise or Cloud already deployed and collecting data from at least vCenter. The screenshots in the rest of this post are taken from vROps Cloud, but the same applies to the On-Prem deployment. You can notice the SaaS version already includes the UI updates introduced with vROps 8.6.<\/p>\n\n\n\n

Compatibility Matrix<\/h3>\n\n\n\n

To leverage credential-less service discovery you need an environment with the followings:<\/p>\n\n\n\n