> For the complete documentation index, see [llms.txt](https://docs-old.zus.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-old.zus.network/products/chimney/visualize-blobber-logs.md).
# Visualize Blobber Logs
1. Begin by navigating to the Chimney Dashboard and select the "Logs" option. The logs section is highlighted within a black box in the screenshot below.
2. The application will then present you with a log list, categorized by Blobber and Validator.
3. To visualize these logs on the Grafana Dashboard, simply click on the "Go to Loki" button. This button is highlighted in the screenshot below.
4. Upon clicking the button, you will be redirected to the Grafana Dashboard where you can begin visualizing both Blobber and Validator logs.
5. To gain access to the Grafana Dashboard, please use your Chimney deployment username and password.
6. Once you are logged in, you can select a specific entity (Server, Blobber, or Validator) for which you wish to view and visualize the logs. For this example, let's choose "Blobber Logs."
7. To add a panel for visualizing the logs, click on the "Add" button, and then select "Visualize" on the Grafana Dashboard, as indicated in the reference screenshot below.
---
# 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://docs-old.zus.network/products/chimney/visualize-blobber-logs.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.