Applications Systems

Configuration changes not detected by Server Configuration Monitor

Describes a network connection issue that causes SCM to be unable to detect configuration changes.

First published date

11/13/2018 1:28 PM

Last published date

6/4/2019 8:25 PM

Overview

Server Configuration Monitor (SCM) may not detect configuration changes when there are network connection issues.

Product section

Server Configuration Monitor

Resolution

In order to provide relevant information, SCM relies on the proper order of incoming messages. However, SCM may not detect configuration changes when network issues occur, as the Orion agent does not guarantee the order of queued messages in the order that they occurred. After the network connection is restored, the Orion agent sends a summary of all changes, so some granularity of changes may be lost, and only an aggregated summary of changes may be available. Currently, there is no workaround for this issue.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.