Manage Prometheus extensions
Dynatrace provides you with a framework that you can use to extend your observability into data acquired directly from a Prometheus endpoint. With it, you can bring the Prometheus data into Dynatrace at scale and in context with all other data.
- To take full advantage of the Dynatrace Prometheus extension, you need a OneAgent on the monitored box, but it can also work in an agentless manner.
- Check our Software intelligence hub to see if your technology is already covered by a preexisting extension. If this is not the case, you can easily build your own Dynatrace Prometheus extension.
Before you begin
Decide which of your hosts will provide the Prometheus data for the extension.
Prometheus extensions can run locally on a OneAgent (recommended) or remotely on an ActiveGate.
- When run locally, the extension connects to the Prometheus interface automatically. Make sure the Extension Execution Controller (EEC) is enabled at the environment or selected host level. For more information, see Extension Execution Controller.
- When monitored remotely, the ActiveGates belonging to an ActiveGate group that you'll designate for remote monitoring need to be able to connect to the host where Prometheus metrics originate.
Add extension to environment
Dynatrace Hub provides a unified workflow to enable and manage extensions that ingest Prometheus data into your Dynatrace environment.
- From the Dynatrace menu, go to Dynatrace Hub.
- Search for a Prometheus extension. You can use the Prometheus keyword to filter the Hub tiles. Select the tile you're interested in.
- Select Add to environment. This creates the environment configuration for your extension, thus enabling the extension in your environment.
- Select Add monitoring configuration.
Define monitoring source
Decide how you want to monitor your host: local or remote.
- Select a host or a host group where you want to run the extension. The host needs to be running a OneAgent that is enabled to run extensions.
- Select Next step.
- Select Add endpoint.
- Define the Prometheus endpoint providing metrics and authentication details. For more information on supported authentication schemes, see Authentication. Authentication details passed to Dynatrace when activating monitoring configuration are obfuscated and it's impossible to retrieve them.
- Select Monitor remotely without OneAgent.
- Define the Prometheus endpoint providing metrics and authentication details. For more information on supported authentication schemes, see Authentication
- Select Next step.
- Select the ActiveGate group to determine which ActiveGates will run the extension. When done, select Next step.
Select Define to configure optional advanced properties:
Timeout in seconds: The maximum time (in seconds) to wait to return data. Default = 10 seconds.
Retries: The maximum number of retries for a query if it fails (total time for a query is
retries). Default = 0 retries.
Autodiscovery is a feature that automatically resolves the DNS endpoints. If autodiscovery is defined, the URL becomes the DNS name.
Select Define to configure DNS endpoints:
Auto discovery type: Only the
DNS type: The type of DNS query to perform. Only the
Atype is available, which corresponds to IPv4 addresses.
DNS port: Specifies the port assigned to all IPs resolved by the DNS.
DNS refresh interval (s): Sets interval time in seconds to the frequently changing IP addresses.
Provide final configuration details.
- Description Text explaining details of this particular monitoring configuration. When troubleshooting monitoring, this can give your teams details of this particular monitoring configuration.
- Feature sets In highly segmented networks, feature sets can reflect the segments of your environment. You can use them to limit your monitoring to particular segments. Feature sets are predefined for each extension. For more information, see Prometheus data source reference.
When done, select Activate.
Monitoring configuration as JSON
The extension activation wizard contains a dynamically updated JSON payload with your monitoring configuration. See Extensions 2.0 lifecycle to learn how to use it to activate an extension using the Dynatrace API.