> For the complete documentation index, see [llms.txt](https://docs.akamas.io/akamas-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akamas.io/akamas-docs/3.5.0/reference/glossary/telemetry-instance.md).
# Telemetry Instance
A **telemetry instance** is an instance of a [telemetry provider](/akamas-docs/3.5.0/reference/glossary/telemetry-providers.md) that collects data from a specific instance of the data source.
A **telemetry instance** is an instance of a telemetry provider, providing the required information on how to connect and collect a given set of metrics from a specific data source.
While telemetry providers are platform-wide entities, telemetry instances are defined at each system level.
## Construct
The construct to be used to define a telemetry instance is described on the [Telemetry Instance template](/akamas-docs/3.5.0/reference/construct-templates/telemetry-instance-template.md) page.
## Commands
A telemetry provider is an [Akamas resource](/akamas-docs/3.5.0/reference/cli-reference.md#clireference-operations) that can be managed via CLI using the [resource management commands.](/akamas-docs/3.5.0/reference/cli-reference/resource-management.md)
## User Interface
Telemetry instances are displayed in the Akamas UI when drilling down each system component.
---
# 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://docs.akamas.io/akamas-docs/3.5.0/reference/glossary/telemetry-instance.md?ask=&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.
