> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/how-to/finding-vsphere-uuid-for-vsphere-vm-in-clarity-ui.md).

# Finding vSphere UUID for vSphere VM in Clarity UI

## Problem

There can be a use-case where vSphere UUID for a VM is needed. It can be used for monitoring or automation purposes.

## Environment

* Platform9 Managed OpenStack - v3.6.0 and Higher

## Procedure

There are two ways to accomplish this in the Clarity UI

1. You can find the vSphere UUID by clicking on an individual VM instance in the Clarity UI under Instances tab and note down the "Openstack ID"

<figure><img src="https://3413721029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8o9pwjt91cVZOj58RUXj%2Fuploads%2Fgit-blob-603d6224b356e0060df50267361547f774b8465e%2F1623345616.png?alt=media" alt="mceclip0.png"><figcaption><p>mceclip0.png</p></figcaption></figure>

2. A user can view the UUIDs for all the instances by enabling the Openstack ID as a Column in the Clarity UI. This can be done by browsing to "Instances View" -> Click on the "Settings" button in the right corner -> Add Openstack ID field -> Click on "Save".

![](https://support.platform9.com/attachments/token/1HpUNDQQjaTef3BOS6vVTDYat/?name=inline179934351.png)

![](https://support.platform9.com/attachments/token/PqKwSHUg06nuDLuFs9YlwdN9i/?name=inline1653886097.png)

Now you can view the instance UUIDs for all the VM instances in the Clarity UI.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmo/how-to/finding-vsphere-uuid-for-vsphere-vm-in-clarity-ui.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.