Showing results for 
Show  only  | Search instead for 
Did you mean: 

Dynatrace display issue when scrolling down



I try to open "Problems" view on dynatrace. When i scroll down, the "Impacted", "Affected", "Root cause" and "alerting profiles" columns disappeared.

when i scroll up the columns appear again.

This issue is only on Ms Edge. (no problem with chrome browser)

I've tried to clear story and cache => the same issue 

Scrolling up:



Scrolling down:



Thanks for your help.






Dynatrace Champion
Dynatrace Champion

Hi MedB, 

yes, this is a known issue that we are working on. We'll let you know when the fix will be available. As you found, it only affects Edge. 

Best wishes, Hannah

Thank you for your help.

Best regards.


Just to add; this (annoying) issue is not only on the problem screen but also happening on other screens as well. It looks to be more frequent on smaller screens. I experience more issue on my tablet screen (when travelling) rather than using the big monitor being on the office or at home.

Hopefully will be fixed soon.


I have also seen a variety of Edge-specific UI view element scaling/rendering problems when scrolling.  For example, the RHS control to show the section headers disappears when scrolling down.  This could be the cause of the 'Host performance' widgets going from 'tiled' to full width.  There's also the redraw of widgets to full width when scrolling down to the point where the Incoming Connections/Outgoing Connections views are not visible after scrolling.

Dynatrace Champion
Dynatrace Champion

A fix has been created. We're expecting it to be pushed later this week or next. Thanks for your patience. 

That's great @HannahM ! Is it already known in which version the fix will be rolled out? 

Looking forward seeing your response, 

Kind regards,


Dynatrace Champion
Dynatrace Champion

It was a fix to something bundled with the Cluster. So I'm expecting it to come out with 1.259 which has started to be rolled out to customers.

Dynatrace Champion
Dynatrace Champion

Unfortunately, the fix wasn't as successful as we had believed. We are reviewing this and will update you when we have more information