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

Creating a template, to monitor specific things?

waqas.ahmed.bw

Hey,

I'm looking to make a template so we can monitor a group of devices, ie: just say the CPU load, or just say the disk load. We don't need to see every thing for every single device, but we'd like this relatively automated as well, to make it a bit easier to manage

Does any one know of such a way?

The product in question is the "Network Performance Monitor" I think I posted this in the right area

Any help would be much appreciated.

Thanks.

Find more posts tagged with

Accepted answers

All comments

d09h

If you onboarded the devices via a Network Discovery, that functionality already exists to a certain extent. During import, you can limit what you bring in.

Automatically add discovered nodes

check out steps 5, 8, and 9

Automatically add discovered nodes

Automatic monitoring means you do not have to go through the Discovery Import wizard every time you run a discovery. It is useful when you have configured your discovery to find similar nodes or network devices.

Click Settings > Network Discovery, and add a discovery, or select an existing one and click Edit.
Click through the Discovery Wizard to the Monitoring Settings page.
Choose to include devices that only respond to ICMP (ping). If you decide to exclude devices that only respond to ICMP, your discovery list may be smaller than you expect and you must add those devices manually.
On Monitor Settings, select Automatically monitor based on my, and click Define Monitoring Settings.
Select the interfaces properties you want to apply to any discovered nodes and click Next. You can also create advanced filters for interfaces under Advanced selection options. This option is available for NPM.
For switches, routers & firewalls, select Up trunk ports and wireless access ports.
For servers, select Up interfaces.
Use Advanced Filtering Options for existing interface descriptions to choose your most interesting ports, such as 'uplink', 'WAN', etc.
Choose the types of volumes you want to monitor.

d09h

You can also limit what you view (this doesn't limit polling):

Assign views by device type

jvb

You could do a couple things... One would be to add a custom resource to a page and use a filter to only show certain resources on certain nodes (screen shots below)

You may also want to consider looking at Custom Properties to do more logical groupings on your devices.

Create a custom property

Click Customize Page in the upper right corner:

Click the plus sign in one of the columns to add a resource:

Use the search bar to find a resource, in this case I selected a particular CPU resource:

That will result in a new resource / widget on your page which you can then edit:

Then use the "Filter Nodes (SQL)" section to filter that resource (there are some examples included on the edit dialog):

waqas.ahmed.bw

Thanks all

wlipford

This is all good, but you would bring in everything and filter out on views. Not ideal with a large estate.

We have over 30k nodes in NPM, I am doing a import of 5000 right now, so I only want 3 interfaces per node and I can't bring everything in.

jvb

wlipford... In that situation (unless I am misunderstanding you) you would want to limit what gets pulled in

using the "Interfaces" section of the discovery results. That way you don't have to filter out resources you didn't wish to monitor in the first place.

As you can see below it is possible to specifically select or ignore interfaces.

wlipford

exactly, and when you are doing thousands of devices then selecting what interfaces to ignore is very cumbersome. I guess what I was really griping about is the fact that the system doesn't have a way to set reg-ex templates of some sort. It is also VERY annoying that you can't exclude devices from being imported into NPM. It just adds another step of my automation scripts going back and removing them from NCM.

My workaround was basically to let the discovery complete, then go into the discovery results and change the up/down status of the interface based on my pearl regex routines, then simply select all UP interfaces and import. Not ideal and subject to breaking if anything gets changed in the DB schema for Discovery.