Custom properties – How do you use them? SHOW US

solarwinds_worldwide_llc over 8 years ago Less than one minute read time

We are working to improve the onboarding process for NPM and SAM. As such, we are looking for real world examples of every-day practical ways our customers can use custom properties. We would like your real world examples of using custom properties to:

Set up alerts
Customize reports
Customize views

Please describe how you use custom properties and add a screenshot of how you are using custom properties in reports, alerts or views (a picture is worth 1000 words). As a thank you, we’ll get you 500 thwack points.

Top Comments

Parents

cahunt over 8 years ago

All of these, intensely! The AJAX / TREE View is all Custom Properties broken down into locations and buildings for visual display. My favorite module to use are the Top XX Reports that are malleable to the effect of isolating area's by patient care & non patient care, Distribution & Core, Access Layer, Data Center, Remote Sites & Remote Patient Care Sites. Pseudo NOC view was just updated yesterday for high usage views. Broken in two for Data Center & Non Data Center.
Beyond that Custom Properties separating Distribution & Access Layer, and SAN, etc, etc. add to the granularity of views, I have 1 module for usage of Distribution Nodes, and another next to it for the access layer.
Further broken down with SQL queries that remove the DIST Labeled interface on the access layer - create more to see(as my problems page in the NOC view rotation includes a small view of both sides of the top used interfaces. That coupled with the Top Errors, and Top Errors this hour (again sql to filter discards on a module to show only the errors) allow a sight manipulation of the display to show/isolate current issues. This also has an edited module here and there on certain pages to show Data Center & Non Data Center and also to Isolate and show Core & Distribution Usage and errors.
I like to use a physical grouping as well as a type or usage grouping also. Break down is not limited to - Core & Distribution, Access Layer, Appliances/Servers of varying network management type, PD Cameras, Telehealth Devices, Building Management & Automation Devices, Telecom, Wireless Dist, Wireless Controllers, There used to be wireless access layer but that was consolidated with our last refresh, PCI, Out of Band, Facilities, Time Clocks AND also Location aspects throughout the AJAX display.
Main part of the location distribution effort on the first level of display is our Access Layer - Immediate Status Display of Campuses, then broke down into Buildings.
Higher Functioning items are broken into device or usage type on first level of display and then location - usually building and then floor.
Of course Groups are used for display limitation - as I find this easiest - but users AJAX views (for users outside of our group or engineering) are broken down into regions or buildings then floor.
Alerts - Custom Properties used for alerting different device types to different departments. Isolated Distribution/Core Alerts aside from Access (mitigated email groups using the different alerts) - many cases this is just a copy of an existing alert and a change of that custom property to create the new alert for group/department involved. Use of Multiple custom properties in an alert (and even reports) can allow the granularity needed when trying to highlight certain area's or devices or alerting. Specifically those like devices (same vendor mainly or even device type) that have different functions and/or locations.
Reports - using the custom properties we have generated reports for certain departments, groups and property management
Maps - Having a custom sorting or search option when making maps is crucial when you have multiple nodes at multiple sites ; anything to keep from having a long list of nodes to scroll through and add to your maps.
Names were covered to protect the innocent.. AJAX, everything you see is a custom property... you see 2 levels.. after that it either breaks into the Building Acronym (which you see some that is okay to share) or floor - for those where you already see the building. Campus Sections are access layer, and routers for remote sites... WAN in included with the distribution section.
The Usage views has another one that is non Data Center that shows Distribution on the left and access layer on the right (filtering for interface descriptions with DIST, and to type of proprietary virtual to remove the up links back to distribution which would be displayed on the distribution if a top talker. SAN also broken off in this DC view.
The idea with these views is to show traffic on the isolated layers of 2 & 3.
- Cancel
- Vote Up +3 Vote Down
- Sign in to reply
- More
- Cancel

Comment

cahunt over 8 years ago

All of these, intensely! The AJAX / TREE View is all Custom Properties broken down into locations and buildings for visual display. My favorite module to use are the Top XX Reports that are malleable to the effect of isolating area's by patient care & non patient care, Distribution & Core, Access Layer, Data Center, Remote Sites & Remote Patient Care Sites. Pseudo NOC view was just updated yesterday for high usage views. Broken in two for Data Center & Non Data Center.
Beyond that Custom Properties separating Distribution & Access Layer, and SAN, etc, etc. add to the granularity of views, I have 1 module for usage of Distribution Nodes, and another next to it for the access layer.
Further broken down with SQL queries that remove the DIST Labeled interface on the access layer - create more to see(as my problems page in the NOC view rotation includes a small view of both sides of the top used interfaces. That coupled with the Top Errors, and Top Errors this hour (again sql to filter discards on a module to show only the errors) allow a sight manipulation of the display to show/isolate current issues. This also has an edited module here and there on certain pages to show Data Center & Non Data Center and also to Isolate and show Core & Distribution Usage and errors.
I like to use a physical grouping as well as a type or usage grouping also. Break down is not limited to - Core & Distribution, Access Layer, Appliances/Servers of varying network management type, PD Cameras, Telehealth Devices, Building Management & Automation Devices, Telecom, Wireless Dist, Wireless Controllers, There used to be wireless access layer but that was consolidated with our last refresh, PCI, Out of Band, Facilities, Time Clocks AND also Location aspects throughout the AJAX display.
Main part of the location distribution effort on the first level of display is our Access Layer - Immediate Status Display of Campuses, then broke down into Buildings.
Higher Functioning items are broken into device or usage type on first level of display and then location - usually building and then floor.
Of course Groups are used for display limitation - as I find this easiest - but users AJAX views (for users outside of our group or engineering) are broken down into regions or buildings then floor.
Alerts - Custom Properties used for alerting different device types to different departments. Isolated Distribution/Core Alerts aside from Access (mitigated email groups using the different alerts) - many cases this is just a copy of an existing alert and a change of that custom property to create the new alert for group/department involved. Use of Multiple custom properties in an alert (and even reports) can allow the granularity needed when trying to highlight certain area's or devices or alerting. Specifically those like devices (same vendor mainly or even device type) that have different functions and/or locations.
Reports - using the custom properties we have generated reports for certain departments, groups and property management
Maps - Having a custom sorting or search option when making maps is crucial when you have multiple nodes at multiple sites ; anything to keep from having a long list of nodes to scroll through and add to your maps.
Names were covered to protect the innocent.. AJAX, everything you see is a custom property... you see 2 levels.. after that it either breaks into the Building Acronym (which you see some that is okay to share) or floor - for those where you already see the building. Campus Sections are access layer, and routers for remote sites... WAN in included with the distribution section.
The Usage views has another one that is non Data Center that shows Distribution on the left and access layer on the right (filtering for interface descriptions with DIST, and to type of proprietary virtual to remove the up links back to distribution which would be displayed on the distribution if a top talker. SAN also broken off in this DC view.
The idea with these views is to show traffic on the isolated layers of 2 & 3.
- Cancel
- Vote Up +3 Vote Down
- Sign in to reply
- More
- Cancel

Children

No Data

Thwack - Symbolize TM, R, and C