> 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/solution/block-storage-metrics-not-displayed-in-clarity-ui.md).
# Block Storage Metrics Not Displayed in Clarity UI
## Problem
* In Clarity UI, under Infrastructure -> Hosts, when viewing the host details (via clicking on the hostname of a host listed) for a host with the Block Storage role, the Block Storage metrics are blank.
Screen_Shot_2018-09-05_at_3.30.12_PM.png
## Environment
* Platform9 Managed OpenStack - v3.6-3.7
* Cinder
## Cause
A Platform9-specific API was deprecated and a decision was made to move to the standard Cinder pool API for collecting the Block Storage statistics. The latter API failed to be implemented ahead of this change and thus the call to the old API endpoint returned a 404 error.
## Resolution
1. An upgrade to the affected versions has been released. If you are still facing this issue, please [contact Platform9 Support](https://support.platform9.com/hc/en-us).
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://platform9.com/kb/pmo/solution/block-storage-metrics-not-displayed-in-clarity-ui.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.