WPM Module

Hi, yes WPM can check several different URL's from a single WPM player.

It's also possible to check a single url from different locations. Just install the player software were ever you want to make the check from. Can also be a server in AWS for example. Take a look here for more info:  solarwindscore.my.site.com/.../Use-Amazon-Cloud-Services-as-a-WPM-playback-location

As Seashore says, you can install the WPM player just about anywhere you want.   Just be aware of 2 things:

1) Connectivity requirements back to the main console.   https://documentation.solarwinds.com/en/success_center/wpm/content/orionseumaginstallingplayer.htm

2) Licensing.  WPM is licenses per recording playback location.   So even if you use the same recording, if you monitor from 2 different players, that is 2 licenses.

Also, if you are just checking a URL, you can also use an http or https component monitor from SAM.

Checking a URL with SAM component from multiple locations would require a more costly Additional Polling Engine license for each location.  

If you're looking for a true site uptime monitor, with global probes, I'd be more inclined to use a dedicated site uptime tool such as Pingdom https://documentation.solarwinds.com/en/success_center/pingdom/content/topics/pingdom-probe-servers-ip-addresses.htm

The problem with AWS and Azure is that it does give you a valid user experience accessing the URL in question, but you're restricted to the datacentre locations provided. 

If you already have access to an Azure or AWS instance, then you can stick a WPM player there as per Seashore comment. 

You can use an Agent monitored device as a Remote Collector for SAM. No APE needed

documentation.solarwinds.com/.../sam-orion-remote-collector.htm

SWO SaaS also has that same capability of Pingdom. You can check websites from multiple locations. 

Website Performance Monitoring Solution | SolarWinds Observability SaaS (formerly known as SolarWinds Observability)

SolarWinds Observability | Digital Experience area overview - how to check probe locations. 

If you already have SWOSH, are you likely to fork out for the SWOSaaS product though?  My understanding, albeit limited, is that majority of Pingdom functionality is in SaaS, but it's a costly alternative and if your env is already established it'd be a big project to move over. 

There are other alternatives here, but as we're advocating for SolarWinds products I won't mention those

Every day is a school day! I've used this for NetPath but didn't know you could use it for that. Can also use Linux Agents to save on license costs...

SWOSaas is actually cost and feature comparative with Pingdom now - ask for competitive pricing to migrate. I would recommend SWOSaas over pingdom. I love pingdom, but swo saas is finally reached a level of goodness. One of the major pain points in pingdom is user access. You pay per user in pingdom - not a problem with SWO Saas. Reporting and analysis within the platform are arguably better in SWO Saas too. Pingdom has very limited reporting - you really need to fire up the api to work with it. Migration will be concern with the SEUM/Transactional checks more than anything. Also - if you are integrating SWOSH or the other aspects of SWOSaas - they can share data, not something that Pingdom can do as easily. There are ways - but the dev focus is on SWOSaas. Pingdom has not changed much in years. Pingdom is still a darn nice product though. 

Why have pingdom or swosaas if you have wpm? External probes. Not having to administer external probes is a bonus too. Also - lots to say for have an external web monitor that can verify issues or point out issues such as DNS locally or externally. WPM does integrate with pingdom transactions, I wish it would with SWOSaas - but I do not believe that is in the works. 

jklundy said:

2) Licensing.  WPM is licenses per recording playback location.   So even if you use the same recording, if you monitor from 2 different players, that is 2 licenses.

WPM is licensed per WPM Transaction - meaning that you can have as many WPM Players connected to main pollers as you want but you can assign to them only as many WPM Transaction as the license allows. For example, you can have 5 WPM Players in your setup and have WPM license to 10 Transactions. With that license limit, you can assign 10 WPM Transactions to a single WPM Player or spread them on two or more WPM Player locations. If more transactions are added to your env, the license manager will disable transactions that exceed the license limit after some short period of time.

documentation.solarwinds.com/.../wpm_licensing_model.htm