Submit a ticketCall us

AnnouncementsSystem Monitoring for Dummies

Tired of monitoring failures disrupting the system, application, and service? Learn the key monitoring concepts needed to help you create sophisticated monitoring and alerting strategies that can help you save time and money. Read the eBook.

Get your free eBook.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Alert Summary page shows the old server name

Alert Summary page shows the old server name

Table of contents

Updated May 10, 2017

Overview

This article explains why a new alert is working as expected but shows the old server name on the Alert Summary page.

Environment

All SAM versions

Detail

This occurs when the SwisUriSystemIdentifier setting within the WebSettings database table is set to the old server.

 

Note: SolarWinds does not recommend changing this setting to the new server name because this requires rebuilding containers, limitations, dependencies, and so on. The alert will continue to work and will not cause any issues.

 

See the following for more information:

Alert variable issue

Migrating Orion is leaving the old hostname in the SwisUriSystemIdentifier in the WebSettings table

 

Last modified

Tags

Classifications

Public