Service Mapping with Dynatrace SG: Application Service names change w/ new microservice code
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2025 10:01 AM
We started to Service Map microservices the are collected through Dynatrace's Service Graph. We saw opportunity to pair with Application(microservice owners) to automate Service Mapping as much as possible. Over time the Application Service names (trailing ids LIKE -a1b2e205xyz) and the original App Services stopped being discovered and broke the Service Maps. Dynatrace has Service detection rules — Dynatrace Docs
but the Monitoring team could not get Application Names to be Static.
Service Mapping team is thinking about creating Static parent Application Service, then parenting the Discovered App Services. Has anyone come across this/ Possibly solved this similar or other method(s)?
Please and Thank you for any guidance/experiences.