Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Network Performance Monitor (NPM) > Custom Properties - Video

Custom Properties - Video

Created by Jennifer Kuvlesky, last modified by Lori Krell_ret on Jul 26, 2016

Views: 39 Votes: 0 Revisions: 5

Overview

This video (4:28) will show you how to use the Custom Property Editor. First, we will take a look at the Backend Applications which offer advanced configuration options for Orion® and where to find them. Next, we’ll look at the Account Limitation Builder. 

 

Environment

  • Network Performance Monitor
  • Orion Core products

Video Transcription

The Custom Property Editor allows users to add descriptive properties to nodes, interfaces and volumes. It comes with a set of pre-defined properties or you can define your own. Custom Properties are very flexible and can be used for a wide variety of configurations in almost every area of the web console. Once created, the property values can be set by importing from .csv or text files, or manually set through the web console.

 

For this example, let’s go ahead and create a custom property to identify a node as a server or network device.

To create a property from scratch, go to Settings >> Node and Group Management >> Manage Custom Properties. Here, you have the option to manage current Custom Properties, or to create new ones.

Click the "Add Custom Property" button. At this point you will be prompted to define if the property is for a node, interface or volume.

For our example, we’ll select Node and click "Next". On this screen, we have the option of using one of several preconfigured property templates on the left, or creating a new custom property. We’ll select "Custom" and assign the property a name and description. Let's name the property "DeviceFunction" and give it a brief description. We also will define the format as Text, but there are other formats, such as numerical available.

We can also create a custom drop-down list for this property by selecting the check box next to "Restrict Values". Once selected, we have the option to create custom values for our drop down list. In this example we don’t need a drop-down list, so I’ll clear the checkbox and click "Next". 

Finally, we will assign this property to our nodes by clicking the "Select Nodes" button. In this window, you can select specific nodes or groups of nodes, and click the "Add" button to add them to our list, or use the "Select All" button to apply this custom property to all nodes.

Once we have our node list complete, we’ll click "Select Nodes" to exit this window.  

Click "Submit" to finish creating and assigning this property.

Once the process is complete, you will be directed back to the Manage Custom Properties window. Here, you can edit properties at any time, assign the property to additional nodes, import or export properties or even delete them.

Backend Configuration Applications are used in conjunction with the web console, and provide additional configuration options for Orion. They are found in the SolarWinds® Orion program group in the Start Menu on the Orion server.  From here they are grouped into categories such as “alerting, reporting, and mapping” so users can easily identify which category they are looking for.

 

The Account Limitation Builder is found in the Grouping and Access Control section and allows custom properties to be used as account or view limitations within the web console. These help ensure that administrators can create dynamic account limitations and site access so that users can only access information pertinent to their job or location. 

Add an Account Limitation by clicking the "Add" button. Here you can name the limitation and assign it to a custom property.

Under selection method, you have the options for Checkboxes, Pattern Matching or Single selection. Pattern matching allows you to use text strings and wildcards to specify the limitation. 

Check boxes allow you to select one or more values already defined.  Single selection will give the drop-down allowing only one option for the limitation value. Once created here, the limitations will show in the Limitations area of the Edit User section in the web console and made available to be assigned to user accounts. 

Let’s go ahead and add an account limitation for our DeviceFunction custom property.  Now in this case, let's just select the property first and the name will be automatically populated so there is no need to fill that part out.  You may have users that need access to devices with different functions, if so, you can make this a “check box” limitation.

Now that we have our Account Limitation built, we can apply it to a user account. Going back to the web console, click "Settings" and then "Manage Accounts". Let's select "Cheryl" and click "Edit". Then, under Account Limitations, click "Add Limitation", and since Cheryl is a network admin and doesn’t need to see the server details, we can go ahead and remove them from her view by selecting only “Network”. Once configured, save the changes and that will apply the limitation to the account.

 

 

Last modified
13:44, 26 Jul 2016

Tags

Classifications

Public