04 Aug 2026
05:15 PM
- last edited on
05 Aug 2026
07:49 AM
by
MaciejNeumann
So, while I like most of the ideas being used in this new app, I have to say that most of our engineers (me included) still use the classic Kubernetes app because it is just far more intuitive.
Initially, I thought it was just a comfort thing. Nobody likes change, right? Just keep using the new app and you'll get used to it.
Well, no... Unfortunately, it's just missing a lot of intuitive features that let us get to what we wanted to see much easier.
The main thing is process group and Dynatrace services that live on our Kubernetes clusters.
With the classic app, you can simply find the cluster you need, click on the namespace on that cluster that you are interested in, and right there on the namespace details page you have the "Resource analysis" table which is just a list of all of the Workloads within that Namespace. So far, you can do something similar in the new app as well. But the big differentiator here is that the Workloads table in Classic has a column for Dynatrace Services that are instantiated from those Workloads. THAT is what we want to see most of the time.
Sure, you can go to a Workload in the new app and, if there is a Dynatrace Service associated to that Workload, you will see it there on the "App services" tab. But I don't want to have to click on every single Workload to be able to see what services are on there.
And yes, I know I can go to the Services app and look for a list of Services that way, but that isn't the point. When I am looking at our Kubernetes infrastructure, there is a lot of information I want to see, both infrastructure-related and app-related. The new app seems almost completely focused on the infrastructure part. It's missing the ability to see app-related info in bulk. We can only see it at the individual level.
Please add App Services as a column and/or filter so that we can easily see what workloads have services instantiated from them and so that we can easily link to those services to drill into them, as well as give us the ability to filter by app services so we can see what infrastructure is used when we only know the service name.
I would like to see the same for Process Groups as well.
Dynatrace has all this topological awareness. Let us use that to make navigating the tool easier. It feels like we have to work really hard to link to things right now.
The drill-down capability still has a lot of room for improvement in these new apps.
Now, if there is a way to see the information I'm looking for in the new app, then please, educate me. But again, even if there is, I would still have to say that it isn't very intuitive. Not nearly as intuitive as it is in the classic.
05 Aug 2026 09:16 AM
Hello @36Krazyfists ,
We are continuously working on improving the K8s app. The cross application / hierarchy connection and intent improvements are in the pipeline.
It is always good to hear feedback as this way we can influence decisions.
Would you be willing to have a generic conversation about these topics? I could also give you an insight into the ongoing works so we can align on expectations.
Thanks,
Geri
05 Aug 2026 03:43 PM
If you mean a call, then absolutely! We've done something similar with David from the Anomaly detection team.
We have several members from our team that would love to be a part of the call and give you feedback on what the new app still needs improvement on for them to stop using the classic.
Feel free to reach out and we'd love to schedule something!
Featured Posts