https://community.dynatrace.com/t5/Open-Q-A/Manual-OR-Automatic-tags-for-service-methods-and-metric-events/m-p/303365#M39397 <P>Hey&nbsp;<a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/22017">@Babar_Qayyum</a>&nbsp;- I dont think we can target specific traces or requests to have tags.&nbsp;<BR /><BR /></P><DIV><P>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.</P><P>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.</P><P>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.</P><P>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.</P></DIV> Mon, 17 Aug 2026 15:08:44 GMT ChadTurner 2026-08-17T15:08:44Z https://community.dynatrace.com/t5/Open-Q-A/Manual-OR-Automatic-tags-for-service-methods-and-metric-events/m-p/300524#M39161 <P>Dear All,</P> <P>Could you please let me know if there is a method to tag specific requests/or service methods and metric events?</P> <P>Regards,</P> <P>Babar Qayyum</P> Fri, 12 Jun 2026 07:20:33 GMT https://community.dynatrace.com/t5/Open-Q-A/Manual-OR-Automatic-tags-for-service-methods-and-metric-events/m-p/300524#M39161 Babar_Qayyum 2026-06-12T07:20:33Z https://community.dynatrace.com/t5/Open-Q-A/Manual-OR-Automatic-tags-for-service-methods-and-metric-events/m-p/303365#M39397 <P>Hey&nbsp;<a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/22017">@Babar_Qayyum</a>&nbsp;- I dont think we can target specific traces or requests to have tags.&nbsp;<BR /><BR /></P><DIV><P>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.</P><P>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.</P><P>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.</P><P>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.</P></DIV> Mon, 17 Aug 2026 15:08:44 GMT https://community.dynatrace.com/t5/Open-Q-A/Manual-OR-Automatic-tags-for-service-methods-and-metric-events/m-p/303365#M39397 ChadTurner 2026-08-17T15:08:44Z