We are moving to AWS cloud and using Dynatrace SaaS. We are running into the issue of having to setup an alert profile for each different piece of technology to do problem notification. We are just starting and have over 40 alert profiles. This will quickly become to cumbersome to manage. However; to make this more usable, I would like to use the contents of the custom tag [AWS]cost-center as the routing key. Currently in the VictorOps integration it looks like the routing key has to be hard coded and then related to an alert profile. Is there another way to do this? Has anyone done this already (or something similar)? Is there enough interest in this to change it to an RFE?
Solved! Go to Solution.
Unfortunately, that's not possible as of today. The use of placeholders within fields other than within the message field is so far not supported. What is upcoming next to help on the problem filtering challenge is filter by Management Zone. Which means that if you did set up ownerships on MZs you will be able to use those within your alerting profiles for routing purposes. Maybe that helps you implement your use-case?
Our issue is that different areas will be sharing the same Infrastructure (kubernetes) so Multiple MZs will contain the same infrastructure the the services use. It is the application and services that will be different. So it helps some. Should I formalize this a little more and create and RFE