Primary Grail tags for Synthetic

  • Latest Dynatrace
  • Explanation
  • Published Apr 03, 2026

When configuring a Synthetic monitor of any type, you can apply Primary Grail tags to the monitor. After that, all events and metrics generated by the monitor are enriched with these Primary Grail tags, so you can retrieve:

  • Monitor events related to tagged monitors.
  • Synthetic metrics with data grouped or filtered by Primary Grail tags (for details, see the use cases below).

Constraints

When you apply Primary Grail tags to the monitor, keep in mind the following constraints:

  • Both Key and Value are required.
  • There is a limit of 50 characters for a key, and a limit of 200 characters for a value.
  • There can be only one value per key.
  • There is a limit of 10 Primary Grail tags per monitor.

Use cases

  • Retrieve monitor events related to tagged monitors using the primary_tags.__key__ field.

    Example:

    fetch dt.synthetic.events
    | filter primary_tags.Owner == "OwnerName"
    | filter event.type == "browser_monitor_execution" OR event.type == "http_monitor_execution" OR event.type == "network_availability_monitor_execution"
    | filter result.state == "FAIL"
    | fields timestamp, monitor.name, event.type, primary_tags.Owner, result.state, result.failed_step.name

  • Retrieve Synthetic metrics using the primary_tags.__key__ dimension for grouping and filtering data.

    Examples for:

    • Browser monitor metrics 
      timeseries av =avg(dt.synthetic.browser.availability),
      by: { primary_tags.Owner },
      filter: primary_tags.Owner != "null"
    • HTTP monitor metrics 
      timeseries av =avg(dt.synthetic.http.availability),
      by: { primary_tags.Owner },
      filter: primary_tags.Owner != "null"
    • NAM monitor metrics 
      timeseries av =avg(dt.synthetic.multi_protocol.availability),
      by: { primary_tags.Owner },
      filter: primary_tags.Owner != "null"
Related tags
Digital Experience