# Integrating Telemetry Providers

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

Notice that Telemetry Providers are shared across all the workspaces within the same Akamas 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](https://docs.akamas.io/akamas-docs/reference/construct-templates/telemetry-instance-template "mention") . 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