This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

WAN utilization report

I need a daily report that will show us any circuit that has been at 80% utilization for over 20 minuets. Can any one help with this?

I am very new to solorwinds but have had some success with making custom reports but only with good instructions emoticons_happy.png.

I would also like an alert to go out when this occurs..

  • You can start with the attachment.  copy it an place it in your reports directory and open the file with the Orion Report Writer.

    Normal path for the report Directory = C:\Program Files (x86)\SolarWinds\Orion\Reports

    The report uses the Interface caption of "Wan" to filter the results.

    the report will give you a report that show the last 24 hours and if a interface goes over 80% on receive or Xmit.  if you can find a way to make it only report if it hits the 20 min mark, add it.

    you will need to take this report and run the report scheduler in order to get daily reports.

  • Can't help you with the report but for the alerting I use Advanced Alert Manager. I have 2 alerts, one for Transmitting and one for Receiving. I use these alerts to only report on the links to my remote sites. I get an email when a remote link is running over 90% for at least 10 mins. I get a reset email when the link drops to 50%.

    I set Type of Property to Monitor in Trigger Condition to Interface, I use the Node Name to only monitor remote routers. I use Interface Caption to only monitor the external facing interface on these remote routers (they all contain a same keyword). And then I use Recv Percent Utilization is greater than 90 (you would use 80 in your case). Then I've set 'Do not trigger this action until condition exists for more than' to 10 mins (you would use 20 mins). I've set the Reset Condition to Recv Percent Utilization is less than 50.

    For Trigger Actions I've set it to email me the following

    Interface <b>${NetObjectName}</b> on node <b>${NodeName}</b> received at <b>${Interface.InPercentUtil}%</b> of its utilization, which triggered this alert.

    I also include a hyperlink to goes directly to the interface so you can see the netflow data (if available) to see what's using the link.

    For the Reset Actions, I've just set it to email me the following.

    Interface <b>${NetObjectName}</b> on <b>${NodeName}</b> received at <b>${Interface.InPercentUtil}%</b> of its utilization, which reset the alert trigger.

    I've used a description subject so that you can easily see if it's a RESET email or not.

    Hope that helps.

  • Thanks gunner2510 for your help!

    I added the report and modified it a bit for testing (lowered the utilization % and set the filter to filter on machine type contains Cisco)

    When i preview the report in Orion Report Writer I see exactly what i need but when i run the report from our orion web interface I get no results.

    Any idea what i'm missing?

  • This looks like a perfect complement to the report gunner2510 suggested above.

    I can use the report for weekly review and your alerts to be proactive on real time issues.

    I will work on the alert now but may have some questions for you as I set it up emoticons_happy.png

  • That is a good one. Since it is the same report and the same database, I would look at an IIS issue. can you see other reports in the website?

  • all other reports seem to be working.

    for the new report I get the headers of the report but below that I get "No activity to report"

  • I fixed this issue by unchecking the "group historical data by day" box on the general tab. 

  • Great. I was racking my brain for a fix.

  • any idea how i could limit the results to only display the interface 1 time with it's highest % utilization (above 80%) instead of listing each time it went above 80%?

    As is an offending interface is listed 50+ times which makes the report hard to read.

  • I am not finding an easy way to create that report. I’ll keep trying