Gahh come on guys! Auto populate wont work anymore? And Kubernetes was removed as an entry for tagging?
I really wish Dynatrace would ask for the customer feedback before making some of these changes.
it use to be like this and it was great:
Solved! Go to Solution.
Oh wow, that both is a real step down in the usability of the UI
The auto complete was a bit quirky, but a huge tree list is just a real step down from before.
Huge kudos though that the Property for conditions is finally a proper text box with a search, been waiting for that for years!
If the other things are fixed, the new auto tag UI would be really great.
Ouch! There is this dev principle within Dynatrace to ask anyone who could be impacted by a change for permission/confirmation.
Seems this was missed here, at least noone asked me 😉
Seems everything is focused on configuration via API anyways, who cares about the UI *joking*
I'm not a fan of this, it was the same when the problem alert profile UI changed. I liked being able to have the tag preview be separated out by service, infrastructure, etc. It also feels like the UI is cut off a bit, everything feels smushed together. Again not having auto populate is awful and adds alot of time
Agree. I even thought something wasn't matching, because it was way hidden down in the long list of preview.
Doesn't help also when service names are very much like process names sometimes.
Bring back the separation!
At least by the main entities like Service, Processes, Hosts, then everything else.
I'm really wondering what was the driver for this change. The previous UI was effective. This one is a mess. Especially the placeholders.
Why was the placeholder autocompletion removed?
Maybe @MarcusEng can bring some light to this?
So in longer form – thanks a lot for the spirited feedback!
I understand that moving the cheese (and yes, we did that a lot recently in settings) is painful, especially to power users who have well-established patterns to navigate through familiar dialogs.
Internally, the auto tags setting was carried over into a new settings architecture and the visual result is that it is also rendered differently. That is the painful part for some, but of course, there are good parts.
Auto tags, among most other settings, are now manageable through a common API that behaves consistently in both content and permissions so users who have been granted access to this setting are now able to interact on both the UI and API (through personal access tokens). The UI is now rendered through a framework that allows ensuring consistent user experience (save patterns, styling) and features: Configuration history aka changelog (coming soon), searchable lists, etc. The best part is that it now allows us to fairly easily introduce UX improvements to all such screens at once like column sorting or more powerful list filtering. So to summarize and to borrow an industry idiom: in general we move from handcrafted individual setting pets that were likable and well-implemented individually but with sometimes quirky behavior towards neater, more orderly, and consistent settings cattle that are easier to maintain and improve.
Yes - this will return very soon in auto-completion style. Currently targeted to be released in July!
This is either a misunderstanding in the UI or I don’t understand yet what is missing. Kubernetes is relevant to auto tags as either a replacement placeholder or as a condition property. What has changed visually is that the observed labels are now shown in a dedicated combo box and no longer alongside the property itself.
hope this helps!
First off, I want to say we appreciate all your work.
Its great to see a product that is changing and evolving all the time, and we understand that this takes a lot of effort and care on your part.
And there are some amazing new features which is great.
The reasoning to uniform the API's makes a lot of sense, and yes changing UI's will always have haters and lovers, BUT... this change is cumbersome and goes a step back in usability and readability of the auto-tag settings.
Same goes to the Alerting profile, as was already mentioned, but I thought that the UI for that will get better, and not spread to other screens.
Please believe us when saying this change is un-usable, could result in production errors, and will have a negative effect on the product, rating, customer ease of use and so on.
I would love to elaborate more if needed.
Please consider changing the UI back, or even allow a degree of indentation in the rules and the conditions that populate them, for ease of readability.