Tags in metric events

[gustavodutra]

Is it possible to create a tag for metrics events? I created an event based on the metric "builtin:cloud.aws.alb.connections.new," and it's working fine. Here is an example image:

But I need to add a tag to this item so that when I receive an alert, it can be forwarded to ServiceNow to start an incident. However, I am unable to add a tag to this type of event, and I would like to know if there is any way to do this.

My metric event:

builtin:cloud.aws.alb.connections.new:filter(and(or(in("dt.entity.aws_application_load_balancer",entitySelector("type(aws_application_load_balancer),entityName.equals(~"alb-private-*****~")"))))):splitBy():sort(value(auto,descending)):limit(20)

[AntonPineiro]

Hi,

Not sure if you can add a tag to a metric event. You can always adding metric event to alerting profile (base on properties, title or another event filter.

Best regards

[gustavodutra]

Could you give me an example of how to do this?

[Peter_Youssef]

Hello @gustavodutra 

PFA Doc URL:

• https://docs.dynatrace.com/docs/discover-dynatrace/platform/davis-ai/anomaly-detection/set-up-a-cust...
• https://docs.dynatrace.com/docs/discover-dynatrace/platform/davis-ai/anomaly-detection/set-up-a-cust...
• https://www.youtube.com/watch?v=NVuiTwOYHQA

Hoping it helps.

BR,

Peter

[VenkataSainath]

You can try to add the tags to filter entity, it may use the tags in problem out put. 

[gustavodutra · Accepted solution]

Hi everyone,

I wanted to inform you that I was able to assign a tag to a custom event by following the steps below:

1. Go to Settings > Alerting.
2. Select Problem alerting profiles.
3. Choose the desired alerting profile.
4. Expand the profile settings.
5. Look for "Event Filters".
6. Click on Add event filter.
7. Configure the filter as needed for the alert.

Additionally, I encountered an issue with the metric that was previously configured. It had the following fields:

Previous Metric Selector:

builtin:cloud.aws.alb.connections.new:filter(and(or(in("dt.entity.aws_application_load_balancer",entitySelector("type(aws_application_load_balancer),entityName.equals(~"alb-private-******~")"))))):splitBy():sort(value(auto,descending)):limit(20)

The issue was with the use of the splitBy():sort(value(auto,descending)):limit(20) command, which seemed to cause a conflict. After removing it, the alert started working correctly.

Updated Metric Selector:

builtin:cloud.aws.alb.connections.new:filter(and(or(in("dt.entity.aws_application_load_balancer",entitySelector("type(aws_application_load_balancer),entityName.equals(~"alb-private-******~")")))))

Now, the configuration is working properly, and alerts are being generated as expected.

If anyone has questions or needs further information, feel free to reach out!

Best regards,
Gustavo 

[Peter_Youssef]

Hi @gustavodutra 

Thanks for the updates and sharing the results.

Good Job.

BR,

Peter