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

Best Practice for Internet Connectivity monitoring

Hi,

We currently have NPM and APM and need to monitor the connectivity to the internet as we have had issues with the firewall.

Have tried setting up APM (web link) to monitor Yahoo, but we have rec'd false positives as I believe a link on the page was down.

What would be perhaps the best practive toi monitor Internet Connectivity?

Find more posts tagged with

Accepted answers

All comments

FormerMember

personally i have found the HTTP monitor in APM incredibly unreliable... the reported response time is around 100 times higher through APM than it is if i use internet explorer from the Orion server to get to the same URL!!

I am going to try and migrate to an IP SLA probe that sits in our network to poll port 80 on the web servers... and use solarwinds to pull the SLA results and alert on them....

cheers

dan

byrona

My understanding is that the problems with APM and the HTTP monitor has been resolved in the current version, is this not the case?

IP SLA is a great way to do this. We have implemented a state wide network performance monitoring scheme using IP SLA and it's pretty amazing. We actually did this all before the IP SLA tool was available through SW so all of my collections and thresholds are done using good ole NPM and UnDP. Hopefully at some point I will get approval to get the new SW IP SLA tool for this.

FormerMember

if it is fixed in 3.1 APM i will be a happy man, but i have already seen a few false positives, so i will have to do a few checks,...

i am lucky enough to have SLX everything... but i have only just installed IPSLA, so I have not actually used it for anything yet... i am a Fluke response watch person historically

tbell52

We use the HTTP monitor and have it check http://www.google.com. We were getting a lot of false positives at first, but we haven't had any in a long time. One of the things we did to fix it was upgrading to APM 3.0. Also we found it was better to enter the full address of http://www.google.com and not just google.com or www.google.com. Changing the User Agent to Mozilla/4.0 also helped with the response time. We have several internal web sites that we have to check and when we changed the User Agent it cut the response time in half on most of the pages.