This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

APM creates false positives on http (port 80) requests but not https (port 443) requests on same website

AustinLaz over 15 years ago

Hello everyone,

This recently popped up in our environment with no changes to any solar winds configuration. Also, to mention, no-one in any of the IT teams is fessing up to changing anything in the last 36 hours so we will have to assume the detective role here.

We use APM to actively monitor some of our websites. As of 10:00 AM yesterday, we've received a ton of emails of the websites goign up and down on the websites that we are monitoring via http. When we checked on them, and IIS, they were just fine with no issue. It's also not staying constantly down or up, but seemingly going down the list of websites and showing them randomly down and up at different times. However, their https addresses for a specific sub-page are working just fine. So as a test, i sent the address to the https:// main address that we are checking with http (yes it does exist). The errors do not occur on those.

So for anyone who might have experienced anything like this, where can i look or assume is the issue? Anyone have this issue before?

0 josh.clark over 15 years ago

When the HTTP monitor is showing as down, what is the error message shown?
Cancel
Vote Up 0 Vote Down

Cancel
0 AustinLaz over 15 years ago in reply to josh.clark

I guess i am confused... all the error is showing is:
<monitor name> for <monitor template> on <Server> is down

The above entries have been stripped of their actual data for security purposes.
Cancel
Vote Up 0 Vote Down

Cancel
0 AustinLaz over 15 years ago in reply to AustinLaz

Ahhh, i think i have found what you are looking for. Under moreinfo it says the following:
Network Connection failed.
Cancel
Vote Up 0 Vote Down

Cancel
0 josh.clark over 15 years ago in reply to AustinLaz

Ahhh, i think i have found what you are looking for. Under moreinfo it says the following:
Network Connection failed.

That error means that we could not connect to the target server. Is there a network issue going on either for the Orion Server or for that machine?
Cancel
Vote Up 0 Vote Down

Cancel
0 AustinLaz over 15 years ago in reply to josh.clark

Again, not that we know of. We're able to remote into each machine, open the web pages manaually from Orion and from any other machine and from the machine itself. Also, using port 443 we have no issues.
Cancel
Vote Up 0 Vote Down

Cancel
0 gbrance over 15 years ago

I started seeing the same thing this weekend. We use APM to monitor if WebSense is working (Internet Filtering). We basically have a HTTP monitor try and go to a website that we know is blocked. If it gets the specific text that is on the block page it will be in up status. However this weekend we received a alarm that WebSense wasn't working. I would remote in and I would verify that it was working and the web page is being blocked. Then on Sunday I got a alarm that it started working again with no changes. Then about 8 hours later I got another alarm that it went down again. Kind of frustrating.
Cancel
Vote Up 0 Vote Down

Cancel
0 JasonKV over 14 years ago in reply to gbrance

Any progress on this problem. We are encountering something similar and need ideas to figure out more details of our problems.
Cancel
Vote Up 0 Vote Down

Cancel
0 FormerMember over 14 years ago in reply to JasonKV

The error message appears when there are network connectivity issues involved. If you need help troubleshooting, you should open a support ticket.
Cancel
Vote Up 0 Vote Down

Cancel

0 BakerD over 14 years ago in reply to gbrance

I started seeing the same thing this weekend. We use APM to monitor if WebSense is working (Internet Filtering). We basically have a HTTP monitor try and go to a website that we know is blocked. If it gets the specific text that is on the block page it will be in up status. However this weekend we received a alarm that WebSense wasn't working. I would remote in and I would verify that it was working and the web page is being blocked. Then on Sunday I got a alarm that it started working again with no changes. Then about 8 hours later I got another alarm that it went down again. Kind of frustrating.

I would like to know how you set this up. I'm new to APM, but because of a bug in the code we are running on our firewall, occasionally our web filtering stops. Can you step me through how you set this up?

Thanks

EDIT: I figured out an internal solution, so hopefully I can apply that to an external site. See my post