Why Alerting-Profile's Configuration Recommended To Utilize Tags configured from Manual-Tagging (instead of Auto-Tagging)?

[waikeat_chan]

Anyone know the rationale or reason behind?

This really puzzle me because whether we are talking about a tool called 'Dynatrace' or any other tools, I suppose rely heavily on manual-tag is an anti-pattern and we should follow the best practice of rely on auto-tag (especially in a large-environment or cloud-native era, which is definitely where the society/industry is heading to)

I now am facing an issue where problems for some reason just doesn't parked to the right alerting-profile (and hence, doesn't parked to the right notification and causing customer doesn't receiving any alerting-email and missed out their Production incident). And then Dynatrace is telling me to try and achieve the same thing in Alerting Profile BUT WITHOUT using Auto-Tag......

Best Regards,

Wai Keat

[AntonPineiro]

Hi,

Which problem is creating Davis? It base or a custom event?

Which entity is impacted by problem? Host, process?

Best regards

[Vanguard]

@waikeat_chan I totally agree, this "recommendation" does not make sense. We are relying heavily on auto-tagging. It is the fundamental automation mechanism for almost everything!:
Auto-Tag -> Entities get included in Management Zones -> Alerting Profiles -> Notifications etc
And most of our tagging rules are based on the hosts hostgroup naming convention.