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

URL Monitoring Service with APM?

I would like to provide a URL monitoring service for several of our customers but I have run into a bit of a snag and am hoping for some ideas on how to solve it.

For the URL monitoring service we add an external node and assign HTTP Component monitor applications to the node with the URL's for the webistes to be monitored.

The problem is that the potential exists for two different customers to have their websites hosted with the same company on the same server. Because external nodes require unique IP's, I can't setup two external nodes for the same system (one for each customer hosted on the same system).

Any ideas on how to solve or work around this potential problem?

Find more posts tagged with

Accepted answers

jiri.tomek

External nodes don't have to be valid nodes at all. You can create nodes with IPs such as "1.2.3.4", "1.2.3.5", ... To each of this nodes just add HTTP monitors for specific customers and then limit these "fake" nodes by Customer ID.

All comments

martin.susil

When you setup HTTP Monitor, you can specify custom URL. It doesn't need to be URL of the target node. So as a workaround, couldn't you just add fake external nodes and manually specify the URL to what you need?

byrona

When I set these up I do specify a custom URL as that is how you need to configure it to monitor an actual URL. I realize that URL doesn't need to exist on the Node that the application is assigned to.

I need to be able to configure things in such a way as to allow customers to log into Orion to see the URL's that we monitor for them. Currently we restrict views based on CustomerID which is a Custom Node Property. This allows the to see the external node with the URL application that monitors their URL's. For this to work each customer needs to have their own external node which require unique IP's even though it doesn't really monitor or care about that IP.

Please let me know if you have a different way that this all might work, thanks!

jiri.tomek

byrona

Ah, I see, that does work.

What would be preferable to creating "fake" IP's would be the ability to have an External Node be created with any name such as "Bob" allowing for the creation of Meta Nodes for URL monitoring. Maybe this would be an additional node option called Meta Node or an option you can select for an External Node.