I noticed a change in our Dynatrace environment a few weeks ago and at first thought it was just a cache thing, but it seems like it truly has changed. It used to be when I was in edit in a dashboard, whatever Management Zone and timeframe I had set while in edit would be saved as the default for that password. At least that is how it seemed to be anyway. Each time I would login and select different dashboards, the Management Zone and timeframe would change.
A couple of weeks ago I noticed this no longer seems to be the case. Did something change?
Solved! Go to Solution.
You are right. Something has changed and it is annoying.
I've tried to embrace this change and find something positive to this - but there nothing positive to say.
For the dashboards provided to many of our users we now need to communicate that they have to change filter and time frame all the time.
Also my default time frame seems to be 72 hours - that is also quite annoying.
The workaround is to use links to dashboards. The url contains time frame and management zones.
Hope for a change back to the better soon.
Ok so I am not going crazy then, lol. And you are correct, it's VERY annoying and needs to go back to what it was. Links are ok, but our dashboards have been created with the idea that the Management Zone and timespan are saved by default when in edit mode. This just makes users need to click on more things and not to mention makes it confusing for some. This must have been one of those silent changes because I do not recall seeing anything on it. I guess it's time to open an RFE to see if we can get it pushed back.
No and in the use case that would not matter. I nor anyone else should now need to use the API to set the default Management Zone and timespan on a dashboard when the easy functionality of doing this while editing a dashboard "was" there.
At least this works for me. I can set the Management Zone for a dashboard using the configuration REST API.
By default I have NULL as the management zone. If I set it to a proper value (must be a JSON object), it applies as the setting for the dashboard.
Download the dashboard definition (jq is just for formatting the ouput here):
curl -XGET -H "Authorization: api-token $APITOKEN" "$TENANT/api/config/v1/dashboards/$DASHBOARD" | jq '.' >/tmp/dashboard.json
set the management zone to a object, for example I now have:
"name": "CSM testing"
And put the dashboard definition back using REST API ( I recommend to use the validator first 😞
curl -XPUT --data @/tmp/dashboard.json -H 'Content-Type: application/json; charset=UTF-8' -H "Authorization: api-token $APITOKEN" "$TENANT/api/config/v1/dashboards/$DASHBOARD"
Thanks Julius. I appreciate the effort, but this is functionality that was already in Dynatrace and has been removed recently and in my opinion is not a helpful change and if anything is impactful. Our users design their dashboards around the Management Zones and timespans and want what they had which was the ability to set the defaults for this when you open said dashboard. They should not need to go through an API after editing or creating a dashboard just to set the defaults for Management Zone and timespan. It makes no sense to me or our users as to why this would be removes from the GUI.
If you are creating a dashboard through the API, then yes I can see doing it that way. But once a dashboard is either edited or made by hand inside the Dynatrace GUI, there is no reason we should not be able to set these defaults anymore.
Agreed. This was just an idea, since I have been playing with the dashboard API recently.
There definitely should be an option to set it directly in the UI. Maybe there is a featureflag already that will enable those settings in the UI - @Roman W. ?
You're correct, we did change the behavior of persisted management zones and time frames being automatically applied upon opening a dashboard. We do however still save the settings when editing a dashboard.
The reason for this was some negative sentiment on automatically changing global time frame and management zone settings without letting the user know about it.
It seems to me we need to take a third shot at this, since I do see where you're all coming from. Let me get back to you as soon as we have re-evaluated all options.
Roman, that's most appreciated.
But let me understand what you write correctly.
"We do however still save the settings when editing a dashboard. "
Ehm, not really. Is that not the main problem? Or what settings are we talking about if not the time frame and the management zones?
And as a note, the problem is, that with several management zones and a huge amount of hosts/applications/services most of the users of dashboards might not know the entire infrastructure and which management zone to use. Most have no interest in switching between zones at dashboard level - this is for the overview.
The possibility to have tiles configured with management zones would be nice - then the dashboard could be very specialized without the users need to set the filter themselves.
Like I said, we'll have to find a better solution for this.