Network Management
Managing report schedules with multiple Orion instances across different time zones
This article addresses concerns introduced with managing report schedules if you have multiple Orion instances that are located in different regions and time zones. The statistics that Orion collects are stored in UTC and the Web Console presents the information in relation to the time zone where the user logs in from. If you are logged into the Web Console from Florida, the time results will be presented in relation to the Eastern Time zone even if the server is located in California.
First published date
10/15/2018 7:49 PM
Last published date
2/9/2022 2:11 PM
Overview
This article addresses concerns introduced with managing report schedules if you have multiple Orion instances that are located in different regions and time zones.
Product section
Network Performance Monitor
Cause
The statistics that Orion collects are stored in UTC and the Web Console presents the information in relation to the time zone where the user logs in from.
Resolution
The statistics that Orion collects are stored in UTC and the Web Console presents the information in relation to the time zone where the user logs in from.
For example:
If you are logged into the Web Console from Florida, the time results will be presented in relation to the Eastern Time zone even if the server is located in California which uses Pacific Time zone.
If you would like the reports to be delivered to users who are in the same time zone as you, this is convenient. If you are remotely scheduling reports that are going to be delivered to the California office, you would have to manually factor in the offset for that region when scheduling the reports.
Another workaround would be to remotely log into the server in California, visit the Web Console from that server and schedule the reports from there to eliminate the time offset.
For example:
If you are logged into the Web Console from Florida, the time results will be presented in relation to the Eastern Time zone even if the server is located in California which uses Pacific Time zone.
If you would like the reports to be delivered to users who are in the same time zone as you, this is convenient. If you are remotely scheduling reports that are going to be delivered to the California office, you would have to manually factor in the offset for that region when scheduling the reports.
Another workaround would be to remotely log into the server in California, visit the Web Console from that server and schedule the reports from there to eliminate the time offset.