After assigning tags, start using them to filter and group your data in your Datadog platform.
The Events Stream shows all the events that have occurred in your environment over the time period specified. Use tags to filter down the event list and focus on a subset of events. Enter
tags: followed by a tag to see all the events that come from a host or an integration with that tag. The example below is used to search for the tag
tags:service:coffee-house. To search multiple tags, separate each tag by a comma:
Use tags to filter metrics to display in a dashboard graph, or to create aggregated groups of metrics to display. To filter the metrics to display, enter the tag in the from textbox. You are now looking at a chosen metric over all sources that have that particular tag assigned (
service:coffee-house in the example below).
To create an aggregated group using tags, enter the key part of the tag in the avg by textbox. For example, if you have a timeseries graph showing a metric tagged with the key
service, such as
service in the avg by textbox to show one line for each
service tag value. Each line represents the average metric value across all sources that share that
service tag value.
Tags can also be used to overlay events on the dashboard. This works the same way as in the Events Stream.
tags: followed by the tag. The matching events are overlaid as vertical bars on the graph. The example below uses
Use template variables to save time switching the from tag on graphs in your dashboard. In the example below,
service is used to represent the
service tag key. To use the template variable, add the
$service template variable in the from textbox of your graph query.
Here is an example of tags using the timeseries chart editor. For the first screenshot, no tags have been applied, and the average CPU usage across all hosts is displayed:
Next, the editor is updated to include a tag (
region:eastus) in the from textbox that enables Datadog to look at CPU usage across the US East region. The
region tag is used as an example here, but you could use any arbitrary tag sent to your Datadog platform, including
Finally, the second empty field (the avg by textbox) is used to show an individual timeseries line for each
host. Server CPU is displayed for individual hosts running in the US East region.
If needed, add additional tags to narrow down the scope even further—for example, hosts in
env:production. Tags can be used throughout Datadog and be applied to all core elements (metrics, traces, and logs).
To filter the Host Map, Infrastructure List, Containers, and Processes, enter a tag in the Filter by textbox at the top of the page. Hosts and containers can be grouped by tag key using the Group by textbox. If you enter
service in the group box, you see each service as a group heading.
Under this section, use tags to filter or group Hosts:
Here are the filter and group by textboxes on the Infrastructure List page:
Here are the filter and group by textboxes on the Live Containers page:
Here are the filter and group by textboxes on the Live Processes page:
To filter monitors by assigned tags, use the search bar or facet checkboxes. The search bar format is
tag:<KEY>:<VALUE>, for example
tag:service:coffee-house. Note: monitor tags are different and separate from metric tags.
When creating a monitor, use metric tags in the:
from textbox to limit the monitor scope to only metrics that have those tags.
excluding textbox to remove the corresponding metrics from the monitor scope.
avg by textbox to transform the monitor into a multi-alert monitor on each tag value.
To filter downtimes by monitor tag, type the tag name in the search bar, for example
Use tags in the Metrics Explorer to filter metrics over tags or display multiple graphs by tag key. The example below graphs a metric over
service:coffee-house and displays one graph per
Some integrations such as AWS, Google Cloud, and Azure allow you to optionally limit metrics using tags. In the specific integration tile, use a comma separated list of tags in the form
This defines a filter used while collecting metrics. Wildcards such as
? (for single characters) and
* (for multiple characters) can also be used. Only hosts that match one of the defined tags are imported into Datadog. The rest are ignored. Hosts matching a given tag can also be excluded by adding
! before the tag.
For Trace Search, filter traces with tags using the search bar or facet checkboxes. The search bar format is
<KEY>:<VALUE>, for example
service:coffee-house. For advanced search, see the trace search page.
When creating a Notebook graph, limit metrics by using tags in the from textbox. Additionally, group metrics by using tags in the avg by textbox. In the example below, metrics are limited to
service:coffee-house and grouped by
To exclude tags, use
</> to edit the text then add the tag in the form
!<KEY>:<VALUE>. In the example below,
service:coffeehouse is excluded using
For Logs Search, Analytics, Patterns, and Live Tail filter logs with tags using the search bar or facet checkboxes. The search bar format is
<KEY>:<VALUE>, for example
service:coffee-house. For advanced search, see the log search page.
Additionally, tags are used to filter a logs Pipeline. In the example below, the pipeline filters logs by the tag
Tags can be used in various ways with the API. See the list below for links to those sections: