Latest Dynatrace Preview Dynatrace version 1.303+
Leverage entity-lookups in segments to filter observability signals by properties of monitored entities.
The following procedure shows the current state of entity-lookups in Dynatrace segments. Some details of the configuration flow may change with upcoming improvements.
This article is intended for admins aiming to configure segments using entity-lookups, in order to upgrade existing management zones to new Dynatrace segments.
In this article, you'll learn how entity-lookups can help to include observability signals by properties of their emitting entities.
storage:filter-segments:read
and storage:filter-segments:write
permissions. To learn how to set up the permissions, see Permissions in Grail.Filter step in DQL queries fetching signal data types, for example, logs
, performing a lookup
to monitored entities referenced by those signals.
Include metrics and spans of tagged services
Analyze metrics of services in Notebook
Analyze spans of services in Notebook
Entity-lookups for signals are configured through checkboxes in any entity include. To include metrics and spans of services with tag bookstore:client
tags
tags = bookstore:client
)For entity properties already physically present as fields of signal records, including signals directly filtering for that field should be the preferred option instead.
You can analyze metrics and spans in different apps. To query for those in Notebooks
dt.service.request.response_time
fetch spans
Previewfetch spans
is currently in Preview and only accessible to selected customers. If you would like to share feedback or ideas, please join our dedicated Community user group, or reach out to your Customer Success Manager.
For more information, see
fetch spans
to query for spansYou've created a segment for tagged services, including metrics and spans emitted by those services. You've additionally seen how to analyze those metrics and spans of those services in Notebooks using entity-lookups with Dynatrace segments.