From the documentation it states: * Agents do not work with AppInsight for SQL if the SQL server is monitored in a cluster. * SQL clusters cannot be polled with domain credentials via the Orion agent because agents do not work with AppInsight for SQL if the SQL server is monitored in a cluster. Is this still the case? We use agents on all windows servers for the following reasons: * Less ports to open on firewalls than WMI * We like and use application dependency mapping

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

AppInsight for SQL - Cluster Monitoring with Agents

shocko

From the documentation it states:

Agents do not work with AppInsight for SQL if the SQL server is monitored in a cluster.
SQL clusters cannot be polled with domain credentials via the Orion agent because agents do not work with AppInsight for SQL if the SQL server is monitored in a cluster.

Is this still the case? We use agents on all windows servers for the following reasons:

Less ports to open on firewalls than WMI
We like and use application dependency mapping

Find more posts tagged with

Accepted answers

All comments

martin.lkab

I am in the exact same situation, our security team does not allow for WMI because of the wide span of ports, and we also have cluster.

This is a problem in our environment.

sturdyerde

After you update SAM to the 2020.2 release, you'll be able to use WinRM for monitoring applications (including AppInsight for SQL). Using WinRM sends WMI queries through HTTPS ports 5985 or 5986 directly (and is secured on both). This avoids the legacy approach of using WMI with DCOM and RPC--which is where that large span of firewall ports came into play. Your security team and/or network firewall team will be much happier that there is one less application requiring those ephemeral ports. The only thing that this does not solve for is application dependency mapping, which of course still requires the agent.