nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

10.1 Upgrade - Tons of bogus "High Response Time" alerts.

MarkHofmann

I just upgraded our Orion NPM to 10.1 today and ever since, have been receiving "High Response Time" alerts on various Cisco managed switches/interfaces. It will then send the Reset alert shortly afterwards.

The high ms response time alerts are NOT reflected in any of the graphs. They seem to be some type of bogus problem that comes and goes on various devices.

I saw this problem back on 10.0 - and was wondering if anyone was having it again with 10.1?

Any ideas, please let me know. Thanks.

- Mark

Find more posts tagged with

Accepted answers

MarkHofmann

Jason,

That is similar to what I had to do. The default time to trigger the High Responsetime alerts was set to 0 seconds. I changed it to 3 minutes and it appears to have helped greatly.

- Mark

All comments

eiab

I also have strange behaviour with response times.

acctual message:

Alert: Node XXX has exceptionally high response time. Average Response Time is 552 ms and is varying from 22 ms to 22 ms. Last Reset was Unknown

How can a response time varying between 22ms and 22 ms be an average of 552ms? The graphs don't report the high response times either. This hapens frequently on a number of nodes.

/Fredrik

robertcbrowning

The figures in your alerts are set as variables. Which variables are chosen for the email can totally change the meaning of it. I had a similar problem and had to correct the text around the variable.

Remember that averages are over a period of time, while specifics are spot values and are “right now values”. Notice how my alert sends the warning out because the time is 16ms, but the recent average is 627ms. The link had just recovered & looks wrong, but it is accurate. If you check it with the Toolset (and poll it much more frequently), you’ll see these figures fluctuate.

Sample email (with specific data replaced with italics)

16 November 2010 01:35 10.21.16.242 High Response Time

10.nnn.nnn.nnn is currently responding to polls in 16 ms, but has recently been responding in an average of 627 ms. The node is configured on polling engine PollingEngineName . The device is in City and affects Company.

URL to the node

(Alert=(Networks) High Response Time)

Source email text

${DateTime} ${NodeName} High Response Time${CrLf}

${NodeName} is currently responding to polls in ${ResponseTime}, but has recently been responding in an average of ${AvgResponseTime}. The node is configured on polling engine ${SQL:Select ServerName From Engines Where EngineID = ${EngineID}}. The device is in ${City} and affects ${Company}.${CrLf}

http://solarwinds.DomainName.com/Orion/NetPerfMon/NodeDetails.aspx?NetObject=N:${Node.NodeID}${CrLf}

(Alert=${AlertName})

MarkHofmann

Below is what I currently have for "Response Time" alerts.

Alert: ${NodeName} has exceptionaly high response time. Average Response Time is ${AvgResponseTime} and is varying from ${MinResponseTime} to ${MaxResponseTime}.

Here is what I keep seeing for tons of nodes on our network (had 300+ alerts just overnight). The trigger and reset alerts below were less than 1 minute apart.

Alert: BL2A has exceptionaly high response time. Average Response Time is 209 ms and is varying from 209 ms to 209 ms.

Reset: 11/23/2010 08:39 Average Response Time of BL2A is 7 ms and is varying from 7 ms to 7 ms.

Something is broken with the alerts in 10.1 - at least with my install.

I have also seen bogus "High Packet Loss" messages that are similar to the Response Time messages. I don't see any of this reflected in any of the charts, real time polling, etc. Just the alerts. I'm going to call support today to see if they can figure out what is going on.

Thanks.

- Mark

MarkHofmann

Worked on the issue today with support - was informed that basic alerts are going away and not supported, to use Advanced Alerts. Configured the same Alert for High Response Time in Advanced Alerts only to have the same outcome.

Will let everyone know once this is solved. As or now, I have High Response Time alerts and High Packet Loss alerts in 10.1 disabled.

It seems the graphs are showing the correct information - but they are the only ones with the correct info on that subject.

I have between 1-10ms response time on local nodes and somehow the 10.1 Orion is showing these same nodes at times having 250-380 or more ms response times at times, which is invalid.

Hopefully we will get to the bottom of this soon. I do like the 10.1 upgrade features, but this problem is driving me nuts (and everyone else at my work that received the hundreds of bogus alerts).

- Mark

rrutkowski

Has anyone heard an update on this? I updated to 10.1 last week and have been having the same problem. We get email alerts constantly about 100% packet loss for random devices even though I can ping them just fine.

FormerMember

Since the upgrade to 10.1 we were also seeing loads of event log entries for high utilization and after looking in the advanced alerts there were 2 new ones for Top Talkers. This was configured to alert when the condition had existed for 0 seconds. I just amended this to be 5 minutes and the problem went away.

Also it had a default entry to send an email to <EnterEmailAddress> and this was filling the windows event log up with loads of failed attempts to send emails.

Hope this helps!

Jason

MarkHofmann

Jason,

That is similar to what I had to do. The default time to trigger the High Responsetime alerts was set to 0 seconds. I changed it to 3 minutes and it appears to have helped greatly.

- Mark

pacetti

The following Knowledge Base article covers all known possible causes of this condition:

I am seeing High Response Time alerts in the web console without corresponding values displayed on response time charts.

http://knowledgebase.solarwinds.com/kb/questions/2106/