> 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/integrating/integrating-telemetry-providers.md).

# Integrating Telemetry Providers

Akamas Studio supports the integration with virtually any telemetry and observability tool.

### Supported Telemetry Providers

The table below lists the supported Telemetry Providers that are **automatically created during an online installation**.

In an offline environment (where your Kubernetes cluster cannot access public repositories), telemetry providers are not automatically installed. Instead, each telemetry provider must be installed individually and manually. **For specific installation instructions, refer to the documentation page of each individual telemetry provider.**

| Telemetry Provider                                                                                                                       | Description                                                                          |
| ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| [CSV provider](/akamas-docs/integrating/integrating-telemetry-providers/csv-provider.md)                                                 | collects metrics from CSV files                                                      |
| [Dynatrace](/akamas-docs/integrating/integrating-telemetry-providers/dynatrace-provider.md)                                              | collects metrics from Dynatrace                                                      |
| [Prometheus](https://gitlab.com/akamas/documentation/akamas-docs/-/tree/4.1/reference/telemetry-providers/prometheus-metrics-mapping.md) | collects metrics from Prometheus                                                     |
| [Spark History Server](/akamas-docs/integrating/integrating-telemetry-providers/spark-history-server-provider.md)                        | collects metrics from Spark History Server                                           |
| [NeoloadWeb](/akamas-docs/integrating/integrating-telemetry-providers/neoloadweb-provider.md)                                            | collects metrics from Tricentis Neoload Web                                          |
| [Load Runner Professional](/akamas-docs/integrating/integrating-telemetry-providers/loadrunner-professional-provider.md)                 | collects metrics from MicroFocus Load Runner Professional                            |
| [Load Runner Enterprise](/akamas-docs/integrating/integrating-telemetry-providers/loadrunner-enterprise-provider.md)                     | collects metrics from MicroFocus Load Runner Enterprise                              |
| [AWS](/akamas-docs/integrating/integrating-telemetry-providers/aws-provider.md)                                                          | collects price metrics for Amazon Elastic Compute Cloud (ec2) from Amazon’s own APIs |
| [Custom Metrics](/akamas-docs/integrating/integrating-telemetry-providers/custom-metrics/install-custom-metrics-provider.md)             | generates metrics randomly or based on formulas                                      |

Notice that Telemetry Providers are shared across all the workspaces within the same Akamas Studio installation, and only users with administrative privileges can manage them.

Click on the provider name in the table above for additional details on how to create a telemetry provider of the desired type and the corresponding telemetry instance that will use it. Instructions to generate generic telemetry instances are also referenced in page[Telemetry Instance template](/akamas-docs/reference/construct-templates/telemetry-instance-template.md) . This page, in fact, lists configuration options that are common to all telemetry providers instances (such as `defaultValue` ). For specific providers and providers instance, instead, refer to the links in the table above


---

# 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/integrating/integrating-telemetry-providers.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.