Documentation Plugins Dynatrace data source Query editor

Dynatrace query editor

Grafana provides a query editor for the Dynatrace data source, which is located on the Explore page. You can also access the Dynatrace query editor from a dashboard panel. Click the menu in the upper right of the panel and select Edit.

This document explains querying specific to the Dynatrace data source. For general documentation on querying data sources in Grafana, refer to Query and transform data. For options and functions common to all query editors, refer to Query editors.

The query editor allows you to create multiple Dynatrace query types.

Query

Grafana supports the following Dynatrace query types, depending on the kind of data you want to query:

• Grail
• Metrics
• Problems
• Problems V2
• USQL
• Logs
• Audit Logs
• Management Zones
• Direct API Access
• SLO
• Events
• Synthetic
• Tokens

Grail query type

Grail is Dynatrace’s unified data lakehouse that stores all your observability data in one place. With Grail, you can query logs, metrics, events, spans, and business analytics data using DQL (Dynatrace Query Language). Grail requires a Platform token to be configured.

DQL uses a pipe-based syntax that lets you chain operations together to fetch, filter, and transform data. Queries start with a fetch command to retrieve a data type, followed by additional commands separated by pipes (|).

What you can query:

• logs — Application and infrastructure log data
• metrics — Time-series performance and monitoring data
• spans — Distributed tracing data for analyzing request flows
• events — System events, deployment events, and custom events
• bizevents — Business events and user session analytics

DQL Query

Enter your DQL query to retrieve data from Grail. The query should start with a fetch command specifying the data type you want to query.

Example queries:

Fetch error logs from the last hour:

dql Copy

fetch logs
| filter loglevel == "ERROR"
| sort timestamp desc
| limit 100

Query metrics with aggregation:

dql Copy

fetch dt.metrics
| filter metric.key == "builtin:host.cpu.usage"
| summarize avg(value), by: {host.name}

Analyze spans for a specific service:

dql Copy

fetch spans
| filter service.name == "checkout-service"
| filter duration > 1s
| summarize count(), avg(duration), by: {span.name}

For more information about DQL syntax and available commands, refer to Dynatrace Query Language in the Dynatrace documentation.

Metrics query type

The Metrics query type allows you to query Dynatrace metrics using either a visual builder or by writing metric selector expressions directly.

Mode - Select how you want to build your metric query:

• Builder - Use a visual interface to select metrics, aggregations, transformations, and filters. Recommended for most users.
• Code - Write metric selector expressions directly for advanced querying. Supports the full Dynatrace metric selector syntax.

Management Zone - (Optional) Select one or more management zones to filter results. Only metrics from entities within the selected management zones are returned.

Builder mode options

The following options are available when using Builder mode:

Metric - Select the metric you want to query. Use the search field to find metrics by name. Click the Refresh button to reload the metric list from Dynatrace.

Aggregations - Select the aggregation function to apply to the metric data. Click the aggregation value to change the type, or click + to add multiple aggregations. Common aggregations include avg, sum, min, max, and count.

Transformations - Apply transformations to modify the metric data. Click + to add a transformation. The names transformation is applied by default to display human-readable dimension names. For information about available transformations, refer to Metric selector transformations in the Dynatrace documentation.

Filters - Filter metric results by dimension values. The plugin dynamically loads available filter options based on the selected metric.

• To add a filter, click + next to Filters, select a dimension to filter on, choose an operator, and select a value.
• Use Filter Groups to create complex logical comparisons by combining multiple filters with AND/OR operators. For most use cases, filter groups are not required.
• When filtering by Tags, Dynatrace always uses AND logic regardless of the conjunction selected.

Alias - Customize the display name for the metric series. You can use static text or dynamic alias variables:

Additional dynamic aliases based on dimensions (such as Host or Service) are available depending on the selected metric.

Code mode options

The following options are available when using Code mode:

Expression - Enter a Dynatrace metric selector expression. This field supports the full metric selector syntax, including metric IDs, transformations, filters, and aggregations. For syntax details, refer to Metric selector in the Dynatrace documentation.

Alias - Customize the display name for the metric series, using the same static and dynamic alias variables available in Builder mode.

Series limit

Limit - Limits the number of metric series returned. The default is 1000. Use this to prevent queries from returning too much data.

Problems query type

The Problems query type retrieves problem data from your Dynatrace environment using the Problems API v1. For additional information, refer to Problems API - GET feed in the Dynatrace documentation.

Problem Query Type - Select the Problems API endpoint to use. Currently, only the Feed option is available, which returns a chronological feed of problems detected in your Dynatrace environment over the selected time range.

