Dynatrace automatically captures important metrics for services with no configuration required. You might need additional business or technical metrics that are specific to your application. These metrics can be calculated and derived based on a wide variety of available data within the captured distributed trace. You can also split these metrics by multiple dimensions, for example, a requests attribute or an HTTP method.
OpenPipeline metric extraction now replaces calculated service metrics as the method to create additional service business or technical metrics. To read more about metric extraction, see Extract metrics from spans and distributed traces. If you're an existing customer, you can still use them until we deprecate them. If you're a new customer, you won't be able to create calculated service metrics anymore.
More flexible metric creation from spans—with OpenPipeline, metrics are no longer limited to support at most 100 dimension values (“top X”).
Better scale and performance—platform-scale ingest and stream processing built to go beyond petabytes; no more 500 calculated service metrics limit per tenant.
Security, cost management, and data governance—filter and mask sensitive or unnecessary fields; assign cost center usage to specific metrics; route data to specific Grail buckets with controlled retention durations.
remainder dimension. The remainder filter condition allowing you to filter on this remainder dimension.Go to Settings > Server-side service monitoring > Calculated service metrics > Create new metric.
Enter the name for the metric.
The name and the calc:service. prefix are added automatically to the metric key. Note that once a metric is enabled in Grail the prefix is automatically changed to service.
Choose the metric source from the Metric source list.
Optional Select the management zone. The new metric will be restricted to data from this zone.
Provide conditions to define which requests are included in the calculation.
If you provide several conditions, all conditions must be fulfilled to use the metric.
Select Add condition.
Select the attribute to be checked.
Select the operator of the condition.
If needed, specify the reference value.
Classic metric Preview shows the list of services to be included to the custom metric and the estimation of DDU consumption.
Preview only considers management zone and conditions based on service attributes. These attributes are marked with [Service property] in the attribute list.
Optional Add dimension to your new metric.
The top X value limit applies to the Classic metric only, not to the Grail metric.
Review the metric source and dimension names. They will be used in the UI and API. Once a metric is created, you can't change them.
Select Save metric.
When a placeholder is not available, you can create a custom placeholder. All custom placeholders must be used in the dimension value pattern, alternatevely you can delete unused custom placeholders.
You have two methods to extract the value for a placeholder:
Placeholders that are based on request attributes provide three options for value extraction:
To create a custom placeholder
While creating or editing a calculated service metric, select Add custom placeholder.
Enter a name for your placeholder. The name will be used in the Dimension value pattern field.
Select the source for the dimension.
Choose the extraction method.
If the source is a request attribute,
Select Add.
Required Use the newly created placeholder in the dimension value pattern.
Latest Dynatrace
To enable a metric in Grail, turn on Enable on Grail.
The prefix is automatically modified from calc:service. to service.. The metric name and previosuly existing dimension are maintained. Supported placeholders are converted to additional dimensions and new dimensions are added for metrics derived by OneAgent.
For a complete list of available dimensions see Built-in Metrics on Grail - Calculated service metrics.