Overview

Tags are the labels with a key-value pair that you can use for filtering the data for the cloud entities. The tag filtering public API enables DevOps and CloudOps engineers to use the tagging values in Cisco Cloud Observability programmatically. Tags add content and context to an entity. The tag filtering API endpoints allow you to discover and dynamically organize data across the entire observable stack using tags.
You can search, filter, and group topology and MELT (Metrics, Events, Logs, and Traces) data by using tags to analyze the root causes and troubleshoot issues. Use the API tag filtering endpoints, which leverage the flexible data model to get the details per your requirements. You can export the resulting data into third-party solutions.

Filter

You can filter objects such as entities, metrics, and events by comparing their scalar fields or facts with constants. The fields that are of scalar type can be used for filtering the data. Facts are fields that are indirectly associated with the filtered object. For example, attribute or tag of a given name.

Supported Operations

You can use the Query Service API endpoints to fetch filtered data.

Use Cases

You can assign tags in multiple ways depending on the intended purpose. Filtering allows you to express your intent as a UQL payload. Following are top use cases for tags:

• Aggregate metrics Fetch ART metric of a service instance where tag service:payment AND region IN (eu-west-2, eu-east-1) AND env:prod.
• Alerts Fetch all health rule violations between time T and T-30 matching: 'env:prod AND owner:ABC ANDservice:payment`.
• Multi-cloud Fetch all hosts with CPU >90% where tag: aws.region:eu-west-1 OR azure.location:uksouth.
• Entity Agnostic Fetch all resources tagged with: <owner:product> in a K8 cluster.