Status Filter - Filter problems by their lifecycle status:

Impact Filter - Filter problems by their business impact level:

Severity Filter - Filter problems by their severity classification:

Tags - Filter problems by Dynatrace tags. Enter one or more tags to return only problems associated with entities that have the specified tags. Press Enter after each tag to add it to the filter.

Expand Details - Toggle on to include additional contextual information in the results, such as related events, root cause analysis, and impact details. This provides a comprehensive view of each problem but may increase response size and query time.

Problems V2 query type

The Problems V2 query type retrieves problem data using the current Dynatrace Problems API v2. This is the recommended query type for querying problems, as it provides more filtering options and better performance than the legacy Problems query type.

For additional information, refer to Problems V2 API in the Dynatrace documentation.

Fields - (Optional) Select additional properties to include in the response. Available fields include:

ProblemSelector - (Optional) Define filters to narrow down which problems to retrieve using Dynatrace selector syntax. Separate multiple criteria with commas.

Example selectors:

• status("OPEN") - Return only open problems
• severityLevel("AVAILABILITY","ERROR") - Return problems with specific severity levels
• impactLevel("SERVICE") - Return problems affecting services
• managementZoneIds("123456789") - Return problems in a specific management zone

For a complete list of selector options, refer to problemSelector parameters in the Dynatrace documentation.

EntitySelector - (Optional) Filter problems to those affecting specific entities using Dynatrace entity selector syntax.

Example selectors:

• type("HOST") - Return problems affecting hosts
• entityId("HOST-1234567890ABCDEF") - Return problems for a specific entity
• tag("environment:production") - Return problems for entities with a specific tag

For a complete list of entity selector options, refer to Entity selector in the Dynatrace documentation.

Sort - (Optional) Specify how to sort the returned problems. Enter a comma-separated list of fields with optional sort direction.

Example sort values:

• status - Sort by status ascending
• -startTime - Sort by start time descending (newest first)
• severityLevel,-startTime - Sort by severity, then by start time descending

For a complete list of sort properties, refer to sort parameter in the Dynatrace documentation.

USQL query type

The USQL query type allows you to query user session data (real-user monitoring data) from Dynatrace using the User Session Query Language (USQL). Use this query type to analyze user behavior, session performance, and digital experience metrics.

For additional information, refer to:

• Custom queries, segmentation, and aggregation of session data
• User sessions API

USQL Query - Enter your USQL query in the text area. USQL uses a SQL-like syntax to query user session data.

Example queries:

• SELECT * FROM usersession LIMIT 100 - Return the first 100 user sessions
• SELECT userId, duration, userActionCount FROM usersession WHERE duration > 60000 - Return sessions longer than 60 seconds
• SELECT AVG(duration) AS avgDuration FROM usersession GROUP BY city - Average session duration by city
• SELECT COUNT(*) FROM useraction WHERE name = "Loading of page /home" - Count specific user actions

For complete USQL syntax, refer to USQL reference in the Dynatrace documentation.

Add deeplink fields - Toggle on to include deeplink fields in the result set. These fields contain direct URLs to the corresponding data in Dynatrace, enabling you to:

• Create clickable links in table panels that navigate to Dynatrace
• Add “View in Dynatrace” buttons to your dashboards
• Quickly jump from Grafana visualizations to detailed Dynatrace views

After enabling this option, use Grafana transformations to format and display the deeplink values as needed.

Logs query type

The Logs query type retrieves log data from Dynatrace Log Monitoring v2. Use this query type to search and analyze application and infrastructure log data within Grafana.

For additional information, refer to Log Monitoring API in the Dynatrace documentation.

Query - Enter a log search query using the Dynatrace search query language.

Example queries:

• loglevel="error" - Return all error-level logs
• log.source="/var/log/syslog" - Return logs from a specific source
• loglevel="error" OR loglevel="warn" - Return error and warning logs
• log.source="/var/log/syslog" AND loglevel="error" - Combine multiple filters

Sort - Select the order for returned log entries. The dashboard’s time range is applied automatically.

Audit Logs query type

The Audit Logs query type retrieves security-relevant and configuration-change events from the Dynatrace Audit Log API. Use this query type to track administrative actions, not application or system logs.

For additional information, refer to Audit logs API in the Dynatrace documentation.

Filter - (Optional) Enter filter criteria to narrow down audit log entries. You can filter by the following criteria:

Combine multiple filters by separating them with commas: eventType("CREATE","UPDATE"),category("CONFIG")

Sort - Select the order for returned audit log entries. The dashboard’s time range is applied automatically.

Management Zones query type

