Database Management

SQL Sentry Issue with Gaps on AWS RDS Target(s) and/or Azure Managed Instance Target(s) - Message: The network path was not found.

The purpose of this article is to provide an explanation around a known issue that started with SQL Sentry Version 2023.4.3 regarding a feature flag named AlternateSqlServerCounterCollection that causes gaps on AWS RDS target(s) and/or Azure Managed Instance Target(s) while monitored by SQL Sentry.

First published date

7/5/2024 3:36 PM

Last published date

2/19/2025 3:12 AM

Overview

It seems that implementing the AlternateSqlServerCounterCollection feature flag leads to gaps on the dashboard for Amazon RDS Target(s) and/or Azure Managed Instance Target(s). Gaps were observed in both the legacy (thick) client and the Portal UI (see screenshots).

image.png

Also noticed the following error stack in the rolling log:


Message: The network path was not found.

System.IO.IOException: The network path was not found.

at Microsoft.Win32.RegistryKey.Win32ErrorStatic(Int32 errorCode, String str)
at Microsoft.Win32.RegistryKey.OpenRemoteBaseKey(RegistryHive hKey, String machineName, RegistryView view)
at System.Diagnostics.PerformanceCounterLib.FindCustomCategory(String category, PerformanceCounterCategoryType& categoryType)
at System.Diagnostics.PerformanceCounterLib.IsCustomCategory(String machine, String category)
at System.Diagnostics.PerformanceCounterCategory.Exists(String categoryName, String machineName)
at SqlSentry.Server.Windows.DataCollectors.PerformanceAnalysisDataCollector.UpdatePerformanceCategoriesByName()

 

Repro Steps:

  • Add an RDS Target/Azure MI Target

  • Enable the AlternateSqlServerCounterCollection feature flag using the following insert statement: insert into dbo.FeatureFlag
    (Name, Enabled)
    values
    ('AlternateSqlServerCounterCollection', 1)

  • Restart the SQL Sentry Monitoring Service(s)

  • Observe gaps and error stacks

Product section

SQL Sentry (SQLS)

Cause

Enabling the feature flag AlternateSqlServerCounterCollection will cause gaps in collection of AWS RDS target(s) and Azure Managed Instance Target(s).

Resolution

If the AlternateSqlServerCounterCollection is enabled in the dbo.featureflag table, it needs to be removed.

Resolution Steps:
  1. Stop SentryOne Monitoring Services.
  2. Delete FeatureFlag with this script below if AlternateSqlServerCounterCollection exists:
    -- Scripts are not supported under any SolarWinds support program or service.
    -- Scripts are provided AS IS without warranty of any kind. SolarWinds further
    -- disclaims all warranties including, without limitation, any implied warranties
    -- of merchantability or of fitness for a particular purpose. The risk arising
    -- out of the use or performance of the scripts and documentation stays with you.
    -- In no event shall SolarWinds or anyone else involved in the creation,
    -- production, or delivery of the scripts be liable for any damages whatsoever
    
    Delete 
    From dbo.FeatureFlag
    Where Name = 'AlternateSqlServerCounterCollection'
    
    
  3. Restart SentryOne Monitoring Services.
As a side note: A permanent fix is set to be implemented in version 2024.3.