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

Map and an Unmanaged child object

I don't want upper-level map objects to turn blue when a node becomes 'unmanaged'.

So, is there any way to not include the blue-colored UNMANAGED objects or maybe not allow them to propagate into the maps?

Find more posts tagged with

Accepted answers

All comments

Congo

I am in the same boat on this. The icons for unmanaged on maps is horrid.

bshopp

So you have a sub-map with multiple nodes and you unmanage one of them and the icon on the parent map goes blue? How is this coming into play in your environment?

lchance

The Unmanaged-BLUE overrides anything 'critical' or down (Yellow & Red is mostly my experience and my needs).

I don't want to see BLUE here...

When what I really need is to be seeing Yellow or Red...here...

Congo

We have a top level map from which you can drill down into our 18,000+ elements, spread across hundreds of submaps. If any one of those goes unmanaged, this tier 1 map, or even the tier 2 maps (which are sometimes used as views for entire departments) goes into this tacky blue dot.

So really, this is a half a cosmetic and half a functionality issue for us.

overview.png

bshopp

Perfect, thanks for the great descriptions, this is a known issue we have filed in the system and we are working on resolving it