Open for Voting

Feature Request - Choose Unmanaged Schedule timezone option.

This idea is related to the case #557657

Hello there

Right now, when we unmanage a device the popup shown Local System Time for the Unmanaged Schedule.

It would be real usefull for us to be able to choose if we want webconsole to capture local data/time  or if we want it to show any other time zone.

In older versions, npm 9 it used to get the server time instead the local system time and so, it was easier to all our partners from many parts of the globe, to unmanage in the right time synchronization without need to cautulate the time diference between the core server and the local system.

Right now the only way to achive this is to change the Local system timezones, which is counter-productive.

Please, give us the option to choose between local system time or synchronized  time to one time zone choosed by the admin.

  • I'm submitting a feature request to support the use of external data sources (like patching schedules exported from patch management tools in xml or spreadsheet formats).

    We have been asked to provide an automated solution to import or at least interrogate the patch calendars used by our patching teams at different sites and perform a blackout function against the managed nodes during the patch cycle.

    In alert processing we're using a custom attribute to check whether or not a node is eligible for alert action processing, instead of unmanaging them to suppress notifications.

    The plan is to toggle this property (set AlertDisabled=Yes) and include canned text in the required "AlertDisabledComments" field indicating a patch cycle identifier (an alphanumeric ID from the patch calendar).

  • This is actually part of a larger issue where SolarWinds overall (NPM, SAM, etc) is NOT UTC-aware. It's locked to the poller time, which means a geographically dispersed installation creates mis-matched data at several points.

  • This is potentially a good thing for us as we have sites in all the time zones here in the US including Arizona that does

    not adjust Daylight Savings Time which can cause some unexpected behaviors at times.  This especially comes about

    when unmanaging a device for patching.  This may be something that could also be tied into Calendars which seems to

    have some interest by others...