> For the complete documentation index, see [llms.txt](https://docs.iotify.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iotify.io/getting-started/look-deeper-with-metrics.md).

# Look deeper with Metrics

We also have a robust Metrics engine that keeps a track of many important metrics throughout all test runs, with the ability to add custom metrics as well. The Metrics can then be visualized using the Metrics section on IoTIFY. Graphs can be generated with a multitude of filters to better understand how the system has been performing.

![](/files/DAcJogo6WrK7sqbhJUnL)

Here, you can select which metric you want to see from the drop-down here, then choose an aggregate function and the job you want the metrics for, and finally click on the Update Chart button to create the chart.

{% hint style="info" %}
We log certain metrics like message latency and sending latency by default for all simulation jobs. Additionally, you can also see the system metrics like the number of MQTT connects, total bytes sent via MQTT and more by the `System-wide Metrics` toggle.
{% endhint %}


---

# 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.iotify.io/getting-started/look-deeper-with-metrics.md?ask=<question>&goal=<endgoal>
```

`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.