DataDog Monitors and Filters

  • Updated

Helpful definitions:

  • Monitor: A tool or system that tracks and records the values of specific metrics over time. Monitors are used to visualize the current state and trends of the metrics, trigger alerts based on thresholds, and provide a historical view of the performance and utilization of cloud resources. Example monitor:
  • Metric: A measurable value used to monitor the performance and utilization of cloud resources such as compute, storage, and network. Example metric:
  • Tag: A metadata label that can be applied to resources such as virtual machines, storage volumes, and network interfaces. Tags can be used to categorize, organize, and identify resources, and can also be used to associate relevant information with specific resources. Example tag filter:

Our monitoring tests respect tag filtering. What does this mean?

  • Example: the following monitor only watches resources with the tag region = us-east-1.
  • We read and evaluate the tag filters that exist on all metric monitors.
  • For each resource tracked in Vanta it must be available in at least one monitor. That means it must pass the tag filter on at least one metric monitor.

What we support

  • Tags that exist on the base resources (ex: on a queue in AWS)
  • Tags that DataDog creates for resources. Exhaustive lists: AWS, GCP, Azure
  • Boolean filtered queries (AND, OR, IN, !) link
  • Wildcards (*) link

What we do not support

  • "Not" leading a filter (ex: not env:prod). We support all other uses of NOT. There is a workaround, which is using (!env:prod). You may need to use parentheses as DD does not support symbolic boolean operators with functional boolean operators. More information.
  • Tags applied at the Datadog level (ex: tags you apply to a Datadog host)


Was this article helpful?

Have more questions? Submit a request