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

Error state when non critical interface are down

CEllsworth

here's my scenerio. We're using orion to monitor all the links comming off all our switches (to client pc's) and I want to leave this enabled, for the purpuse of finding bandwidth hogs. Except I dont want the device to show an error state that one of these trivial links is down, only show an error state if one of the important interfaces is down (you know, the ones with the business critical servers dangling off of them).

Is there any way to mark some interfaces less important than others?

Find more posts tagged with

Accepted answers

All comments

Isaac

Not today.

This has been requested repeatedly in the request new features thread. To date there have been no replies.

Ask for it enough and you may get it.

I would recommend contacting SW support to see if anything like this is in the pipeline if it is critical to your organization.

Be fantastic!

pwinterhalder

Unless I'm mis-understanding, why can't you untick the ports from within the alerts window?

Phil.

Network_Guru

quote:Originally posted by pwinterhalder

Unless I'm mis-understanding, why can't you untick the ports from within the alerts window?

Phil.

That does not affect the status of the nodes/interfaces on the web page. They will still show as blinking red on the Node(switch) and red on the interface/link which is down.

It sounds like we need a "semi-managed" node configuration setup - collect stats, but don't report on status.

-=Cheers=-
NG

jkoebel

Is there any update on this? It would seem rather simple to add another checkbox allowing just the collection of stats on an interface. This would be extremely helpful.

John Koebel

skaczkowski

I agree, this would be a great addition...

-Steve

mattand666

Yep - that would rock.

aLTeReGo

Considering Orion is licensed per element, or per-interface in this instance, you'd think it would be in their best interest to satisfy this feature request.

jba

Agree, i would love to see this feature in the next release

mhh351

I agree with all of you. I asked fro this back in release 7.0. A simple check box to NOT monitor up/down status would be the best. Our scenario is such that with our 700 some servers, our server switches need to be monitored for stats but not for status, as mentioned in one of the other messages for end-users.

A check box tothe RIGHT of the interface for STATUS monitoring would be a good design, with a SELECT ALL for STATUS box in the right column. If one were to select ALL FOR NON-STATUS monitoring and then choose the ones that should be monitored manually, the issue would be fixed. Just my 2 cents worth.

Strongly agreed -- Statistics collection only without status monitoring would really be very helpful, to prevent pollution of my network maps and alerts.

NasaGeek

If I understand correctly, this would also solve my issue with force monitoring interfaces not in an up/up status.

Having to come to a seemingly quasi-supported forum to ask for future requests seems a bit unprofessional to me. I am about to start rocking the boat, not here obvioulsy. See my post in this forum "Forced Polling on Non Up/Up Interfaces" that has yet to be replied to by a Solarwinds employee.

I also don't care for the blinking red icons, and if we can kill two birds with one stone then this seems like a great request, and I will press the issue.

swilliams

Any response on this yet?

FormerMember

I'm looking at the original problem, and you want to alert on a down state for some interfaces but not others. That's very possible today using custom properties. Label some interfaces "Critical" and other interfaces "NotSoMuch". Then add "custom property=critical" as another condition on your alerts.

Although you will still see that status as down on the web, you can use filtering in your resources to do what you want. For instances, you can add two instances of a resource and filter one to show Critical interfaces only.

Does that address the original issue?