Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Network Performance Monitor (NPM) > Managing report schedules with multiple Orion instances across different time zones

Managing report schedules with multiple Orion instances across different time zones

Table of contents
Created by Michael Perez, last modified by MindTouch on Jun 23, 2016

Views: 64 Votes: 5 Revisions: 3

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.  

Environment

All NPM versions

Detail

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

 

Last modified
22:39, 22 Jun 2016

Tags

Classifications

Public