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.
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