Facets are quick filters for log data. They correspond to log attribute key-value pairs detected in your environment and are grouped by facet categories. The most important DQL field IDs are grouped by default in predefined categories. Facets also help you estimate the amount of log data corresponding to each attribute.
To query logs in your environment with facets
Go to
Logs.
Expand facet groups like Core or Log source.
Expand the facet relevant for your query, like Status.
Select values relevant for your query, like Error and Warning.
Observe how the filters are generated in the filter field.
Select as many facets as needed for your query.
Within a single facet, selected values are combined using the OR operator. This means logs matching any of the selected values for that facet will be included.
Between different facets, values are combined using the AND operator. This means logs must match at least one value from each selected facet to be included.
Select Run query to see logs from your environment based on your filter.
You can enrich logs at ingest with primary Grail tags and query them via primary_tags.* fields. In
Logs, primary Grail tags appear as a dedicated Primary tags facet group, so you can filter logs by tag key-value pairs without writing DQL queries.
To filter logs using primary Grail tags
team) rather than the full field name (primary_tags.team).primary_tags.team = "payments" query in the filter field.Enter primary_tag in the filter field to see autosuggestions for primary Grail tag keys.
Keep the following in mind when filtering with primary Grail tags:
When you open a single log record, primary_tags.* fields are grouped under a dedicated Primary tags section in the record details panel. This keeps primary Grail tag fields separate from core fields (Fields section) and topological context (Topology section), so you can quickly inspect which primary Grail tags a record carries without searching through all fields.
AWS, Azure, GCP, and Kubernetes tags that haven't been promoted to primary Grail tags are hidden facets by default, grouped by cloud source. You can unhide them as needed.
To display cloud or Kubernetes tags as facets
Once unhidden, these facets work the same way as primary Grail tags: expand the facet group, select values, and observe the generated filter.
The following table lists the available facet groups with their corresponding field prefixes and examples.
| Facet group | Field prefix | Example |
|---|---|---|
AWS |
|
|
Azure |
|
|
GCP |
|
|
Kubernetes namespace annotations |
|
|
Kubernetes namespace labels |
|
|
Kubernetes pod annotations |
|
|
Kubernetes pod labels |
|
|
Kubernetes workload annotations |
|
|
Kubernetes workload labels |
|
|
To get a sense of how many logs with specific attributes there are in your environment
The numbers displayed for each facet value represent the approximate number of logs based on your last query filters. If you see the '~' symbol, it indicates that Dynatrace is using sampling when reading log data to improve responsiveness.
Example:
k8s.namespace.name = "astroshop" status = "Error".k8s.container.name.To manage which facets of your environment are displayed
If you have previously modified the facets, to revert to the default settings for facets in your environment