If you want to capture website URLs then one option is to use packet capture to extract the URLs via a SPAN or mirror port. Once you have your SPAN port setup you can use an application like LANGuardian which can also integrate with SolarWinds Orion. Demo at link below
Actually i am talking about simple process like in OPManager just monitoring URL through ICMP.
That way can't do in solar winds.
Thank you for your response
If you have SAM, you can use the HTTP monitor template to test any URL.
If you're only looking to test if SolarWinds can ping the the website, just add it as a node, polling via ICMP. As long as your pollers have access to the internet (and a suitable DNS server) this should work. If DNS is a problem, just put the site's IP address in the HOST file on the poller and make sure you add a suitable route in the routing table of the server so it knows which interface should get it to the IP.
Messy, but it should work.
I don't have any node but i have only websites urls then how do i do it?
If the website you're monitoring has a static IP address (i.e. it's not on more than one host/IP address), you can add it to SolarWinds via 'Manage Nodes' under settings. When adding the node, put in the public IP address for the website, and choose ICMP only as the polling method. Once it has been polled successfully, name it something that makes sense to you before clicking ADD NODE at the end of the wizard, and you're done.
However, this is reliant on your poller having access to the internet. If it doesn't, this method will not work.
silverbacksays has described a method we use extensively. If you're poller doesn't have access to the internet you can assign the SAM template containing your HTTP(S) monitor component to any node and hard code the URL into the component settings.
1 of 1 people found this helpful
If you are using Cisco Equipment in your network, use and IP SLA Operation process (see Cisco Doc for configs). To start, take the default settings plus the times you want this to be acted on, say every 5 minutes.
I used this because some websites do not permit ICMP PING. Pinging the website is therefore useless!!!!!
For example: If you wanted to monitor a site that may do your payroll functions, to make sure it is up, construct an Operation to test for a positive response from the first page. Once that functions, you can get the information out of the Cisco device and use that to monitor in NPM.
Here is an example that I have used on a switch. I have blanked out the IP address and the tag (label for the operation).
ip sla 216 (operation number of your choosing from 1 to who cares)
http get http://0.0.0.0 (your needed destination IP address from the website is here)
tag [your title here]
frequency 300 (every 5 minutes)
Then enter "exit" to return to "config" level
ip sla schedule 216(or whatever op number you used) life forever start-time now (this statement is NOT in the IP SLA Config but rather in the "config" level.
To monitor the OPERATION while in the device, enter the command:
Sho IP SLA MON <return>
do this several time against the operation noting that you have put a delay of 5 minutes in between intervals. Run the show command for about 20 minutes to see if your results are what you expect.
When satisfied, use a custom poller such as this in NPM:
Use SW Tools to find the mibs you desire or start at the following mib in the mib tree:
First, look for the mibs starting at 22.214.171.124.126.96.36.199.188.8.131.52.1.1 which is the RTTMON-MIB:rttMonLatestHttpOperRTT mib. This is the Round Trip Time taken to perform the HTTP operation.
Also, you will want 184.108.40.206.220.127.116.11.18.104.22.168.1.3 and 4 and 5 and 6. These will assist you in getting some meaningful stats.
I suggest that you either create a chart to be used on a separate page or use it on the page(s) of the specific device. You might also want to create this in Chart form so that all of the values show up on a single chart. If you need help with that, let me know.
Thirdly, and I'm sorry that this is so long, create an ALARM that looks for a value of ZERO from the .6 portion of the mib. If the value is "1", it was successful. If it is zero, you need to know this. You can vary the amount of time before an alarm is tripped but get it to work first.
To test the alarm, block the IP address in your network to get the failure.
One final note, to change any values in a Cisco IP SLA operation, you must delete the entire operation (no IP SLA number). First copy your operation commands and put them in notepad. Then change the values or add the commands that you might want. Copy the entire new operation set and paste it into the Config T of the Cisco device. Remember that the last line needs to be done at the Config level.
I hope that this helps you and everyone else.