The Management Zones query type retrieves a list of all management zones configured in your Dynatrace environment. Management zones are used to define visibility and access boundaries within Dynatrace, allowing you to segment your monitored environment.

This query type returns management zone names and IDs, which can be useful for:

• Building dashboards that display management zone information
• Using management zone data in transformations
• Creating template variables for filtering other queries

For more information about management zones, refer to Management zones in the Dynatrace documentation.

Direct API Access query type

Use Direct API Access when you need to query Dynatrace API endpoints that are not covered by the standard query types. This mode gives you full access to Dynatrace’s REST APIs and allows you to parse the response using JSONPath.

API Endpoint - Enter the API path beginning with the version segment.

Fields - Select how to parse the API response:

Parse Individual Fields options

When Parse Individual Fields is selected, configure the following options for each field you want to extract:

Field - Enter a JSONPath expression that identifies the value to extract from the API response.

Type - Specify how the extracted value should be interpreted:

Alias - (Optional) Custom name for the extracted field. If left blank, the JSONPath expression becomes the column name.

Nullable - Toggle on to allow null values when the JSONPath expression does not match anything in the API response. This helps avoid parsing errors if data is missing for some items.

Click + to add more fields, or - to remove a field.

SLO query type

The SLO query type retrieves Service Level Objectives from Dynatrace. SLOs measure how well a service is meeting its reliability targets, including error budgets, status, and burn rates.

For additional information, refer to SLO API in the Dynatrace documentation.

SloSelector - (Optional) Filter which SLOs to retrieve using Dynatrace selector syntax.

Example selectors:

• name("my-slo-name") - Filter by SLO name
• id("slo-id") - Filter by SLO ID
• status("SUCCESS") - Filter by status (SUCCESS, WARNING, or FAILURE)

Sort - (Optional) Control the ordering of returned SLO results. You can sort by name (ascending or descending) or by status.

TimeFrame - (Optional) Set the evaluation period for calculating SLO values. The default is CURRENT. You can use relative timeframes like -1d or 1h.

Demo - (Optional) Toggle to retrieve demo/example SLOs instead of production SLOs. Useful for testing and training. Default is FALSE (production SLOs).

Evaluate - (Optional) Toggle to calculate and return current SLO values. When TRUE (default), SLOs include calculated metrics like error budget, status, and burn rate. Set to FALSE to return only SLO definitions.

EnabledSlos - (Optional) Filter SLOs by their enabled/disabled state:

ShowGlobalSlos - (Optional) Control whether to include global SLOs (not assigned to any management zone):

Events query type

The Events query type retrieves events from your Dynatrace environment using the Events API v2. Events include deployment markers, configuration changes, custom events, and other significant occurrences.

For additional information, refer to Events API v2 in the Dynatrace documentation.

EventSelector - (Optional) Filter which events to retrieve using Dynatrace selector syntax. The dashboard time range is applied automatically.

Example selectors:

• eventType("CUSTOM_DEPLOYMENT") - Filter by event type
• eventType("CUSTOM_INFO","CUSTOM_ALERT") - Filter by multiple event types
• status("OPEN") - Filter by event status

EntitySelector - (Optional) Filter events to those affecting specific entities.

Example selectors:

• type("HOST") - Events affecting hosts
• entityId("HOST-1234567890ABCDEF") - Events for a specific entity
• tag("environment:production") - Events for tagged entities

Synthetic query type

The Synthetic query type retrieves synthetic monitoring data from Dynatrace. Use this query type to monitor simulated user interactions and API calls for availability and performance testing.

For additional information, refer to Synthetic API in the Dynatrace documentation.

Common use cases:

• Monitor synthetic test results and availability percentages
• Track synthetic test execution times and response times
• View synthetic monitor locations and configurations

MonitorSelector - (Optional) Filter which synthetic monitors to retrieve.

Example selectors:

• type("HTTP") - Filter by monitor type
• name("Production Health Check") - Filter by monitor name
• enabled(true) - Filter by enabled state

EntitySelector - (Optional) Filter synthetic data to specific entities or locations using Dynatrace entity selector syntax.

Tokens query type

The Tokens query type retrieves information about API tokens configured in your Dynatrace environment. Use this query type for token auditing and management.

For additional information, refer to Access tokens API in the Dynatrace documentation.

Common use cases:

• Audit API token usage and permissions
• Monitor token expiration dates
• Track token creation and modification
• Identify unused or overprivileged tokens

TokenSelector - (Optional) Filter which tokens to retrieve.

Example selectors:

• owner("john.doe@example.com") - Filter by token owner
• name("grafana-token") - Filter by token name
• scopes("metrics.read") - Filter by token scopes