Forum Discussion
Capacity Metrics Dashboard - Notebook Pipeline Run reported incorrectly (time off by an hour?)
Hi v-prasare
Its funny, but I see that there are dozens and dozens of other posts about the timezone problem in the capacity metrics app.
I didn't see those at first.
No customer would expect that we should be updating a timezone offset two times a year, in a configuration parameter. Nor would we expect that there is only one timezone that is relevant to the entire capacity. This had the feeling of a bug, but I don't think Microsoft considers it a bug. It appears in the microsoft documentation.
I'm probably going to close the case now. Whenever I install this app in the future, I will just use UTC. Less confusing.
I should include that I'm running v.1.5.1 of the capacity metrics app.
My original theory was that this bug was specific to the North Central US region.
However I think it is probably even more simple than that. It seems to be affecting East US as well. It appears that all the date/times for these synapse notebooks are being reported as UTC-4 instead of UTC-5. That may be the result of not taking the seasonal differences into account. This app may be unconditionally using the UTC-4 math to display our start/stop times in the eastern timezone.
I have opened a support ticket, but it hasn't gotten to Microsoft yet. Currently with their partners at Mindtree.
The only mystery is why I'm the first to complain about this. Perhaps it is a recent regression or something like that.
Hi dbeavon3,
Thanks for actively participating in MS Fabric Community Support.
As mentioned you have already raised a support ticket, While you're waiting for the support ticket resolution, your feedback about improving the Capacity Metrics App particularly in terms of time zone clarity, Spark cluster monitoring, and admin usability is highly relevant and insightful. It's important that our product team hears about this directly from users like you, who are deeply engaged with the platform and rely on it for essential operations, these insights will undoubtedly contribute to a better experience for all users.
I’d encourage you to submit your detailed feedback and ideas via Microsoft's official feedback channels, such as the Microsoft Fabric Ideas. Feedback submitted here is often reviewed by the product teams and can lead to meaningful improvement.
Thanks,
Prashanth Are
MS Fabric Community Support
Hi v-prasare
Its funny, but I see that there are dozens and dozens of other posts about the timezone problem in the capacity metrics app.
I didn't see those at first.
No customer would expect that we should be updating a timezone offset two times a year, in a configuration parameter. Nor would we expect that there is only one timezone that is relevant to the entire capacity. This had the feeling of a bug, but I don't think Microsoft considers it a bug. It appears in the microsoft documentation.
I'm probably going to close the case now. Whenever I install this app in the future, I will just use UTC. Less confusing.dbeavon3, Thank you for your detailed observations and for identifying the underlying issue with the timezone offset in the Capacity Metrics App. We sincerely appreciate the time and effort you put into exploring this matter and sharing your findings.
please accept your answer, this will help others users to find answer to similar issues more quickly
Thanks,
Prashanth Are
Exactly right and don't get me started on this issue in Power BI Desktop. It's outrageous and a total disaster how badly the ball has been dropped with timezone management. So much for time intelligence, huh? 😂
