Hi all,
could not find anyone else asking this, but: I can't set a chart to a timeframe longer than one year.
This makes it unusable for looking at long-term trends like number of users etc. from a capacity planning or reporting perspective. Appmon had a limit in the Web-UI of 999 days.
Is it possible to change that limit? Some hidden config maybe 😉 ?
cheers,
Torsten
Solved! Go to Solution.
You could always do this by setting a custom timeframe. But the new timeframe selector makes it a lot easier: https://www.dynatrace.com/news/blog/customize-dynatrace-analysis-timeframes-as-never-before-with-the...
Not really. Have you tried showing more than one year in a chart? Whenever I do this - new or old timeframe selector - it adjusts the date so that I see 366 days max.
cheers,
Torsten
Never ran into that limit, but I asked about it and there's still some areas of the product that don't handle very large timeframes well hence the limit. The restriction is already planned to be removed once that's all sorted.
Hi James,we ran into this while doing a PoC with a long-time Appmon customer. It's a Managed installation.
Do you think it makes sense to turn this post into an RFE or is there already a timeline as to when this restriction would be lifted?
cheers,
Torsten
No need for an RFE, it's a temporary restriction while all of the views and charts in dashboard are updated to handle the larger timeframes better. I don't have any insight into timelines but sounds like it's currently being worked on.
Thanks a lot James!
I'd like to propose another workaround for this limit: Being more specific with expressions like:
You can easily shift between years with arrows
interesting. I can confirm that this is the case, at least in SaaS. In Data Retention, there is no direct mention to this limit. Probably interesting to see if someone from Dynatrace can explain, and if yes there is a limit, I would suggest a RFE, which I would vote of course.
Are you a managed or SaaS customer? you can always toss in a RFE and Dynatrace could work on a solution to that issue