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

How Can I Monitor a Single URL with Multiple IP Addresses, using HTTPS monitor?

dldauk

I have several urls https: site that I need to monitor, each of them has multiple IP addresses.

Find more posts tagged with

Accepted answers

All comments

serena

dldauk wrote:
I have several urls https: site that I need to monitor, each of them has multiple IP addresses.

Are each of these IP addresses tied to distinct entities? For instance url endpoint is the same across different servers?

If that's the case you would want to add those IP addresses as nodes, and assign the application template with the HTTPs monitor you're building on those nodes. HTTPS Monitor

serena

Also please check out SolarWinds Lab Bits: Configuring the HTTPS Component in SAM - YouTube

dldauk

Example: Each external node is Https:\\abc.com - it has 15 IP address, I'm already using Application Monitor HTTPs to monitor the url. How do I monitor the other 14 IP address with the same url?

dldauk

I suppose I could create new nodes with example: ABC Site Port - IP XXX.XXX.XXX.XXX, assign it a different IP address and then create an https monitor for each of the different nodes.

serena

dldauk wrote:
I suppose I could create new nodes with example: ABC Site Port - IP XXX.XXX.XXX.XXX, assign it a different IP address and then create an https monitor for each of the different nodes.

This is how many customers do this workflow - adding each node to be managed via Orion, adding these nodes to a group and then ultimately applying the application template to the group.

Alternatively if you aren't looking to monitor each node and preserving the node to application relationship, you could build one application template with 15 individual https component monitors set up, each with a different ip address specified for the component monitor.