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

Customize Component Views for Only Selected Components/Applications?

I that that there was a way to customize component views and gauges within an application without affecting all of the other component views so long as the application was using a customized view; however that doesn't seem to be the case.

Is it possible to customize only specific component views without affecting all others?

Find more posts tagged with

Accepted answers

aLTeReGo

It is not currently possible to assign a custom component details view to a specific application, just like it's not possible to have a custom interface details view for a specific device or device type in NPM. Resources in these views will auto-hide if they're not applicable to the component type etc, so for many cases it shouldn't be necessary to have a custom component details view for a specific application. If you don't mind me asking, what's your specific use case? What are you trying to achieve using custom component monitor views for specific applications? Maybe this would be a good feature to post in the Ideas section of Thwack?

All comments

byrona

I am still struggling with this and would love to receive some feedback, thanks!

aLTeReGo

byrona

I will go ahead and create an Idea (Feature Request) for that tonight. My specific use case is that we have created a lot of custom script monitors (mostly for monitoring our facilities/data-center where having a custom component view would be a lot more appropriate. One of the more general issues is the gauge ranges. The default gauge goes from 0 to 2500 and in many cases this isn't appropriat; for example we have several components that monitor temperature where 120 should be the top end of the range however that isn't a good range for an HTTP response time gauge.

Does this make sense?

aLTeReGo

That makes sense. Ideally the gauge range would adjust dynamically based upon the statistical value returned from the component in relationship to the warning and critical thresholds as they're defined in the component settings.