Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > Network Performance Monitor (NPM) Training > Free SolarWinds Training Videos - NPM > Create a New View - Video

Create a New View - Video

Updated March 11th, 2016


This video (5:41) demonstrates how to create a new view, customize views, and manage views. 




Orion Platform v2016 and above.

Server & Application Monitor  v6.2.4 and above

Network Performance Monitor v12 and above

Virtualization Manager

Network Traffic Analyzer         

Storage Resource Monitor  

Network Configuration Manager 

Web Performance Monitor

IP Address Manager

User Device Tracker                                                        

VoIP & Network Quality Manager


Video Transcription

Before we show you how to build a custom view, we'll offer a quick word of caution when it comes to managing views. Building and editing custom views is really easy. In fact it might be argued that sometimes it can be a little TOO easy. You’ll notice that in the top right-hand corner of my view there’s a handy little customize page button. And this takes me directly into my view editor where I can add resources and move things around.

While this is a very powerful capability, most Orion users may not understand that when they make a change to a view, that change isn’t just applied for them, it’s applied for everyone with access to the view.
There are a lot shared views in Orion but when you go into the view editor, there’s no warning. You have to understand what you’re doing when you’re creating new views and especially when you’re editing existing views, so that you don’t mess things up for anyone else.

If you are the one and only Orion administrator, then this won’t be a problem. However if you have a lot of users logging in to the web console, you need to be extremely careful about who gets view management rights. View management rights is one of the permissions in the individual user accounts. If a user doesn’t have view management rights, then they can’t create new views and they also can’t modify existing views, so the customize page button isn’t even there for those users. So just a word of caution, if you’re managing a large environment with a lot of Orion users logging in, don’t give them all view management rights. 
With all of those warnings, let's go ahead and build a custom view.
Go to the settings menu and select the All Settings link
This will take you to the Main Settings and Administration page.
Scroll down the page to the Views resource and select Manage Views
This brings up a list of all your existing views. Here you can edit a view, make a copy of a view, or create a new view from scratch, which is what we want to do. So I’ll click on Add.

The first thing you need to do is give your view a name. But let's pause again for just a moment and talk a little about view management. When building custom views, you shouldn't build views for individuals, but rather build views for certain roles, like network admin, or helpdesk staff, or security admin. 

Even if all the roles need the exact same information, it is not recommended that you share views between them. Inevitably, one of those teams is going to want something different and make a change that affects other teams as well. Instead, you can make a copy of the view and assign one copy to one group and another to the other group. This makes our naming convention very important.
Next you’ll choose the type of view you’re going to build. If you click the dropdown you’ll see that there are a number of view types and below the dropdown is a brief description of each type. The view type you choose is going to determine two things. First, it determines which resources you have available to build your view. You have literally hundreds of resources to choose from, but not all those resources are available in every view type. So make sure you choose the right view type or you’re not going to see what you want. The second thing the view type determines is whether or not the view has to reference an object. If you look down through the list, you’ll see that we have two basic view types. We have Summary views and Details views. Details views have to reference an object. Summary views do not. You’ve probably already noticed this. One of the first views most people see is the Node Details view, which has to reference a specific node to populate the informational resources within the view. Pay attention to the view type you choose because once it’s set, you cannot change it.

Once you’ve got a name and a view type, click submit. 

And this brings you to the view editor. Up at the top you see the name of the view and the view type, which again notice you cannot change. Below that you have Left Navigation. If you turn on left navigation, this will allow you to create sub views. Sub views are identical to regular views except that they are assigned to one of the navigation tabs. In fact you’ll see your sub views included in the list with all the others when you click on Manage Views from the Settings page. They’ll be saved as the name of the view – the name of the tab. So this sub view would be called Summary – junior admin – Custom tab 2.

Sub views are great any time you have more information than fits comfortably in a single view, or if you have a particular resource that just takes up way too much screen real estate. You can move that resource to a sub view where you still have easy access to the information, but it doesn’t clutter up your main page.

We don’t need sub views for this particular view we're building, so we will just turn off left navigation. Notice when you do you, get a pop up that says - do you want to delete sub views? Be aware of this because this isn’t a negotiation, this is going to happen, the sub views are going away. But at least it gives you a friendly heads up and a choice of whether you want to preserve view information by cramming all the resources onto the main view or just let them be deleted with the sub views.

Below the Left Navigation check box we have the view layout editor. The view starts out with two columns by default, but you can go up to as many as 6 columns. Below each column you’ll see the column pixel width. Keep in mind that the columns are fixed pixel width; they will not scale to accommodate resources that are too wide, nor will they scale to match the full width of the display size. So you need to keep those two things in mind; how wide is the widest resource you’re going to include in the column and at what resolution will your users be viewing this page?

After you set your column widths, you’ll need to click done to save the views because those column widths won’t stick until the view is saved. If you don’t save after changing the column widths the column width settings will end up being lost when you make certain changes to the view, like adding new resources or view limitations. 

Last modified