Hey @Babar_Qayyum - I dont think we can target specific traces or requests to have tags.
We can apply tags to the top-level service either manually or automatically using Monitored Entity Rules or Entity Selectors. However, tagging does not extend beyond that layer.
The closest alternative at lower levels is a Request Attribute. With Request Attributes, you define a key:value pair similar to a tag, but there are more constraints. Specifically, if you want a dynamic value, that value must already exist within the trace data. Unlike tags, you cannot freely assign arbitrary values.
For Metric Events, you can include the associated tags of the alerting entity as Event Properties. For example, if a host triggers a custom Metric Event, all applicable tags on that host can be included in the event payload. This capability also applies to the new Davis Anomaly Detectors, now renamed Anomaly Detection.
In practice, this means you can create dynamic key:value pairs within alerts by leveraging Event Properties. You can also create a manually defined "tag-like" structure within the alert configuration itself. However, manually defined values are static. Unless the value uses a dynamic placeholder (for example, values enclosed in {}), the key:value pair will remain the same for every alert and will not change based on the alerting entity.
-Chad
