-
Suggestion
-
Resolution: Fixed
We've updated all the dashboards, and the timestamp values are now in the correct format for each of them.
Problem:
With the new Alert details view widget introduced in the Opsgenie Alert analytics report, the created/closed timestamps are now shown as x.0h y.0m z.0s
Suggestion:
Revert the decimal precision introduced in the alert metrics for Created/Acknowledged/Closed timestamps because the 5.0h has no point of use, if there are minutes to show it shows (example) 5h15m so the zero has no use at all.
Column: Created at time is the date and time the issue was created
The old view/ CSV file shows the correct format as 4/4/2024 15:29:01
- mentioned in
-
Page Failed to load
[OPSGENIE-2069] Revert the decimal precision introduced in the alert metrics for Created/Acknowledged/Closed timestamps
We've updated all the dashboards, and the timestamp values are now in the correct format for each of them.
All comments
Dear Justin,
We sincerely apologize for the frustrations caused by the new Analytics feature. Your feedback is invaluable, and we are committed to resolving these issues promptly.
Regarding the specific problems you've highlighted:
Downloading Chart Data: You have the option to download all the charts in the dashboard as CSV. This will contain the list of all the entries in that chart. Please let us know if this is not working for you.
Dashboard Timezone: We are working on this as a high priority. Our team is actively developing a solution to automatically sync the dashboard timezone with your organization's default setting. This should be available soon.
Data Discrepancy: Ideally, the discrepancy should not exist. We are keen to investigate it further. Please contact our support with specifics, and we will prioritize resolving these discrepancies.
Timestamp Format (for sorting): We are happy to share that the fix has been implemented and is pending deployment. We expect it to be live by next week.
We greatly appreciate your patience and the time you took to share your concerns. Your detailed input is instrumental in guiding our improvements.
Once again, we deeply apologize for the inconvenience and disruption this has caused. We're dedicated to not just resolving these issues but ensuring your experience with us is positive moving forward. Thank you for your patience and understanding.
Thank you
bf60ea9c7606
I am sorry to hear you also experience similar issues.
And thank you for the support on the issue I welcome your additional and well stated report about the problem. It is indeed not just a 'thing' with the timestamp.
I'll Keep my fingers crossed on a rapid solution
OpsGenie Team, I know you are working on fixing the rollout of massive problems with the NEW analytics page/feature. From a customer standpoint I want it to be publicly stated similar to 0090940c42a6 stance, this is the worst it's every been. You completely broke my organization's flow and reporting to leadership/stakeholders. You removed So many features that should never have been removed and it is taking far too long to fix what your new version broke. It is very dissapointing as it seems you had little to no customer chaos testing before rollout then said it was impossible to rollback the update and in chat with support, they admitted they were still using the OLD dashboard so they didn't yet know the pains customers were experiencing.
In addition to all already mentioned on standardizing the time stamps in the charts, you can't view the whole chart or download the whole chart. It shows the first 10 results but if you have more than 10 rows, You cant view and export all of them. When exporting it only shows the current page view. You can't expand that chart. As Peggy pointed out sort is completely broken.
Please allow the dashboard timezone to be synced with default org selection instead of having to choose each time.
AND, Elapsed time to (close, open)....what is this for? When I run queries set from old dates that the OLD dashboard created, they values don't match though I am now selecting the exact same query.
Hi Rishabh,
Thank you for the response.
The proposed change will certainly help to work with time related functions in exel/ sheets.
I'll hope to see the result soon
Thank you
Hi 0090940c42a6
Thank you for providing your detailed analysis. The current time representation (hh mm ss) is the same as what we had in the previous experience. However, we understand that this format does not allow for sorting or calculating average values in Google Sheets/Excel.
As a result, our team is working on making further changes to this format so that Time to Ack and Time to Close will follow the "hh:mm:ss" format. This format will allow using all time-related functions in Excel/Sheets. This change will only apply to the Table view charts, which are mainly used for Excel/Sheets analysis. Unfortunately, we won't be able to support this for the Bar type or other visualization charts.
We kindly ask for your patience as we work on these changes and roll them out to all our customers. Thank you for your understanding.
Hi Rahul,
I am not happy with this notation.
To be honest: it has never been as crappy as it now. And far away from a really professional appearance.
How is it possible working with a report that requires not only a push on the button, but also creating a report aside to re-calculate all data from the original report to an acceptable view and notations.!
I cannot present to my organisation: " Hi all, the average performance is 533.73 minutes.!!"
This needs to be specified in hours minutes seconds
I expect it to be similar as e.g. : 15:29:01
The current notation e.g. 5h15m doesn't work in a sheet, i cannot filter on data from less to more - or more to less
See it yourself this cannot be filtered from more to less or from less to more time
| Time to acknowledge |
| 1.0h 0.0m 25.0s |
| 1.0h 0.0m 4.0s |
| 1.0h 1.0m 1.0s |
| 1.0h 1.0m 42.0s |
| 1.0h 1.0m 6.0s |
| 1.0h 11.0m 16.0s |
| 1.0h 11.0m 50.0s |
| 1.0h 11.0m 53.0s |
| 1.0h 11.0m 58.0s |
| 1.0h 11.0m 7.0s |
| 1.0h 12.0m 49.0s |
| 1.0h 13.0m 21.0s |
| 1.0h 13.0m 24.0s |
| 1.0h 13.0m 28.0s |
| 1.0h 14.0m 26.0s |
| 1.0h 16.0m 7.0s |
| 1.0h 17.0m 6.0s |
| 1.0h 18.0m 59.0s |
| 1.0h 2.0m 18.0s |
| 1.0h 26.0m 2.0s |
| 1.0h 3.0m 0.0s |
| 1.0h 33.0m 46.0s |
| 1.0h 34.0m 24.0s |
| 1.0h 44.0m 12.0s |
| 1.0h 44.0m 12.0s |
| 1.0h 45.0m 1.0s |
| 1.0h 52.0m 12.0s |
| 1.0h 54.0m 26.0s |
| 1.0m 0.0s |
| 1.0m 0.0s |
| 1.0m 0.0s |
| 1.0m 0.0s |
| 1.0m 0.0s |
| 1.0m 1.0s |
| 1.0m 1.0s |
| 1.0m 1.0s |
| 1.0m 1.0s |
| 1.0m 10.0s |
| 1.0m 10.0s |
| 1.0m 10.0s |
| 1.0m 10.0s |
| 1.0m 11.0s |
| 1.0m 11.0s |
| 1.0m 12.0s |
| 1.0m 12.0s |
| 1.0m 12.0s |
| 1.0m 12.0s |
| 1.0m 13.0s |
| 1.0m 13.0s |
| 1.0m 14.0s |
| 1.0m 14.0s |
| 1.0m 14.0s |
| 1.0m 15.0s |
| 1.0m 15.0s |
| 1.0m 15.0s |
| 1.0m 15.0s |
| 1.0m 16.0s |
| 1.0m 17.0s |
| 1.0m 18.0s |
| 1.0m 18.0s |
| 1.0m 19.0s |
| 1.0m 19.0s |
| 1.0m 19.0s |
| 1.0m 2.0s |
| 1.0m 2.0s |
| 1.0m 2.0s |
| 1.0m 20.0s |
| 1.0m 21.0s |
| 1.0m 22.0s |
| 1.0m 22.0s |
| 1.0m 22.0s |
| 1.0m 22.0s |
| 1.0m 22.0s |
| 1.0m 23.0s |
| 1.0m 23.0s |
| 1.0m 23.0s |
| 1.0m 24.0s |
| 1.0m 24.0s |
| 1.0m 25.0s |
| 1.0m 26.0s |
| 1.0m 27.0s |
| 1.0m 27.0s |
| 1.0m 28.0s |
| 1.0m 28.0s |
| 1.0m 28.0s |
| 1.0m 28.0s |
| 1.0m 29.0s |
| 1.0m 29.0s |
| 1.0m 3.0s |
| 1.0m 3.0s |
| 1.0m 3.0s |
| 1.0m 3.0s |
| 1.0m 30.0s |
| 1.0m 30.0s |
| 1.0m 30.0s |
| 1.0m 30.0s |
| 1.0m 31.0s |
| 1.0m 32.0s |
| 1.0m 32.0s |
| 1.0m 33.0s |
| 1.0m 34.0s |
| 1.0m 35.0s |
| 1.0m 35.0s |
| 1.0m 37.0s |
| 1.0m 37.0s |
| 1.0m 39.0s |
| 1.0m 4.0s |
| 1.0m 40.0s |
| 1.0m 40.0s |
| 1.0m 41.0s |
| 1.0m 43.0s |
| 1.0m 44.0s |
| 1.0m 45.0s |
| 1.0m 47.0s |
| 1.0m 48.0s |
| 1.0m 49.0s |
| 1.0m 5.0s |
| 1.0m 5.0s |
| 1.0m 5.0s |
| 1.0m 5.0s |
| 1.0m 5.0s |
| 1.0m 5.0s |
| 1.0m 5.0s |
| 1.0m 5.0s |
| 1.0m 5.0s |
| 1.0m 50.0s |
| 1.0m 51.0s |
| 1.0m 53.0s |
| 1.0m 54.0s |
| 1.0m 54.0s |
| 1.0m 54.0s |
| 1.0m 56.0s |
| 1.0m 56.0s |
| 1.0m 57.0s |
| 1.0m 57.0s |
| 1.0m 58.0s |
| 1.0m 58.0s |
| 1.0m 59.0s |
| 1.0m 59.0s |
| 1.0m 59.0s |
| 1.0m 59.0s |
| 1.0m 59.0s |
| 1.0m 6.0s |
| 1.0m 6.0s |
| 1.0m 6.0s |
| 1.0m 6.0s |
| 1.0m 6.0s |
| 1.0m 7.0s |
| 1.0m 7.0s |
| 1.0m 7.0s |
| 1.0m 7.0s |
| 1.0m 8.0s |
| 1.0m 8.0s |
| 1.0m 8.0s |
| 1.0m 8.0s |
| 1.0m 9.0s |
| 1.0m 9.0s |
| 1.0m 9.0s |
| 1.0m 9.0s |
| 10.0h 31.0m 31.0s |
| 10.0h 37.0m 2.0s |
| 10.0h 40.0m 17.0s |
| 10.0m 12.0s |
| 10.0m 13.0s |
| 10.0m 14.0s |
| 10.0m 22.0s |
| 10.0m 23.0s |
| 10.0m 25.0s |
| 10.0m 30.0s |
| 10.0m 30.0s |
| 10.0m 32.0s |
| 10.0m 43.0s |
| 10.0m 43.0s |
| 10.0m 48.0s |
| 10.0s |
| 10.0s |
| 10.0s |
| 10.0s |
| 10.0s |
| 10.0s |
| 10.0s |
| 10.0s |
| 10.0s |
| 10.0s |
| 10.0s |
| 10.0s |
| 10.0s |
| 10.0s |
| 102.0h 32.0m 43.0s |
| 11.0h 1.0m 24.0s |
| 11.0m 13.0s |
| 11.0m 14.0s |
| 11.0m 31.0s |
| 11.0s |
| 11.0s |
| 11.0s |
| 11.0s |
| 11.0s |
| 11.0s |
| 113.0h 56.0m 0.0s |
| 115.0h 10.0m 5.0s |
| 12.0h 23.0m 17.0s |
| 12.0h 46.0m 17.0s |
| 12.0h 53.0m 11.0s |
| 12.0m 10.0s |
| 12.0m 11.0s |
| 12.0m 13.0s |
| 12.0m 14.0s |
| 12.0m 16.0s |
| 12.0m 21.0s |
| 12.0m 25.0s |
| 12.0m 54.0s |
| 12.0m 58.0s |
| 12.0s |
| 12.0s |
| 12.0s |
| 12.0s |
| 12.0s |
| 12.0s |
| 12.0s |
| 12.0s |
| 12.0s |
| 12.0s |
| 126.0h 4.0m 9.0s |
| 13.0h 1.0m 0.0s |
| 13.0h 13.0m 17.0s |
| 13.0h 53.0m 34.0s |
| 13.0h 6.0m 13.0s |
| 13.0m 16.0s |
| 13.0m 32.0s |
| 13.0m 43.0s |
| 13.0m 44.0s |
| 13.0m 45.0s |
| 13.0m 50.0s |
| 13.0s |
| 13.0s |
| 13.0s |
| 13.0s |
| 13.0s |
| 13.0s |
| 13.0s |
| 13.0s |
| 13.0s |
| 13.0s |
| 13.0s |
| 14.0h 1.0m 11.0s |
| 14.0h 31.0m 11.0s |
| 14.0h 31.0m 22.0s |
| 14.0m 37.0s |
| 14.0m 6.0s |
| 14.0s |
| 14.0s |
| 14.0s |
| 14.0s |
| 14.0s |
| 14.0s |
| 15.0h 16.0m 28.0s |
| 15.0h 16.0m 30.0s |
| 15.0h 28.0m 11.0s |
| 15.0m 12.0s |
| 15.0m 17.0s |
| 15.0m 33.0s |
| 15.0m 53.0s |
| 15.0m 58.0s |
| 15.0m 59.0s |
| 15.0s |
| 15.0s |
| 15.0s |
| 15.0s |
| 15.0s |
| 15.0s |
| 15.0s |
| 15.0s |
| 15.0s |
| 15.0s |
| 15.0s |
| 15.0s |
| 15.0s |
| 157.0h 58.0m 16.0s |
| 16.0m 0.0s |
| 16.0m 0.0s |
| 16.0m 13.0s |
| 16.0m 18.0s |
| 16.0m 18.0s |
| 16.0m 19.0s |
| 16.0m 29.0s |
| 16.0m 42.0s |
| 16.0m 52.0s |
| 16.0s |
| 16.0s |
| 16.0s |
| 16.0s |
| 16.0s |
| 16.0s |
| 16.0s |
| 16.0s |
| 16.0s |
| 16.0s |
| 16.0s |
| 16.0s |
| 16.0s |
| 16.0s |
| 16.0s |
| 16.0s |
| 16.0s |
| 17.0m 10.0s |
| 17.0m 33.0s |
| 17.0m 42.0s |
| 17.0s |
| 17.0s |
| 17.0s |
| 17.0s |
| 17.0s |
| 17.0s |
| 17.0s |
| 17.0s |
| 17.0s |
| 170.0h 38.0m 53.0s |
| 18.0h 21.0m 5.0s |
| 18.0h 37.0m 52.0s |
| 18.0m 18.0s |
| 18.0m 40.0s |
| 18.0s |
| 18.0s |
| 18.0s |
| 18.0s |
| 18.0s |
| 18.0s |
| 18.0s |
| 18.0s |
| 18.0s |
| 18.0s |
| 18.0s |
| 18.0s |
| 19.0s |
| 19.0s |
| 19.0s |
| 19.0s |
| 19.0s |
| 19.0s |
| 19.0s |
| 19.0s |
| 19.0s |
| 19.0s |
| 19.0s |
| 2.0h 16.0m 1.0s |
| 2.0h 17.0m 41.0s |
| 2.0h 26.0m 51.0s |
| 2.0h 28.0m 0.0s |
| 2.0h 3.0m 9.0s |
| 2.0h 32.0m 28.0s |
| 2.0h 44.0m 39.0s |
| 2.0h 44.0m 55.0s |
| 2.0h 50.0m 47.0s |
| 2.0m 0.0s |
| 2.0m 1.0s |
| 2.0m 1.0s |
| 2.0m 1.0s |
| 2.0m 10.0s |
| 2.0m 10.0s |
| 2.0m 11.0s |
It still is not what is was before:
The old view/ CSV file shows the correct format as 4/4/2024 15:29:01
hey 0090940c42a6 this "Average close time 533.73 " means 533.73 minutes all time units are in minutes
Hello Rishabh,
Well unfortunately the dashboard charts doesn't show the exact timestamps.
They still show the following (I cannot attach a screenshot!)
June
Alerts 85 (count)
Average close time 283.61
Min close time 0
Max close time 3.271
Still don't know what this should reflect in exact time.
I would like to attach some screenshots, but that doesn't work, I think because I'm not authorized to do so?
Hi,
Unfortunatly I've found a fault.
Alert MTTA/R reports:
E.g: Daily Mean Time to Resolve
When I hoover over the piles
it shows in every graphic the wrong notations
How is it possible this is shown as eg. Average close time 533.73 !!
Is this Seconds? Minutes? Hours?
I cannot attach a file with printscreen to show how it looks like
This issue is fixed please let us know if you have further queries