Documentation forSolarWinds Platform Self-Hosted

Monitor load balancers

You can monitor load balancers in monitored Azure and GCP accounts.

Before you begin

Supported providers

  • AWS
  • Azure
  • GCP

License

  • Requires a SolarWinds Observability Self-Hosted Advanced license.

  • Each Azure load balancer counts as a node against the license node count. However, load balancers do not appear as nodes on web console screens and reports.

  • GCP load balancer license usage is calculated from the total number of backend services linked to the load balancer.

Enable monitoring load balancers

If you monitor load balancers, all load balancers on the subscription are collected. Regional limitations and tag filtering are ignored.

When adding a load balancer, you have the following options to enable load balancer monitoring in the Add Cloud Account wizard:

  • Select Monitor all supported resources.
  • Select Monitor entities by tags and specify the tag.
  • Select Monitor selected entities and then select the Load Balancers box.

View Azure load balancer data

  1. Click Dashboards > Cloud > Azure to get an overview of monitored Azure resources.

  2. Click the Network tab and review the Load Balancers tab to see the number of monitored load balancers and their status.

  3. Click the Load Balancers widget title to go to the Load Balancer details view.

View GCP load balancer data

  1. Click Dashboards > Cloud > GCP to get an overview of monitored GCP resources.

  2. Click the Network tab and review the Load Balancers tab to see the number of monitored load balancers and their status.

  3. Click the Load Balancers widget title to go to the Load Balancer details view.

Supported types of Google Cloud Load Balancing

  • Application Load Balancers
  • Proxy Network Load Balancers
  • Passthrough Network Load Balancers

Key features and metrics

  • Traffic statistics
  • Latency
  • Error rates
  • Connections (Open, Closed, and Active)

You can use GCP load balancers in PerfStack, alerts, reports, and groups.