Depending on the size of your environment, odds are you are using automatic tagging. Automatic tagging is great but also can have its downfalls. Over the last several updates, Dynatrace has increased the functionality of its tagging.
- Tagging Entity Names
With larger organizations adopting new technologies and methodologies, its important to provide tags on these entities. For example. Lets say we have our Application "EasyTravel" but your organization is shifting from being hosted on VMWare to AWS. As a result, you have two different EasyTravel Apps now "AWS EasyTravel" and "VM EasyTravel" you can use custom regex to pull the dynamic values of the Application Names. I like to use www.regex101.com to test all my regex:
Then we just supply that in: by adding the /<RegexCode>}
Once you create and save this rule, it will apply to the entire scope. You can also use this for Environment as well by just updating your Regex:
Using dynamic regex tagging allows you to create one rule that will provide the targeted value of a set entities across the entire scope! So no more single rules stating if the name contains NP1, tag it with NP1 and so on.
The possibilities are endless and can be used for Hosts, Processes, Services, Applications, Synthetics, Properties and so much more!
Solved! Go to Solution.
Hi Chad, I have to admit that you are an iconic person on our Team for keeping us abreast with Dynatrace, assisting and answering our questions as always! Thank you and it's very much appreciated!
This is a fantastic tip, I have been using/suggesting this for a while now and I came here to post about it on the community as a tip but found you had already beaten me to it by a whole year! 😁
I have also found it to be really helpful for tagging based on the host groups if you can decide on a naming scheme for host groups. You can then propagate environments, locations and other tags throughout your environment making it easier to navigate!