Device Groups and Device Templates

SL1 version 12.1.0

Table of Contents
What is a Device Group? 4
What is a Device Template? 6
Creating and Editing Device Groups 7
Before You Start 7
Viewing the List of Device Groups 8
Filtering the List of Device Groups 9
Special Characters 10
Creating a Device Group 13
Adding and Removing Static Devices and Child Device Groups 17
Adding Dynamic Rules 18
The Relationship Selection Page 27
Editing and Deleting Dynamic Rules 31
Creating Device Groups From Views 31
Editing an Existing Device Group 32
Assigning Devices to a Device Group During Discovery 32
Controlling Access to a Device Group 33
Defining the Actions for a Device Group 33
Deleting a Device Group 34
Example of Creating a Device Group 34
Creating and Editing Device Templates 36
Before You Start 37
Viewing the List of Device Templates 37
Filtering the List of Device Templates 38
Special Characters 39
Creating a Device Template 41
Defining Device Properties and Device Thresholds in the Config Tab 43
Defining Interface Monitoring in the Interface Tab 48
Defining Web-Content Monitoring in the CV Policies Tab 52
Defining TCP/IP Port Monitoring in the Port Policies Tab 55
Defining Windows Services Monitoring in the Svc Policies Tab 56
Defining Process Monitoring in the Proc Policies Tab 57
Aligning Dynamic Applications and Defining Thresholds in the Dynamic Apps Tab 58
Aligning Log File Monitoring Policies in the Logs Tab 61
Creating a New Device Template Based on an Existing Device Template 63
Editing an Existing Device Template 63
Using Device Templates 65
Before You Start 66
Using a Device Template to Edit the Configuration of the Devices in a Device Group 66
Using a Configuration Template to Edit the Configuration of One or More Individual Devices 68
Using the Bulk Configuration Tool to Apply Ad Hoc Settings to a Device Group 69
Using the Bulk Configuration Tool to Apply Ad Hoc Settings to One or More Devices 70
Example Device Group and Device Template 71
Example Device Group 71
Example Configuration Template 72
Using Device Group Maps and Views 75
Viewing the Device Maps for a Device Group 76
Viewing the Device Group Map Page for a Single Device Group 76
Viewing the Classic Views of a Device Group 76
Viewing Custom Device Maps 77
Using the Interface for Device Group Views 77
 Drag-and-Drop Editing 77
Fields and Buttons 78
Scheduling Downtime for a Device Group 79
Viewing the Schedule Manager 80
Defining a Scheduled or Recurring Device Group Maintenance Window 80
Enabling or Disabling One or More Scheduled Device Group Maintenance Windows 84
Deleting One or More Scheduled Device Group Maintenance Windows 84
Events and Device Groups 85
Searching Events by Device Group 86
Suppressing an Event for a Device Group 87
Automation Policies and Tickets 88
What is an Automation Policy? 89
Aligning an Automation Policy with a Device Group 89
What is an Action Policy? 90
Aligning a Ticket with a Device Group 91
Searching for a Ticket Aligned with a Device Group 91
Assigning Device Groups and Applying Device Templates During Discovery 92
What is Discovery? 92
Assigning Devices to a Device Group During Discovery 93
Applying a Device Template to Devices During Discovery 94
 Chapter

1
What is a Device Group?

Overview
A device group is a group of multiple devices. Device groups allow you to:

l Use device configuration templates to perform initial configuration for multiple devices simultaneously.
l Use device configuration templates to make changes to the configuration for multiple devices
simultaneously.
l In the [Views] tab, view each device group and the sub-groups and devices within each device group.
l Schedule maintenance and downtime for multiple devices simultaneously.
l Suppress events on multiple devices simultaneously.
l Include the device group in an automation policy. An automation policy allows you to trigger an automatic
action if specified criteria are met on all the devices in the device group.

A device can belong to multiple device groups. For example, suppose SL1 discovered a server. Suppose this
server hosts a corporate website that you want to monitor with a web-content policy. Suppose this server also
hosts a MySQL database that you want to monitor with a Dynamic Application for MySQL. You could make this
server a member of two device groups, one device group for web servers and another device group for MySQL
databases. You could then use a device configuration template to apply a web-content policy to all devices in the
device group for web servers and another device configuration template to apply a Dynamic Application for
MySQL to all devices in the device group for MySQL servers.

You can add devices to a device group either explicitly or dynamically.

4
 l You can create static device groups, where you explicitly assign one or more devices to a device group.
l You can create dynamic device groups, where you define rules for the device group. Each device that
meets the criteria in the rule is automatically included in the device group. For example, suppose that you
define a rule that specifies "include all devices in the System organization, with an IP address that starts with
'10.100.100' ". SL1 would automatically assign all devices from the System organization with an IP of
"10.100.100.*" to the new device group. When a new device is added to the System organization with an IP
that begins with "10.100.100.*", that device will also be included in the device group. If a device with an IP
that starts with "10.100.100.*" is removed from the System organization, that device will also be removed
from the device group.

NOTE: You can create a device group that includes both explicitly assigned devices and also includes a
dynamic rule. This device group will include both the explicitly assigned devices and all devices that
meet the criteria in the dynamic rule.

The IT Services feature in SL1 uses device groups to define an IT Service. An IT Service contains sets of rules that
define the state of that IT Service based on the state of the devices within the device group. For example, if you
created an IT Service that represents the state of your email service, the associated device group might contain
your DNS Servers, Exchange Servers, and Virtual Devices that are associated with Email Round-Trip Policies. To
learn more about IT Services, see the IT Services manual.

This manual describes how to define groups, device configuration templates, view device groups, manage device
groups, and include device groups in event suppressions and automation policies.

5
 Chapter

2
What is a Device Template?

Overview
Device templates allow you to save a device configuration, apply it to one or more devices, and reuse the same
configuration over and over again.

You can apply device templates to:

l One or more device groups.

l One or more devices, selected from the Device Manager page.

You can also apply device templates to automate the initial configuration of multiple devices. If you change a
device template, you can use it to automate the editing of the configuration of multiple devices.

Device templates are not dynamic. That is, when you update or change a device template, no changes are
made to any devices that have used the template in the past.

You can make temporary changes to a device template, apply the template to a devices, and then exit the device
template without saving the temporary changes. In this way, you can apply settings to a device group but not
permanently save the settings in the device template.

NOTE: If you make changes to a device template or simply apply the device template a second time, SL1 will
not create duplicate policies on the member devices. However, if you edit a device template and
make a change to a policy, the policy will be updated on the member devices.

The section on using device templates describes in detail all the ways you can use a device template in SL1.

6
 Chapter

3
Creating and Editing Device Groups

Overview
This chapter describes how to create and edit device groups.

Use the following menu options to navigate the SL1 user interface:

l To view a pop-out list of menu options, click the menu icon ( ).

l To view a page containing all of the menu options, click the Advanced menu icon ( ).

This chapter covers the following topics:

Before You Start 7

Viewing the List of Device Groups 8
Creating a Device Group 13
Editing an Existing Device Group 32
Controlling Access to a Device Group 33
Deleting a Device Group 34
Example of Creating a Device Group 34

Before You Start

You might want to consider the following when planning your device groups:

Before You Start 7

 l How do you configure your devices? Can you group devices by their configuration? If so, you might want to
create device groups based on their configuration and then use configuration templates to manage the
configuration for all devices in the device group.
l Remember that when you create a device group, you can control the actions that can be performed with the
device group and control access to the device group. You should plan which users need access to the
device group and what they will do with the device group.
l Device groups can be nested. Remember that child device groups are not required to inherit the same set of
actions as the parent device group. This feature allows you to fine tune actions and access for device
groups.

Viewing the List of Device Groups

From the Device Groups page, you can view the list of existing device groups and access tools to create, edit,
and manage device groups.

To view a list of existing device groups:

1. Go to the Device Groups page (Registry > Devices > Device Groups).
2. The Device Groups page displays the following about each device group:

l Plus-sign icon (+). Expands the device group and displays a list of member devices and the name,
IP address, device category, device class, device Id, and organization for each member device.
l Device Group Name. Name of the device group.
l ID. Unique, numeric ID, assigned to the device group automatically by SL1.
l Owner. User who created the device group.
l Access. Specifies whether users can view and use the device group. Shared device groups can be
viewed by other users who belong to the same organization as the creator. Private device groups can
be viewed only by the creator of the device group and administrators.
l Dev Count. Number of devices in the device group.
l Grp Count. Number of device groups included in this device group. If the number is greater than
zero, the current group is a parent group and contains sub-groups or child groups.
l Rule Count. Specifies the number of dynamic rules included in the device group.
l Edited By. User who created or last edited the device group.
l Last Edited. Date and time the device group was created or last edited.
l Tools. For each device group, one or more of the following tools are available:

o
Edit this app ( ). Leads to the Device Group Editor page, where you can edit the
parameters of the device group.

8 Viewing the List of Device Groups

 o
View IT Service( ). Leads to the IT Service Summary page, where you can view the IT
Service dashboards that have been configured for the IT Service that uses this device group.
For details on the IT Service Summary page, see the manual on IT Services.

o Bulk configuration ( ). Leads to the Apply Device Configuration Template page, where
you can make one-time changes to a configuration template and apply a configuration
template to the device group.

o Group Scheduling( ). Leads to the Device Group Scheduling page where you can
schedule downtime for maintenance for all devices in the device group.

o List devices matching dynamic rules ( ). Displays the Matched Devices modal page. This
page displays a list of all devices that match all rules in the device group.

TIP: To sort the list of device groups, click on a column heading. The list will be sorted by the column value, in
ascending order. To sort the list by descending order, click the column heading again. The Last Edited
column sorts by descending order on the first click; to sort by ascending order, click the column heading
again.

Filtering the List of Device Groups

The following describes each filter on the Device Groups page:

l Device Group Name. You can enter text to match, including special characters, and the Device Groups
page will display only device groups that have a matching name.
l ID. You can enter text to match, including special characters, and the Device Groups page will display only
device groups that have a matching ID. SL1 automatically assigns this unique, numeric ID to each device
group.
l Owner. You can enter text to match, including special characters, and the Device Groups page will
display only device groups that have the specified.
l Access. You can enter text to match, including special characters, and the Device Groups page will display
only device groups that have a matching access (Shared or Private).
l Dev Count. You can enter text to match, including special characters, and the Device Groups page will
display only device groups that have a number or devices.
l Grp Count. You can enter text to match, including special characters, and the Device Groups page will
display only device groups that have a matching number of child device groups.
l Rule Count. You can enter text to match, including special characters, and the Device Groups page will
display only device groups that have a matching number of dynamic rules.
l Edited By. You can enter text to match, including special characters, and the Device Groups page will
display only device groups that have a matching user name in the Edited By field.
l Last Edited. Only those device groups that have the specified creation date or last-edited date will be
displayed. The choices are:

Viewing the List of Device Groups 9

 l All. Display all device groups that match the other filters.
l Last Minute. Display only device groups that have been created within the last minute.
l Last Hour. Display only device groups that have been created within the last hour.
l Last Day. Display only device groups that have been created within the last day.
l Last Week. Display only device groups that have been created within the last week.
l Last Month. Display only device groups that have been created within the last month.
l Last Year. Display only device groups that have been created within the last year.

Special Characters
You can include the following special characters to filter by each column except those that display date and time:

NOTE: When searching for a string, SL1 will match substrings by default, even if you do not include any
special characters. For example, searching for "hel" will match both "hello" and "helicopter". When
searching for a numeric value, SL1 will not match a substring unless you use a special character.

String and Numeric

l , (comma). Specifies an "OR" operation. Works for string and numeric values. For example:

"dell, micro" matches all values that contain the string "dell" OR the string "micro".

l & (ampersand). Specifies an "AND " operation. Works for string and numeric values. For example:

"dell & micro" matches all values that contain both the string "dell" AND the string "micro", in any order.

l ! (exclamation point). Specifies a "not" operation. Works for string and numeric values. For example:

NOTE: You can also use the "!" character in combination with the arithmetical special characters (min-max,
>, <, >=, <=, =) described below.

l * (asterisk). Specifies a "match zero or more" operation. Works for string and numeric values. For a string,
matches any string that matches the text before and after the asterisk. For a number, matches any number
that contains the text. For example:

"hel*er" would match "helpers" and "helicopter" but not "hello".

"325*" would match "325", "32561", and "325000".

"*000" would match "1000", "25000", and "10500000".

10 Viewing the List of Device Groups

 l ? (question mark). Specifies "match any one character". Works for string and numeric values. For example:

"l?ver" would match the strings "oliver", "levers", and "lover", but not "believer".

"135?" would match the numbers "1350", "1354", and "1359", but not "135" or "13502"

String

l ^ (caret). For strings only. Specifies "match the beginning". Matches any string that begins with the specified
string. For example:

"^sci" would match "scientific" and "sciencelogic", but not "conscious".

"^happy$" would match only the string "happy", with no characters before or after.

"!^micro" would match all values that do not start with "micro".

"!^$" would match all values that are not null.

"!^" would match null values.

l $ (dollar sign). For strings only. Specifies "match the ending". Matches any string that ends with the specified
string. For example:

"ter$" would match the string "renter" but not the string "terrific".

"^happy$" would match only the string "happy", with no characters before or after.

"!fer$" would match all values that do not end with "fer".

"!^$" would match all values that are not null.

"!$" would match null values.

NOTE: You can use both ^ and $ if you want to match an entire string and only that string. For example,
"^tern$" would match the strings "tern" or "Tern" or "TERN"; it would not match the strings "terne" or
"cistern".

Numeric

l min-max. Matches numeric values only. Specifies any value between the minimum value and the maximum
value, including the minimum and the maximum. For example:

"1-5 "would match 1, 2, 3, 4, and 5.

l - (dash). Matches numeric values only. A "half open" range. Specifies values including the minimum and
greater or including the maximum and lesser. For example:

"1-" matches 1 and greater. So would match 1, 2, 6, 345, etc.

"-5" matches 5 and less. So would match 5, 3, 1, 0, etc.

Viewing the List of Device Groups 11

 l > (greater than). Matches numeric values only. Specifies any value "greater than". For example:

">7" would match all values greater than 7.

l < (less than). Matches numeric values only. Specifies any value "less than". For example:

"<12" would match all values less than 12.

l >= (greater than or equal to). Matches numeric values only. Specifies any value "greater than or equal to".
For example:

"=>7" would match all values 7 and greater.

l <= (less than or equal to). Matches numeric values only. Specifies any value "less than or equal to". For
example:

"=<12" would match all values 12 and less.

l = (equal). Matches numeric values only. For numeric values, allows you to match a negative value. For
example:

"=-5 " would match "-5" instead of being evaluated as the "half open range" as described above.

Examples

l "!dell" matches all values that do not contain the string "dell".
l "!^micro" would match all values that do not start with "micro".
l "!fer$" would match all values that do not end with "fer".
l "!^$" would match all values that are not null.
l "!^" would match null values.
l "!$" would match null values.
l "!*" would match null values.
l "happy, !dell" would match values that contain "happy" OR values that do not contain "dell".
l "aio$". Matches only text that ends with "aio".
l "^shu". Matches only text that begins with "shu".
l "^silo$". Matches only the text "silo", with no characters before or after.
l "!silo". Matches only text that does not contains the characters "silo".
l "!^silo". Matches only text that does not start with "silo".
l "!0$". Matches only text that does not end with "0".
l "!^silo$". Matches only text that is not the exact text "silo", with no characters before or after.
l "!^". Matches null values, typically represented as "--" in most pages.
l "!$". Matches null values, typically represented as "--" in most pages.
l "!^$". Matches all text that is not null.

12 Viewing the List of Device Groups

 l silo, !aggr". Matches text that contains the characters "silo" and also text that does not contain "aggr".
l "silo, 02, !aggr". Matches text that contains "silo" and also text that contains "02" and also text that does not
contain "aggr".
l "silo, 02, !aggr, !01". Matches text that contains "silo" and also text that contains "02" and also text that does
not contain "aggr" and also text that does not contain "01".
l "^s*i*l*o$". Matches text that contains the letter "s", "i", "l", "o", in that order. Other letters might lie between
these letters. For example "sXiXlXo" would match.
l "!^s*i*l*o$". Matches all text that does not that contains the letter "s", "i", "l", "o", in that order. Other letters
might lie between these letters. For example "sXiXlXo" would not match.
l "!vol&!silo". Matches text that does not contain "vol" AND also does not contain "silo". For example, "volume"
would match, because it contains "vol" but not "silo".
l "!vol&02". Matches text that does not contain "vol" AND also contains "02". For example, "happy02" would
match, because it does not contain "vol' and it does contain "02".
l "aggr,!vol&02". Matches text that contains "aggr" OR text that does not contain "vol" AND also contains
"02".
l "aggr,!vol&!infra". Matches text that contains "aggr" OR text that does not contain "vol" AND does not
contain "infra".
l "*". Matches all text.
l "!*". Matches null values, typically represented as "--" in most pages.
l "silo". Matches text that contains "silo".
l " !silo ". Matches text that does not contain "silo".
l " !^silo$ ". Matches all text except the text "silo", with no characters before or after.
l "-3,7-8,11,24,50-". Matches numbers 1, 2, 3, 7, 8, 11, 24, 50, and all numbers greater than 50.
l "-3,7-8,11,24,50-,a". Matches numbers 1, 2, 3, 7, 8, 11, 24, 50, and all numbers greater than 50, and
text that includes "a".
l "?n". Matches text that contains any single character and the character "n". For example, this string would
match "an", "bn", "cn", "1n", and "2n".
l "n*SAN". Matches text the contains "n", zero or any number of any characters and then "SAN". For example,
the string would match "nSAN", and "nhamburgerSAN".
l "^?n*SAN$”. Matches text that begins with any single character, is following by "n", and then zero or any
number of any characters, and ends in "SAN".

Creating a Device Group

To define a new device group, perform the following steps:

1. Go to the Device Groups page (Registry > Devices > Device Groups).
2. In the Device Groups page, click the [Create] button.
3. The Device Group Editor page appears.

Creating a Device Group 13

 4. In the Device Group Editor page, supply values in each field and select devices to include in the device
group. You can also select other device groups to include in the new device group. The selected device
groups will be children device groups to the new device group.

l Device Group Name. Specify the name of the new device group.
l Icon. Select an icon to represent the new device group. To add an icon to this list, go to the Device
Icon Browser modal page (System > Customize > Device Classes, click the [Icon] button) and then
select the [Import] button.
l Force Child Visibility. If the current device group includes another device group, that nested device
group is considered a "child" device group. A device group can contain multiple children device
groups. Those children device groups can also contain nested device groups. The Force Child
Visibility feature specifies whether or not all nested device groups will inherit the Visibility settings of
the parent device group. This field affects all Visibility settings except Maps/Views and Discovery.
Choices are:

o No. Child device groups will not inherit the Visibility settings of the parent device group. When
SL1 performs actions on the parent device group, devices in the child device groups will be acted
upon only if the child device groups have the appropriate Visibility setting.
For example, suppose a device group parent_groupA includes a nested device group called
child_groupB and another nested device group called child_groupC.

Suppose parent_groupA has Force Child Visibility set to No.

Suppose parent_groupA has Visibility set to Notification/Automation.

Suppose parent_groupA is aligned with an Automation Policy.

All the devices in parent_groupA can be acted upon by that Automation Policy.

Suppose child_groupB has Visibility set to Views/Maps only.

The devices in child_groupB will not be acted upon by the Automation Policy, because child_
groupB does not have the required Visibility setting and because child_groupB does not inherit
the Visibility settings of parent_groupA.

Suppose child_groupC has Visibility set to Notification/Automation.

All the devices in child_groupC will be acted upon by the Automation Policy, because child_
groupC has the required Visibility setting.

The value in Force Child Visibility for parent_groupA is recursive and affects all child,
grandchild, great grandchild etc. device groups nested under the parent group

o Yes. Child device groups will inherit the Visibility settings of the parent device group, regardless of
the Visibility settings for the child device group. When SL1 performs actions on the parent device
groups, all devices in each child device group will also be acted upon, regardless of the Visibility
settings for each child device group.

14 Creating a Device Group

 For example, suppose a device group parent_groupX includes a nested device group. called
child_groupY.

Suppose parent_groupX has Force Child Visibility set to Yes.

Suppose parent_groupX has Visibility set to Device Schedules.

Suppose you define a maintenance schedule for parent_groupX that says "stop collection for
parent_groupX on October 17, from 3:00 AM until 3:30 AM.

On October 17, from 3:00 AM until 3:30 AM, all the devices in parent_groupX will have a
Collection State of "Maintenance".

Suppose child_groupY has Visibility set to Maps/Views only.

On October 17, from 3:00 AM until 3:30 AM, all the devices in child_groupY will have a
collection status of "Maintenance", even though child_groupY does not have Visibility set to
Device Schedule. This is because child_groupY inherited the Visibility of parent_groupX.
However, because child_group_Y does not have Visibility set to Device Schedule, a user
cannot explicitly schedule maintenance for child_group_Y.

Suppose child_groupY includes a nested device group, called grandchild_groupZ. Suppose

grandchild_groupZ has Visibility set to Discovery only.

On October 17, from 3:00 AM until 3:30 AM, all the devices in grandchild_groupZ will have a
collection status of "Maintenance", even though grandchild_groupZ does not have Visibility set
to Device Schedule. This is because grandchild_groupZ inherited the Visibility of parent_
groupX. However, because grandchild_group_Z does not have Visibility set to Device
Schedule, a user cannot explicitly schedule maintenance for grandchild_group_Z.

The value in Force Child Visibility for parent_groupX is recursive and affects all child,
grandchild, great grandchild etc. device groups nested under the parent group . However,
inherited Visibility settings only apply to child, grandchild, great grandchild and so forth device
groups if the action controlled by the Visibility setting is performed on the parent device group.

NOTE: The Force Child Visibility feature affects only actions that expand a device group into a list of
devices. The Force Child Visibility feature does not affect the Visibility settings for Maps/Views and
Discovery. Children device groups cannot inherit the Visibility settings for Maps/Views and
Discovery, even if Force Child Visibility is set to Yes. If you want a parent device group to appear in
the Views pages, set Visibility to Maps/Views. If you want children device groups to appear in the
Views pages, you must explicitly set Visibility to Maps/Views for each child device group. If you want
a parent device group to appear in the list of device groups in the Discovery Control Panel page
(System > Manage > Classic Discovery), set Visibility to Discovery. If you want children device
groups to appear in the list of device groups in the Discovery Control Panel page (System >
Manage > Classic Discovery), you must explicitly set Visibility to Discovery for each child device
group.

Creating a Device Group 15

 l Visibility. Specifies where in SL1 the device group will be visible. Choices are:

o Maps/Views. If selected, the device group will appear in the Device Group Map page (Classic
Maps > Device Maps > Device Groups), the Custom Device Group Map page (Classic Maps
> My Customized Maps), and the Device Group Views page (Classic Maps > Classic Views
> Device Groups).
o Config Policies/Bulk Edit. If selected, the building blocks icon ( ) is visible in the Device Groups
page. This allows you to configure all the devices in the device group using a device template.
o Notification/Automation. If selected, the device group will appear in the list of device groups in the
Automation Policy Editor modal page (Registry > Run Book > Automation > Edit/Create). This
page allows you to trigger an automatic action if specified criteria are met on all the devices in the
device group.
o Discovery. If selected, the device group appears in the field Auto-add Devices to Device Group
in the Discovery Control Panel page (System > Manage > Classic Discovery). This allows you
to automatically add newly discovered devices to a pre-existing device group during the discovery
process.

o Device Schedules. If selected, the calendar icon ( ) is visible in the Device Groups page. This
allows you to schedule downtime for all the devices in the device group. The scheduled downtime
will appear in the Maintenance Schedule page for each device in the device group.
o Event Suppression. If selected, the device group will appear in the [Suppressions] tab in the
Event Policy Editor page (Registry > Events > Event Manager > create or edit). In this page, you
can suppress the event for all devices in the device group.
o IT Services. This is a view-only option. If this option is selected when the Device Group Editor is
loaded, the device group is associated with an IT service and was created automatically by SL1.
Do not select or deselect this option.
l Sharing Permissions. Specifies whether other users can view and use the device group, in both the
Device Groups page and in the pages in SL1 where the device group is visible. Choices are:

o Shared with users in your organization. The device group can be viewed and used by other users
who belong to the same organization as the creator.
o Private (visible only to you). The device group can be viewed and used only by the creator of the
device group and administrators.

l Permission Keys. If you selected Shared with users in your organization in the Sharing Permissions
field, you can specify the Access Keys that a user of type "user" must have to view the device group.
The Permission Keys field will display a list of all the Access Keys in the EM7 System Administration
category and all the Access Keys in the Device Group category.

o If you select one or more Access Keys in the Permissions Keys field, each user must meet the
following criteria to access the device group:

16 Creating a Device Group

 n The user must have at least one of the selected Access Keys to access the device group.
n The user must be granted one or more Access Keys that contains the Access Hooks "Registry"
and "Registry > Devices > Device Groups"
n The user and creator of the device group must be members of a common organization.

NOTE: For both the user and the creator of the device group, the common organization can be either the
primary organization or an additional organization membership. For example, the user could have a
primary organization of "East Coast NOC" and an additional organization membership in the
organization "Headquarters". The creator of the device group could have a primary organization of
"West Coast NOC" and an additional organization membership in the organization "Headquarters".
In this situation, the user and creator of the device group are both members of a common
organization.

o If you do not select one or more Access Keys in the Permissions Keys field, any user meeting the
following two requirements can access the device group:

n The user must be granted one or more Access Keys that contains the Access Hooks "Registry"
and "Registry > Devices > Groups".
n The user and creator of the device group must be members of a common organization.

NOTE: Users of type "administrator" will be able to view and access all device groups, regardless of the
settings in the Shared field and the Permission Keys field.

5. Optionally, add static devices and child device groups to the new device group.
6. Optionally, add dynamic rules to the new device group.
7. Click the [Save] button in the Device Group Editor page to save the device group. The new device group
will appear in the Device Group page. You can now perform actions upon all the devices in the device
group simultaneously.

Adding and Removing Static Devices and Child Device Groups

You can explicitly assign one or more devices or child device-groups to a device group. These devices and device
groups are considered static because they will remain in the device group until you manually remove them.

To manually add a device to a device group:

1. Open a device group from the Device Groups page (Registry > Devices > Device Groups) and go to the
Static Devices and Groups pane.
2. Click the [Add] button then select Add Devices.
3. The Device Alignment modal appears and displays a list of all devices in SL1.

Creating a Device Group 17

 4. In the Device Alignment modal, select the checkbox of each device you want to include in the device
group. Click the [Add/Remove] button in the lower right.
5. The selected devices will appear in the Static Devices and Groups pane.

To remove one or more static devices from the device group:

1. Open a device group from the Device Groups page (Registry > Devices > Device Groups) and go to the
Static Devices and Groups pane.
2. Select the checkbox for each device you want to remove.
3. Click the [Del] button (in the upper right).
4. The selected device(s) no longer appear in the Static Devices and Groups pane.

NOTE: If you remove a static device from a device group while the device is in maintenance mode, the
device will stay in maintenance mode until you disable it. You must disable the maintenance
schedule on the device itself in the Device Manager (Registry > Devices > Device Manager by
clicking on its calendar ( ) icon. For more information, see the chapter on "Device Maintenance" in
the Device Management manual.

To manually add a child device-group to a device group:

1. Open a device group from the Device Groups page (Registry > Devices > Device Groups) and go to the
Static Devices and Groups pane.
2. Click the [Add] button then select Add Groups.
3. The Device Group Alignment modal page appears and displays a list of all device groups in SL1.
4. In the Device Group Alignment modal page, select the checkbox of each device group you want to
include in the device group. Click the [Add/Remove] button in the lower right.
5. The selected device groups will appear in the Static Devices and Groups pane.

To remove one or more static device-groups from the device group:

1. Open a device group from the Device Groups page (Registry > Devices > Device Groups) and go to the
Static Devices and Groups pane.
2. Select the checkbox for each child device-group you want to remove.
3. Click the [Del] button (in the upper right).
4. The selected device group(s) no longer appear in the Static Devices and Groups pane.

Adding Dynamic Rules

You can create dynamic rules for the device group. Each device that meets the criteria in the rule is
automatically included in the device group.

18 Creating a Device Group

 For example, suppose that you define a rule that specifies "include all devices in the System organization, with an
IP address that starts with '10.100.100'. SL1 would automatically assign all devices from the System organization
with an IP of "10.100.100.*" to the new device group. When a new device is added to the System organization
with an IP that begins with "10.100.100.*", that device will also be included in the device group. If a device with
an IP that starts with "10.100.100.*" is removed from the System organization, that device will also be removed
from the device group.

NOTE: Starting with version 11.1.0, SL1 reduced the amount of time it took to evaluate dynamic device
group rules, which in previous versions of SL1 caused SL1 to refresh the membership of the device
group too slowly, resulting in events not being suppressed for devices in the device group.

To add a dynamic rule:

1. Open a device group from the Device Groups page (Registry > Devices > Device Groups) and go to the
Dynamic Rules pane.
2. Click the [Add] button (in the upper right of the pane). The Device Group Rule Editor modal page
appears.
3. You can select one or more Active Selectors. To be included in the device group, a device must match all
the Selector Definitions.
4. Depending upon your selection, you can enter the following options in the Selector Definitions pane.
l Organization. Displays a list of all organizations in SL1.

o To filter the list, you can enter a string in the field under the title.
o If you select one or more organizations, SL1 will search for devices that are members of at least
one the selected organization(s) and include those devices in the device group. For example, if
you select two organizations, all devices from each organization will be included in the device
group.
o If you select the Invert checkbox, SL1 will search for devices that are not members of the selected
organization(s) and include those devices in the device group.

l Device Class. Displays a list of all device classes in SL1.

o To filter the list, you can enter a string in the field under the title.
o If you select one or more device classes, SL1 will search for devices that are members of the
selected device class(es) and include those devices in the device group. For example, if you select
two device classes, all devices from each device class will be included in the device group.
o If you select the Invert checkbox, SL1 will search for devices that are not members of the selected
device class(es) and include those devices in the device group.

l Device Category. Displays a list of all device categories in SL1.

Creating a Device Group 19

 o To filter the list, you can enter a string in the field under the title.
o If you select one or more device categories, SL1 will search for devices that are members of the
selected device categories and include those devices in the device group. For example, if you
select two device categories, all devices from each device category will be included in the device
group.
o If you select the Invert checkbox, SL1 will search for devices that are not members of the selected
device categories and include those devices in the device group.

l Device Name. Displays a field in which you can enter a string. SL1 will use the string to search for
devices with matching device names. If you do not use wildcard characters, SL1 will return only
devices with a device name that exactly matches the string. You can use the following syntax in the
field:

o term*. SL1 searches for any device name that begins with "term".
o *term. SL1 searches for any device name that ends with "term".
o te?m. SL1 searches for any device name that contains the text "te[any single character]m".
o !term. SL1 searches for any device name that does not include the text "term".
o term1, term2. SL1 searches for any device name that contains either "term1" or "term2".

l Device IP. Displays a field in which you can enter a string. SL1 will use the string to search for devices
with matching IP addresses. If you do not use wildcard characters, SL1 will return only devices with a
device IP that exactly matches the string. You can use the following syntax in the field:

o term*. SL1 searches for any device IP that begins with "term".
o *term. SL1 searches for any device IP that ends with "term".
o te?m. SL1 searches for any device IP that contains the text "te[any single character]m".
o !term. SL1 searches for any device IP that does not include the text "term".
o term1, term2. SL1 searches for any device IP that contains either "term1" or "term2".
o If you select the Invert checkbox, SL1 will search for devices that do not have a matching IP
address and include those devices in the device group.

l Device State. Displays a list of all device states in SL1 (Notice, Healthy, Minor, Major, Critical). Each
device's state is the same as the highest severity event associated with the device..

o To filter the list, you can enter a string in the field under the title.
o If you select one or more device states, SL1 will search for devices that are members of the
selected device states and include those devices in the device group. For example, if you select
two device states, all devices from each device state will be included in the device group.
o If you select the Invert checkbox, SL1 will search for devices that do not have the selected device
state and include those devices in the device group.

20 Creating a Device Group

 l Collection State. Displays a list of all collection states in SL1 (Active, NOT Active, User-Disabled,
NOT User-Disabled, Unavailable, NOT Unavailable, Maintenance, NOT Maintenance, System-
Disabled, NOT System-Disabled)..

o To filter the list, you can enter a string in the field under the title.
o If you select one or more collection states, SL1 will search for devices that are members of the
selected device states and include those devices in the device group. For example, if you select
two collection states, all devices with the first collection state and all devices with the second
collection state will be included in the device group.

l Collector Group. Displays a list of all Collector Groups in SL1.

o To filter the list, you can enter a string in the field under the title.
o If you select one or more Collector Groups, SL1 will search for devices that are members of the
selected Collector Groups and include those devices in the device group. For example, if you
select two Collector Groups, all devices from each Collector Group will be included in the device
group.
o If you select the Invert checkbox, SL1 will search for devices that are not members of the select
Collector Group(s) and include those devices in the device group.

l Open TCP Ports. Displays a list of all open TCP ports that SL1 has discovered on at least one device.

o To filter the list, you can enter a string in the field under the title.
o If you select one or more ports, SL1 will search for devices have that have those ports open and
include those devices in the device group. For example, if you select two collection ports, all
devices where the first port is open and all devices where the second port is open will be included
in the device group.
o If you select the Invert checkbox, SL1 will search for devices that do not have the selected port(s)
open and include those devices in the device group.

l Running Process. Displays a field in which you can enter a string. SL1 will use the string to search for
devices that are running a matching system process. If you do not use wildcard characters, SL1 will
return only devices running a process that exactly matches the string. You can use the following
syntax in the field:

o term*. SL1 searches for any process name that begins with "term".
o *term. SL1 searches for any process name that ends with "term".
o te?m. SL1 searches for any process name that contains the text "te[any single character]m".
o !term. SL1 searches for any process name that does not include the text "term".
o term1, term2. SL1 searches for any process name that contains either "term1" or "term2".
o If you select the Invert checkbox, SL1 will search for devices that are not running the selected
processes open and include those devices in the device group.

Creating a Device Group 21

 l Windows Service. Displays a field in which you can enter a string. SL1 will use the string to search for
devices that are running a matching Windows service. If you do not use wildcard characters, SL1 will
return only devices running a Windows services that exactly matches the string. You can use the
following syntax in the field:

o term*. SL1 searches for any Windows Service name that begins with "term".
o *term. SL1 searches for any Windows Service name that ends with "term".
o te?m. SL1 searches for any Windows Service name that contains the text "te[any single
character]m".
o !term. SL1 searches for any Windows Service name that does not include the text "term".
o term1, term2. SL1 searches for any Windows Service name that contains either "term1" or "term2".
o If you select the Invert checkbox, SL1 will search for devices that are not running a matching
Windows service and include those devices in the device group.

l Subscribed Product. Displays a list of all product SKUs in SL1.

o To filter the list, you can enter a string in the field under the title.
o If you select one or more SKUs, SL1 will search for devices that subscribe to at least one the
selected SKU(s) and include those devices in the device group. For example, if you select two
SKUs, all devices that subscribe to one of the two SKUs will be included in the device group.
o If you select the Invert checkbox, SL1 will search for devices that do not subscribe to the selected
SKU(s) and include those devices in the device group.

l Active Event. Displays a list of all active events in SL1.

o To filter the list, you can enter a string in the field under the title.
o If you select one or more active events, SL1 will search for devices for which that event is currently
active and include those devices in the device group. For example, if you select two events, all
devices for which one of the two events is active will be included in the device group.
o If you select the Invert checkbox, SL1 will search for devices for which the event is not currently
active and include those devices in the device group.

22 Creating a Device Group

 l Aligned Dynamic App. Displays a list of all Dynamic Applications that are currently aligned with one
or more devices.

o To filter the list, you can enter a string in the field under the title.
o If you select one or more aligned Dynamic Applications, SL1 will search for devices that are
aligned with those Dynamic Applications and include those devices in the device group. For
example, if you select two Dynamic Applications, all devices that are aligned with each of the
Dynamic Applications will be included in the device group.
o If you select the Invert checkbox, SL1 will search for devices that are not aligned with the selected
Dynamic Application(s).

l Asset Make. Displays a field in which you can enter a string. SL1 will use the string to search for
devices that have a matching value in the Make field in their asset records (SL1 automatically creates
an asset record for each device during nightly auto-discovery). If you do not use wildcard characters,
SL1 will return only devices that have a Make field that exactly matches the string. You can use the
following syntax in the field:

o term*. SL1 searches for any asset make that begins with "term".
o *term. SL1 searches for any asset make that ends with "term".
o te?m. SL1 searches for any asset make that contains the text "te[any single character]m".
o !term. SL1 searches for any asset make that does not include the text "term".
o term1, term2. SL1 searches for any asset make that contains either "term1" or "term2".

l Asset Model. Displays a field in which you can enter a string. SL1 will use the string to search for
devices that have a matching value in the Model field in their asset records (SL1 automatically
creates an asset record for each device during nightly auto-discovery). If you do not use wildcard
characters, SL1 will return only devices that have a Model field that exactly matches the string. You
can use the following syntax in the field:

o term*. SL1 searches for any asset model that begins with "term".
o *term. SL1 searches for any asset model that ends with "term".
o te?m. SL1 searches for any asset model that contains the text "te[any single character]m".
o !term. SL1 searches for any asset model that does not include the text "term".
o term1, term2. SL1 searches for any asset model that contains either "term1" or "term2".

Creating a Device Group 23

 l Asset Function. Displays a field in which you can enter a string. SL1 will use the string to search for
devices that have a matching value in the Function field in their asset records (SL1 automatically
creates an asset record for each device during nightly auto-discovery). If you do not use wildcard
characters, SL1 will return only devices that have a Function field that exactly matches the string. You
can use the following syntax in the field:

o term*. SL1 searches for any asset function that begins with "term".
o *term. SL1 searches for any asset function that ends with "term".
o te?m. SL1 searches for any asset function that contains the text "te[any single character]m".
o !term. SL1 searches for any asset function that does not include the text "term".
o term1, term2. SL1 searches for any asset function that contains either "term1" or "term2".

l Asset Owner. Displays a field in which you can enter a string. SL1 will use the string to search for
devices that have a matching value in the Management Type field in their asset records (SL1
automatically creates an asset record for each device during nightly auto-discovery). If you do not
use wildcard characters, SL1 will return only devices that have a Management Type field that exactly
matches the string. You can use the following syntax in the field:

o term*. SL1 searches for any asset owner that begins with "term".
o *term. SL1 searches for any asset owner that ends with "term".
o te?m. SL1 searches for any asset owner that contains the text "te[any single character]m".
o !term. SL1 searches for any asset owner that does not include the text "term".
o term1, term2. SL1 searches for any asset owner that contains either "term1" or "term2".

l Asset Location. Displays a field in which you can enter a string. SL1 will use the string to search for
devices that have a matching value in the Facility/Data Center field in their asset records (SL1
automatically creates an asset record for each device during nightly auto-discovery). If you do not
use wildcard characters, SL1 will return only devices that have a Facility/Data Center field that
exactly matches the string. You can use the following syntax in the field:

o term*. SL1 searches for any asset location that begins with "term".
o *term. SL1 searches for any asset location that ends with "term".
o te?m. SL1 searches for any asset location that contains the text "te[any single character]m".
o !term. SL1 searches for any asset location that does not include the text "term".
o term1, term2. SL1 searches for any asset location that contains either "term1" or "term2".

24 Creating a Device Group

 l Asset Serial. Displays a field in which you can enter a string. SL1 will use the string to search for
devices that have a matching value in the Serial field in their asset records (SL1 automatically creates
an asset record for each device during nightly auto-discovery). If you do not use wildcard characters,
SL1 will return only devices that have a Serial field that exactly matches the string. You can use the
following syntax in the field:

o term*. SL1 searches for any asset serial that begins with "term".
o *term. SL1 searches for any asset serial that ends with "term".
o te?m. SL1 searches for any asset serial that contains the text "te[any single character]m".
o !term. SL1 searches for any asset serial that does not include the text "term".
o term1, term2. SL1 searches for any asset serial that contains either "term1" or "term2".

l Asset Tag. Displays a field in which you can enter a string. SL1 will use the string to search for devices
that have a matching value in the Asset Tag field in their asset records (SL1 automatically creates an
asset record for each device during nightly auto-discovery). If you do not use wildcard characters,
SL1 will return only devices that have an Asset Tag field that exactly matches the string. You can use
the following syntax in the field:

o term*. SL1 searches for any asset tag that begins with "term".
o *term. SL1 searches for any asset tag that ends with "term".
o te?m. SL1 searches for any asset tag that contains the text "te[any single character]m".
o !term. SL1 searches for any asset tag that does not include the text "term".
o term1, term2. SL1 searches for any asset tag that contains either "term1" or "term2".

l Asset Software Title. Displays a field in which you can enter a string. SL1 will use the string to search
for devices that have a matching Software Title field in their asset records (SL1 automatically creates
an asset record for each device during nightly auto-discovery). If you do not use wildcard characters,
SL1 will return only devices that have a Software Title field that exactly matches the string. You can
use the following syntax in the field:

o term*. SL1 searches for any software title that begins with "term".
o *term. SL1 searches for any software title that ends with "term".
o te?m. SL1 searches for any software title that contains the text "te[any single character]m".
o !term. SL1 searches for any software title that does not include the text "term".
o term1, term2. SL1 searches for any software title that contains either "term1" or "term2".

Creating a Device Group 25

 l Asset Software Version. Displays a field in which you can enter a string. SL1 will use the string to
search for devices that have a matching Software Version field in their asset records (SL1
automatically creates an asset record for each device during nightly auto-discovery). If you do not
use wildcard characters, SL1 will return only devices that have a Software Version field that exactly
matches the string. You can use the following syntax in the field:

o term*. SL1 searches for any software version that begins with "term".
o *term. SL1 searches for any software version that ends with "term".
o te?m. SL1 searches for any software version that contains the text "te[any single character]m".
o !term. SL1 searches for any software version that does not include the text "term".
o term1, term2. SL1 searches for any software version that contains either "term1" or "term2".

Asset Model Number. Displays a field in which you can enter a string. SL1 will use the string to
search for devices that have a matching Model Number field in their asset records (SL1
automatically creates an asset record for each device during nightly auto-discovery). If you do not
use wildcard characters, SL1 will return only devices that have a Model Number field that exactly
matches the string. You can use the following syntax in the field:

o term*. SL1 searches for any software version that begins with "term".
o *term. SL1 searches for any software version that ends with "term".
o te?m. SL1 searches for any software version that contains the text "te[any single character]m".
o !term. SL1 searches for any software version that does not include the text "term".
o term1, term2. SL1 searches for any software version that contains either "term1" or "term2".

l Software Title. Displays a field in which you can enter a string. SL1 will use the string to search for
devices that have a matching title and version in the list of software defined in the Licenses tab in the
asset record for the device. If you do not use wildcard characters, SL1 will return only devices that
have a Software Title field that exactly matches the string. You can use the following syntax in the
field:

o term*. SL1 searches for any software title and/or version that begins with "term".
o *term. SL1 searches for any software title and/or version that ends with "term".
o te?m. SL1 searches for any software title and/or version that contains the text "te[any single
character]m".
o !term. SL1 searches for any software title and/or version that does not include the text "term".
o term1, term2. SL1 searches for any software title and/or version that contains either "term1" or
"term2".
o If you select the Invert checkbox, SL1 will search for devices that do not have a matching software
title or version in the list of software and include those devices in the device group.

26 Creating a Device Group

 l Custom Attribute. The Active Selectors field includes an entry for each custom attribute defined in
your SL1 system. When you select a custom attribute, the Selector Definitions pane displays a field in
which you can enter a string. SL1 will use the string to search for devices that have a matching value
for this custom attribute. If you do not use wildcard characters, SL1 will return only devices with a
custom attribute that exactly matches the string. You can use the following syntax in the field:

o term*. SL1 searches for any attribute value that begins with "term".
o *term. SL1 searches for any attribute value that ends with "term".
o te?m. SL1 searches for any attribute value that contains the text "te[any single character]m".
o !term. SL1 searches for any attribute value that does not include the text "term".
o term1, term2. SL1 searches for any attribute value that contains either "term1" or "term2".

NOTE: If you input !* in to the Dynamic Rule Operator Selector Definition field, your search returns all
devices that have an empty value for that attribute.

5. After you have selected an Active Selector and the Selector Definitions, you can specify that you want to
include children devices, all descendent devices, parent devices, or all ancestor devices. To do this
do not click the [OK] button. Instead, click the Select related devices link next to the [OK] button. If you
do not want to include related devices, click the [OK] button to add the new rule.
6. If you clicked the Select related devices link, the Relationship Selection modal page appears. In this
modal page, you can select devices by relationship. The Matched Devices pane displays all the devices
that match all the criteria in the rule. The list of devices changes as you add and remove criteria.
7. Click the [OK] button to add the new rule.

NOTE: If a single dynamic rule includes multiple criteria, a device must match all the criteria to be included
in the device group (like the SQL AND operator). If a single device group includes multiple dynamic
rules, a device must match only a single rule to be included in the device group (like the SQL OR
operator). To view a list of devices that are currently included in the device group based on the
dynamic rules defined in the device group, click the [Matched] button.

The Relationship Selection Page

If you click the Select related device link in the Device Group Rule Editor page, the Relationship Selection
page appears.

The Relationship Selection page includes the following panes:

Creating a Device Group 27

 l Relationship Selector. You can choose to include child devices, all descendent devices (children,
grandchildren, great grandchildren, etc.), parent devices, or all ancestor devices (parents, grandparents,
great grandparents, etc.). You can also choose to further filter by including only the children, descendents,
parents, and ancestors devices that are related to the "Seed Devices" through one or more selected Dynamic
Applications.

NOTE: For details on building relationships with Dynamic Applications, see the Dynamic Application
Development manual.

l Seed Devices. This is the list of devices you defined in the Device Group Rule Editor page. You can
include these devices in the device group or include only the children, descendants, parents, ancestors.
l Matched Devices. This is the list of devices that will be included in the device group when you click the
[OK] button.

NOTE: As SL1 discovers devices and component devices that meet the criteria for the dynamic device group,
SL1 will automatically add those devices and component devices to the device group.

Relationship Selectors

In this pane, you can specify devices to include in the device group based on their relationships to the Seed
Devices:

l Children of. If you select this checkbox, all child devices of the Seed Devices are included in the device
group.
l Descendents of. This checkbox is enabled only if you select the Children of checkbox. If you select this
checkbox, all child devices, grandchildren devices, great grandchildren devices, etc of the Seed Devices are
included in the device group.
l Parents of. If you select this checkbox, all parent devices of the Seed Devices are included in the device
group.
l Ancestors of. This checkbox is enabled only if you select the Parents of checkbox. If you select this
checkbox, all parent devices, grandparent devices, great grandparent devices, etc of the Seed Devices are
included in the device group.

l Related by. This checkbox is enabled only if you select the Children of checkbox or the Parents of
checkbox. You can further filter the devices in the device group by including only the children, descendents,
parents, and ancestors devices that are related to the Seed Devices through one or more selected Dynamic
Applications. If you select this checkbox, you can select one or more Dynamic Applications from the list of
Dynamic Applications that can create relationships. Only those devices that meet all the criteria will be
included in the device group.

l Include seed devices. This checkbox is enabled only if you select the Children of checkbox or the Parents
of checkbox. If you select this checkbox, the related Seed Devices are included in the device group. Seed
Devices with no relationships are not included in the group.

28 Creating a Device Group

 Seed Devices

This is the list of devices you defined in the Device Group Rule Editor page. You can include these devices in
the device group or include only the children, descendants, parents, and ancestors of these devices.

For each Seed Device, the Relationship Selection page displays.

TIP: To sort the list of devices, click on a column heading. The list will be sorted by the column value, in
ascending order. To sort by descending order, click the column heading again.

l Device Name. Name of the device. For devices running SNMP or with DNS entries, the name is discovered
automatically. For devices without SNMP or DNS entries, the device's IP address will appear in this field.
l Category. The ScienceLogic category assigned to the device. Categories include servers, routers, switches,
firewalls, printers, etc. The category is automatically assigned during discovery, at the same time as the
Device-Class/Sub-Class.
l Class / Sub-class. The manufacturer (device class) and type of device (sub-class). The Device-Class/Sub-
Class is automatically assigned during discovery, at the same time as the Category.
l ID. Device ID. This is a unique number automatically assigned to the device by SL1.
l Organization. The organization to which the device is assigned.
l Collection State. The current condition of data collection for the device. The device can have one or more
of the following Collection States:

o Active. SL1 is collecting data from the device.

o Unavailable. SL1 cannot connect to the device, and will not collect data from the device until the
device becomes available. A physical device falls back to executing the availability ping every five
minutes, unless you have critical ping enabled. Component devices get their availability calculated
by the component discovery Dynamic Application of the parent device.
o User-Disabled. SL1 is not currently collecting data from the device because the user has disabled
collection.
o System-Disabled. SL1 is not currently collecting data from the device because the system has disabled
collection.
o Maintenance. SL1 is not currently collecting data from the device because it is currently in scheduled
maintenance mode.
o User-Initiated-Maintenance. SL1 is not currently collecting data from the device because it has
manually been put into maintenance mode by a user.
o Component Vanished. The component device has vanished, i.e. is not currently being reported by its
root device. SL1 cannot collect data from the device at this time.

Creating a Device Group 29

 NOTE: Depending on the circumstances, more than one collection state might appear for a single device.
For example, if a device is in a scheduled maintenance mode, the Collection State might be
Unavailable / Maintenance / System-Disabled.

l Tools. Displays icons for managing devices. The choices are:

o Device Management ( ). Leads to the Device Summary page, where you can see reports and
logs related to the device. From the Device Summary page, you can also access the other pages in
the Device Management tools.

Matched Devices

This is the list of devices that match all the criteria in the Relationship Selection page.

For each Matched Device, the Relationship Selection page displays:

TIP: To sort the list of devices, click on a column heading. The list will be sorted by the column value, in
ascending order. To sort by descending order, click the column heading again.

l Device Name. Name of the device. For devices running SNMP or with DNS entries, the name is discovered
automatically. For devices without SNMP or DNS entries, the device's IP address will appear in this field.
l Category. The ScienceLogic category assigned to the device. Categories include servers, routers, switches,
firewalls, printers, etc. The category is automatically assigned during discovery, at the same time as the
Device-Class/Sub-Class.
l Class / Sub-class. The manufacturer (device class) and type of device (sub-class). The Device-Class/Sub-
Class is automatically assigned during discovery, at the same time as the Category.
l ID. Device ID. This is a unique number automatically assigned to the device by SL1.
l Organization. The organization to which the device is assigned.
l Collection State. The current condition of data collection for the device. The device can have one or more
of the following Collection States:

o Active. SL1 is collecting data from the device.

o Unavailable. SL1 cannot connect to the device, and will not collect data from the device until the
device becomes available.
o User-Disabled. SL1 is not currently collecting data from the device because the user has disabled
collection.
o System-Disabled. SL1 is not currently collecting data from the device because the system has disabled
collection.
o Maintenance. SL1 is not currently collecting data from the device because it is currently in scheduled
maintenance mode.

30 Creating a Device Group

 o User-Initiated-Maintenance. SL1 is not currently collecting data from the device because it has
manually been put into maintenance mode by a user.
o Component Vanished. The component device has vanished, i.e. is not currently being reported by its
root device. SL1 cannot collect data from the device at this time.

NOTE: Depending on the circumstances, more than one collection state might appear for a single device.
For example, if a device is in a scheduled maintenance mode, the Collection State might be
Unavailable / Maintenance / System-Disabled.

l Tools. Displays icons for managing devices. The choices are:

o Device Management ( ). Leads to the Device Summary page, where you can see reports and logs
related to the device. From the Device Summary page, you can also access the other pages in the
Device Management tools.

Click the [OK] button to accept all changes and exit the Relationship Selection page.

Editing and Deleting Dynamic Rules

To edit a dynamic rule:

1. Go to the Dynamic Rules pane.

2. Find the dynamic rule you want to edit. Click its wrench icon ( ).

3. The Device Group Rule Editor modal page appears.

4. In the Device Group Rule Editor modal page, you can edit existing criteria, delete existing criteria, or add
new criteria.

To delete one or more dynamic rules:

1. Go to the Dynamic Rules pane.

2. For each dynamic rule you want to delete, select its checkbox.
3. Click the [Del] button.
4. Each selected dynamic rule is no longer displayed in the Dynamic Rules pane. The device group will no
longer include devices that matched the deleted dynamic rule(s).

Creating Device Groups From Views

You can also create a new device group from an existing device group in the Device Group Map page. To learn
more about creating a device group from an existing device group, see the section Creating a Device Group
from an Existing Map in the section on Using Device Group Views.

You can also create a view in Classic Maps > My Customized Maps. That new view will be saved as a device
group.

Creating a Device Group 31

 A Customized Map allows you to view the devices and links that are most important to you.

When you create a Customized Map, you are also creating a new device group (which appears in the Device
Group page). You can add devices and other sub-device groups to the new map, just as you would to a
standard device group.

To learn more about how to use Customized Maps, see the manual Views.

Editing an Existing Device Group

You can edit the properties of an existing device group, including adding or deleting devices from the device
group and adding or deleting other (child) device groups from the device group.

To edit an existing device group:

1. Go to the Device Group page (Registry > Devices > Device Groups).
2. In the Device Group page, find the device you want to edit. Click its wrench icon ( ).

3. The Device Group Editor page appears, populated with values from the selected device group.
4. You can edit the values in one or more of the fields in this page. For details on each field, see the section on
Creating a Device Group.
5. Click the [Save] button to save your changes to the device group.

You can also add devices to a device group from the Device Manager page. To add devices to an existing
device group from the Device Manager page:

1. Go to the Device Manager page (Registry > Devices > Device Manager).
2. In the Device Manager page, select the checkbox for each device you want to add to an existing device
group.
3. In the Select Action drop-down list, the Add to Device Group list shows each device group the device(s) can
be added to.
4. Select the device group you want to add the device(s) to. To add the device(s), click the [Go] button.
Depending on the Visibility setting for the device group, the selected device(s) will then appear in the Device
Group Editor, the Group Maps View, the Device Group Views (Classic Maps > Classic Views > Device
Groups), and the Custom Device Group Map (Classic Maps > My Customized Maps) and will inherit the
properties of the device group, including scheduling, event suppression, and automation policy
membership.

Assigning Devices to a Device Group During Discovery

You can add devices to a device group during discovery. To learn more about assigning devices to a device
group during discovery, see the section Assigning Device Groups and Applying Device Templates During
Discovery.

32 Editing an Existing Device Group

Controlling Access to a Device Group
When creating or editing a device group, you can define the actions that can be performed with the device group
and also determine which users will be allowed to access the device group. These sections will describe how to
control access to a device group.

Defining the Actions for a Device Group

The Visibility field in the Device Group Editor page defines which actions can be performed with the device
group.

NOTE: Users who are allowed to view the device group will automatically be allowed to perform the selected
actions on the device group.

l Visibility. Specifies where in SL1 the device group will be visible. Choices are:

o Maps/Views. If selected, the device group will appear in the Device Group Map page (Classic
Maps > Device Maps > Device Groups).
o Config Policies/Bulk Edit. If selected, the building blocks icon ( ) is visible in the Device Group
page. This allows you to configure all the devices in the device group using a device template.
o Notification/Automation. If selected, the device group will appear in the list of device groups in the
Automation Policy Editor modal page (Registry > Run Book > Automation > Edit/Create). This
page allows you to trigger an automatic action if specified criteria are met on all the devices in the
device group.
o Discovery. If selected, the device group appears in the field Auto-add Devices to Device Group in
the Discovery Control Panel page (System > Manage > Classic Discovery). This allows you to
automatically add newly discovered devices to a pre-existing device group during the discovery
process.
o Device Schedules. If selected, the calendar icon ( ) is visible in the Device Group page. This
allows you to schedule downtime for all the devices in the device group. The scheduled downtime will
appear in the Maintenance Schedule page for each device in the device group.
o Event Suppression. If selected, the device group will appear in the Suppressions tab in the Event
Policy Editor page. In this page, you can suppress the event for all devices in the device group.

o IT Services. This is a view-only option. If this option is selected when the Device Group Editor is
loaded, the device group is associated with an IT service and was created automatically by SL1. Do
not select or deselect this option.

Controlling Access to a Device Group 33

Deleting a Device Group
You can delete a device group. Deleting a device group does not delete its member devices or affect the
configuration of the member devices. When you delete a device group, you can no longer manage the member
devices as a group.

NOTE: When you delete a parent device-group, the child groups are not deleted.

To delete a device group:

1. Go to the Device Groups page (Registry > Devices > Device Groups).
2. In the Device Groups page, find the device group you want to delete. Select its checkbox. To select all
device groups, click the gray checkmark ( ).
3. In the Select Action drop-down in the bottom right of the page, select DELETE Device Groups.
4. The device group is deleted and no longer appears in the list of device groups.

Example of Creating a Device Group

Here is our example device group:

34 Deleting a Device Group

 l Title. We named our device group "windows_servers".
l Icon. We chose the Microsoft Windows icon.
l Force Child Visibility. We selected "Yes", so that the settings for the device group will apply to any future
child device groups.
l Visibility. We selected all options, so our new device group is visible in all areas of SL1.
l Sharing Permissions. We selected "Shared with users in your organizations", so other users of type "user"
can view the use the device group.
l Permission Keys. We did not select any permission keys for the device group. This means that any user who
has permission to view the Registry > Devices > Device Groups page and is a member of our organization
can view the device group.
l Add Remove Devices. We selected four Windows servers to be members of this device group.

Example of Creating a Device Group 35

 Chapter

4
Creating and Editing Device Templates

Overview
Device templates allow you to save a device configuration, apply it to one or more devices, and reuse the same
configuration over and over again. A device template contains multiple tabs. For a list of the tabs and their
descriptions, see the Creating a Device Template section.

When you apply a device template to a device group or to selected devices, all the devices that use the device
template will inherit the field values from the device template. Therefore, you will not need to manually define
settings for each device in the affected pages.

You can use a device template in multiple ways:

l You can apply a device template to a device group to automate the configuration of all devices in the
device group.
l From the Device Manager page (Registry > Devices > Device Manager), you can apply a device template
to one or more selected devices to automate the configuration of the selected devices.
l From the Device Groups page (Registry > Devices > Device Groups), you can use the bulk configuration
tool to apply configuration settings to all the devices in a device group. These configuration settings do not
have to be defined or saved in a device template.
l From the Device Manager page (Registry > Devices > Device Manager), you can use the bulk
configuration tool to apply configuration settings to one or more selected devices. These configuration
settings do not have to be defined or saved in a device template.

All the ways to use a device template are described in the section on using device templates.

This chapter describes how to create a device template and how to edit a device template.

Use the following menu options to navigate the SL1 user interface:

36
 l To view a pop-out list of menu options, click the menu icon ( ).

l To view a page containing all of the menu options, click the Advanced menu icon ( ).

This chapter covers the following topics:

Before You Start 37

Viewing the List of Device Templates 37
Filtering the List of Device Templates 38
Creating a Device Template 41
Creating a New Device Template Based on an Existing Device Template 63
Editing an Existing Device Template 63

Before You Start

Before you start creating and working with device templates, consider the following:

l How have you defined device groups? Can you apply a uniform set of configuration settings to all the
devices in a device group?
l Are there multiple devices that require the same set of configuration settings? Could you create a device
template to configure these devices?
l Do most of the devices in a device group require a uniform set of configuration settings, yet there are a few
devices that require a different set of configuration settings? If so, you could create a child device group for
the few devices that require a different set of configuration settings. You could apply one device template to
the parent device group and another device template to the child device group.

Viewing the List of Device Templates

To view a list of existing device templates:

1. Go to the Configuration Templates page (Registry > Devices > Templates).

2. The Configuration Templates page displays the following about each device template:

l Template Name. Name of the configuration template.

l ID. Unique, numeric ID, assigned to the device template automatically by SL1.
l Created By. Username of the user who created the device template.
l Created On. Date the device template was created.
l Last Edited By. Username of the user who created or last edited the device template.
l Edited On. Date and time the device group was created or last edited.
l Tools. For each device template, one or more of the following tools may be available:

37 Before You Start

 o
Edit this template( ). Leads to the Device Template Editor page, where you can view the
details of a device template and edit one or more values ion a configuration template.
o Checkbox( ). To delete a device template, select this checkbox, select the Select Actions drop-
down (in the lower right) and then select Delete Template.

Filtering the List of Device Templates

The Configuration Templates page includes six filters. You can filter the list of device templates by one or more
of the following parameters: Template Name, ID, Created By, Created On, Last Edited By, and Edited On.
You can specify one or more parameter to filter the display of device templates. Only device templates that meet
all of the filter criteria will be displayed in the Configuration Templates page.

You can filter by one or more parameters. The list of device templates is dynamically updated as you select each
filter. For each filter except Created On and Edited On, you must enter text to match against. SL1 will search for
device templates that match the text, including partial matches. Text matches are not case-sensitive.

You can use special characters in each filter.

To filter the list of device templates:

1. Go to the Configuration Templates page (Registry > Devices > Templates).

2. The Configuration Templates page displays a list of device templates. To sort the list, you can enter a
value in one or more of the following headings:

Filtering the List of Device Templates 38

 l Template Name. Name of the device template. You can enter text to match, including special
characters, and the Configuration Templates page will display only device templates that have a
matching template name.
l ID. Unique, numeric ID, assigned to the device template automatically by SL1. You can enter
numbers to match, including special characters, and the Configuration Templates page will
display only device templates that have a matching template ID.
l Created By. ScienceLogic user who created the device template. You can enter text to match,
including special characters, and the Configuration Templates page will display only device
templates that were created by a matching username.
l Created On. Date and time the device template was created. You can select from a list of time
periods. The Configuration Templates page will display only device templates that were created
within that time period.
l Last Edited By. ScienceLogic user who last edited the device template. You can enter text to match,
including special characters, and the Configuration Templates page will display only device
templates that were edited by a matching username.
l Last Edited. Date and time the device template was last edited. You can select from a list of time
periods. The Configuration Templates page will display only device templates that were last edited
within that time period.

Special Characters
When filtering a list in a registry page, you can include the following special characters to search each field
except those that display date and time:

NOTE: When searching for a string, SL1 will match substrings by default, even if you do not include any
special characters. For example, searching for "hel" will match both "hello" and "helicopter". When
searching for a numeric value, SL1 will not match a substring unless you use a special character.

Special
Description Example
Character
, (comma) (For strings or numeric values) Specifies an OR operation. "dell,micro" would match all
values that contain the string
"dell" OR the string "micro".
& (For strings or numeric values) Specifies an AND operation. "dell&micro" would match all
(ampersand values that contain both the string
"dell" AND the string "micro", in
any order.
! (For strings or numeric values) Specifies a NOT operation. "!dell" would match all values that
(exclamation NOTE: You can also use the "!" character in combination do not contain the string "dell".
point) with the arithmetic special characters (min-max, >, <, >=,
<=, =) described below.
* (asterisk) (For strings or numeric values) Specifies a "match-zero-or- l "hel*er" would match
more" operation. "helpers" and "helicopter"
For a string, matches any string that matches the text before but not "hello".

39 Filtering the List of Device Templates

Special
Description Example
Character
and after the asterisk. For a numeral, matches any numeral l "325*" would match "325",
that contains the text. "32561", and "325000".
l "*000" would match
"1000", "25000", and
"10500000".
? (question (For strings or numeric values) Specifies a "match any one l "l?ver" would match the
mark) character" operation. strings "oliver", "levers",
and "liver", but not
"believers".
l "135?" would match the
numbers "1350", "1354",
and "1359", but not
"13502".
^ (caret) (For strings only) Specifies a "match the beginning" operation. "^sci" would match "scientific"
Matches any string that begins with the specified string. and "sciencelogic", but not
"conscious".
$ (dollar) (For strings only) Specifies "match the ending". Matches any "ter$" would match the string
string that ends with the specified string. "renter" but not the string "terrific".
NOTE: You can use both ^ and $ if you want to match an
entire string. For example, "^tern$" would match the strings
"tern" or "Tern" or "TERN"; it would not match the strings "terne"
or "cistern".
min-max (For numeric values only) Matches any value between the "1-5 "would match 1, 2, 3, 4, and
specified minimum value and the maximum value, including 5.
the minimum and the maximum.
- (dash) (For numeric values only) A "half open" range. Matches values l "1-" matches 1 and
including the specified minimum and greater, or including the greater, so it would match
specified maximum and lesser. 1, 2, 6, 345, etc.
l "-5" matches 5 and less, so
it would match 5, 3, 1, 0,
etc.
> (greater (For numeric values only) Matches any value greater than the ">7" would match all values
than) specified value. greater than 7.
< (less than) (For numeric values only) Matches any value less than the "<12" would match all values less
specified value. than 12.
>= (greater (For numeric values only) Matches any value that is equal to or ">=7" would match all values 7
than or equal greater than the specified value. and greater.
to)
<= (less than (For numeric values only) Matches any value that is equal to or "<=12" would match all values
or equal to) less than the specified value. 12 and less.
= (equal) (For numeric values only) Matches a value that is equal to the "=-5 " would match "-5" instead
the specified value. of being evaluated as the "half
You can also use this special character to match a negative open range" as described above.

Filtering the List of Device Templates 40

Special
Description Example
Character
value, as demonstrated in the example.

Creating a Device Template

To define a new device template, perform the following steps:

1. Go to the Configuration Templates page (Registry > Devices > Templates).

2. Click the [Create] button. The Device Template Editor page appears.
3. In the Template Name field, supply a name for the template.
4. You can then supply values in one or more of the following tabs:

NOTE: In each tab, all of the fields are disabled (grayed-out) by default. To enable a field and change its
value, click on the field name.

l Config. Contains all the fields in the Device Properties page (except device name and device IP)
and all the fields in the Device Thresholds page. When you apply a device template to a device
group or selected devices, you do not have to manually define any settings in the Device Properties
page or the Device Thresholds page for the devices that use the template. All the devices that use
the template will inherit the field values from the device template.
l Interface. Contains all the fields in the Interface Properties page that define how SL1 will monitor
one or more network interfaces and the thresholds for those network interfaces. When you apply a
device template to a device group or selected devices, you do not have to manually define any
settings in the Interface Properties page for the devices that use the template. All the devices that
use the template will inherit the field values from the device template.
l CV Policies. Specifies one or more web-content policies that can be applied to all devices that use
the template. These web-content policies enable SL1 to monitor a website. SL1 will periodically check
the website for specified content. If the content cannot be found on the website, SL1 will generate an
event. When you apply a device template to a devices, you do not have to manually define any web-
content and availability policies in the Monitoring Policies page for the devices. All the devices that
use the template will inherit the web-content policies from the device template; SL1 will automatically
create these web-content policies for each device that uses the template.
l Port Policies. Specifies one or more TCP/IP Port policies that can be applied to all member devices.
These TCP/IP Port policies tell SL1 to monitor a specified port for availability every five minutes.
Availability refers to the port's ability to accept connections and data. When you apply a device
template to a device group, you do not have to manually define any TCP/IP port policies in the
Monitoring Policies page for the member devices. All the devices in the device group will inherit the
TCP/IP port policies from the device template; SL1 will automatically create these port policies for
each device that uses the template.

41 Creating a Device Template

 l Svc Policies. Specifies one or more Windows service policies that can be applied to devices that use
the template. These Windows service policies tell SL1 to monitor the device and look for the specified
service. You can define a service policy so that SL1 monitors whether or not the service is running and
then performs an action (starts, pauses, or restarts the service, reboots or shuts down the device,
triggers the execution of a remote script or program). When you apply a device template to devices,
you do not have to manually define any Windows service policies in the Monitoring Policies page
for those devices. All the devices that use the template will inherit the Windows service policies from
the device template; SL1 will automatically create these Windows service policies for each device that
uses the template.
l Proc Policies. Specifies one or more Process policies that can be applied to devices that use the
template. These Process policies tell SL1 to monitor the device and look for the process. You can
define a process policy so that SL1 monitors whether or not the process is running and optionally,
how much memory a process can use and how many instances of a process can run simultaneously.
When you apply a device template to devices, you do not have to manually define any Process
policies in the Monitoring Policies page for those devices. All the devices that use the device
template will inherit the Process policies from the device template; SL1 will automatically create these
process policies for each device that uses the template.
l Dynamic Apps. Specifies one or more Dynamic Applications that can be aligned with devices that
use the template. SL1 will use the specified Dynamic Applications to retrieve data from the devices
that use the template. (Note that each device that uses the template might also be aligned with
additional Dynamic Applications that have been aligned with the device in other ways; for example,
from the automatic alignment that occurs during discovery.) When you apply a device template to
devices, you do not manually have to align Dynamic Applications in the Dynamic Application
Collections page for those devices. All devices that use the device template will be aligned with the
Dynamic Applications specified in the device template.

o If you select a Dynamic Application in a Device Template, and that Dynamic Application has
associated thresholds, you can change one or more of those thresholds from the Device
Template. The thresholds you specify in the Device Template will override the thresholds defined in
the Dynamic Application. When you apply a device template to devices , you do not manually
have to edit the Dynamic Application Thresholds in the Device Thresholds page for those
devices. All devices that use the device template will inherit the Dynamic Application Thresholds
specified in the device template.
o You can change the frequency at which SL1 will poll all devices that use a device template to
retrieve the information specified in a Dynamic Application. This value will override the default
value specified in the Dynamic Applications.

l Logs. Specifies one or more Log File Monitoring Policies to apply to all devices that use the template.
A Log File Monitoring Policy specifies a log file or Windows log that the SL1 agent will monitor on a
device and the logs that the SL1 agent will send to SL1. When the SL1 agent sends a log to SL1,
SL1displays the log entry in the Device Logs for the associated device. SL1 can then use that log entry
to trigger events. When you apply a device template to devices, you do not have to manually define
any log monitoring policies in the Log File Monitoring page for those devices. All of the devices that
use the device template will inherit the log monitoring policies from the device template; SL1 will
automatically align the log monitoring policy with each device that uses the template.

Creating a Device Template 42

 5. In each tab in a device template, you can choose to define all the fields or you can choose to define only
one or more fields. When you apply the configuration template to devices, only those fields you defined in
the template will be applied to the devices. For the remaining fields, the devices will retain their previous
values or use the default values.
6. If you see a grayed-out field in a device template, this means that the template will not change the current
value for that field; the devices that use this template will retain their previous values or use the default
values for that field. To change the value of a grayed-out field, simply click on the field and edit the value.

Defining Device Properties and Device Thresholds in the Config Tab

The [Config] tab allows you to define the configuration settings from the Device Properties page (except device
name and device IP) and all the fields in the Device Thresholds page.

In the [Config] tab, you can define one or more of the following fields:

NOTE: In the [Config] tab, you can choose to define all the fields from the Device Properties page and the
Device Thresholds page or you can choose to define only one or more fields. When you apply the
device template to devices, only those fields you defined in the template will be applied to the
devices. For the remaining fields, the devices will retain their previous values or use the default
values. When you have disabled a field, it appears grayed-out in the device template.

l Device Organization. Organization that will become the parent organization for the device. You can
select from a list of all organizations in SL1.

NOTE: If you include a device template in a PowerPack and then install the PowerPack on a different SL1
system, the Device Organization field will be cleared and disabled on the SL1 system where the
PowerPack is installed. For details, see the manual on PowerPacks.

l SNMP Read. The community string for read-only access to SNMP information on the device. The
community string is a password that allows SL1 to gather information from the device. This community string
is defined in the Credential Management page (System > Manage > Credentials).
l SNMP Write. The community string for write access to SNMP information on the device. The community
string is a password that allows SL1 to send information to the device. This community string is defined in the
Credential Management page (System > Manage > Credentials).

NOTE: SNMP credentials that are deleted from SL1 will also be removed from device templates.

l Availability Protocol. Protocol that SL1 will use to communicate with the device to determine the device's
availability. Choices are TCP, UDP, or ICMP.
l Avail Port. Port that SL1 will use to communicate with the device to determine the device's availability.

43 Creating a Device Template

 l Latency Protocol. Protocol that SL1 will use to communicate with the device to determine the device's
latency. Choices are TCP, UDP, or ICMP.
l Latency Port. Port that SL1 will use to communicate with the device to determine the device's latency.
l Avail + Latency Alert. Specifies how SL1 should respond when the device fails an availability check, a
latency check, or fails both. These options allow you to create separate events when SNMP fails on a device
and when a device is not up and running. Choices are:

o Enabled. SL1 will create the following events:

n If the device fails the availability check, generates the event "Device Failed Availability Check:
UDP - SNMP"
n If the device fails the latency check, generates the event, "Network Latency Exceeded
Threshold: No Response"
n If the device fails both the availability check and the latency check, generates the event
"Device Failed Availability and Latency checks"

o Disabled. SL1 will create the following events

n If the device fails the availability check, generates the event "Device Failed Availability Check:
UDP - SNMP"
n If the device fails the latency check, generates the event, "Network Latency Exceeded
Threshold: No Response"
n If the device fails both the availability check and the latency check, generates only the event
"Device Failed Availability Check: UDP - SNMP". The event "Network Latency Exceeded Threshold:
No Response" is suppressed under the availability event.

l Collection. Specifies whether SL1 will collect data from the device . Choices are "enabled" or "disabled".
l Collector Grp. Specifies the collector group that SL1 will use to collect data from the device. You can select
from a list of existing collector groups.
l Coll. Type. Specifies how SL1 should perform discovery. The choices are:

o Standard. SL1 will perform discovery of each device based on the device's IP address. This method is
appropriate for devices using standard DNS.
o DHCP. SL1 will perform discovery of each device based on the device's MAC address. This method is
appropriate for devices using DHCP.

l Critical Ping. Frequency with which SL1 should "ping" the device. If the device does not respond, SL1
creates an event. The choices are disabled, every 5 seconds, every 15 seconds, every 30 seconds, every 60
seconds, and every 120 seconds.

Creating a Device Template 44

 NOTE: SL1 does not use data from the critical ping to create device availability reports. SL1 will continue to
collect device availability data only every five minutes.

NOTE: Because high-frequency data pull occurs every 15 seconds, you might experience up to 15 seconds
of latency between an unavailable alert and that alert appearing in the Database Server if you set
Critical Ping to 5 seconds.

NOTE: You might experience some performance issues if you have a large number of devices using Internal
Collection Dynamic Applications (ICDAs) to monitor Critical Availability on a brief polling interval.

l Event Mask. Events that occur on a single device within the selected time interval are grouped together.
This allows related events to be rolled-up and posted together, under one event description. Select a time
span from the drop-down list. Values range from 30 seconds to 1 month.
l Auto-Clear Events. Auto Clear automatically removes an event from the Event Console if a specified
succeeding event occurs. For example, suppose the event "Device not responding to ping" occurs. If the next
polling session produces the event "Device now responding normally to ping", the Auto Clear feature could
clear the event. If you do not want events to be cleared automatically, uncheck this field. For the selected
device, this field overrides the global auto-clear settings in the Event Policy Editor page.
l Accept All Logs. This checkbox specifies whether or not you want to keep and save all logs for this device. If
you want to retain only logs associated with events, uncheck this field.
l Daily Port Scans. This checkbox specifies whether or not you want SL1 to perform a daily scan of the device
for open ports.
l Auto-Update. This checkbox specifies whether or not you want SL1 to perform a nightly discovery of the
device and update records with changes to the device. If this field is unchecked, SL1 will not perform nightly
discovery; changes to the device, including newly opened ports, will not be recorded by SL1.
l Bypass Interface Inventory. This checkbox specifies whether or not the discovery processes should
discover network interfaces. This value is used during re-discovery (clicking the binoculars icon ( ) in the
Device Properties page) and during nightly auto-discovery (run automatically by SL1 every night to update
device information).

o If selected, discovery processes will not attempt to discover interfaces for each device aligned with this
template.
o If not selected, discovery processes will attempt to discover network interfaces for each device aligned
with this template using the Interface Inventory Timeout value and Maximum Allowed Interfaces
value for the device.

l Scan All IPs. If selected, SL1 will scan all IP addresses on a device when looking for open ports. If the device
uses multiple IP Addresses, SL1 will scan for open ports on all IPs during initial dynamic-discovery and
nightly dynamic-discovery.

45 Creating a Device Template

 l Dynamic Discovery. If selected, SL1 will automatically assign the appropriate Dynamic Applications to the
device during discovery.
l Preserve Hostname. If selected, the name of the device in SL1 will remain the same, even if the name of the
actual device is changed. If unselected, the SL1 name for the device will be updated if the name of the
actual device is changed.
l Disable Asset Update. If selected, during nightly discovery, SL1 will not update the asset record associated
with the device. For the selected device, this checkbox over-rides any settings defined in the Asset
Automation page (System > Settings > Assets).
l System Latency. During polling, SL1 initially pings monitored devices. The value in this field is the
maximum number of milliseconds for the device to respond to SL1's ping (round-trip time divided by 2).
When the latency threshold is exceeded, SL1 generates an event for that device. The default value is 1500
ms. To disable this threshold for the current device, set the threshold to 0 (zero) milliseconds. When you
disable a threshold, SL1 does not generate an event for the threshold.
l Availability Ping Count. If the Availability Protocol for a device is set to ICMP, this field specifies the
number of packets that should be sent during each availability check. The default value is 1.
l Availability Packet Size. If the Availability Protocol for a device is set to ICMP, this field specifies the size
of each packet, in bytes, that is sent during each availability check. The default value is 56 bytes.
l Availability Required Ping Percentage. If the Availability Protocol for a device is set to ICMP, this field
specifies the percentage of packets that must be returned during an availability check for SL1 to consider the
device available. The default value is 100%.
l Device Logs Max. Maximum number of records to store in the device log. When a log file reaches its
maximum size, the oldest records will be deleted. The default value is 495,000 records.
l Device Logs Age. Maximum number of days to store each record in the device log. Records that are older
than the specified number of days are automatically deleted. The default value is 546 days.
l Bandwidth Data. Number of days to retain bandwidth usage data and CBQoS bandwidth data collected
from each interface on a device. This data is collected as frequently as every minute (depending upon the
user-defined monitoring policy). Bandwidth data that is older than the specified number of days is
automatically deleted. The default value is defined in the Data Retention Settings page (System > Settings >
Data Retention).
l Daily Rollup Bandwidth Data. Number of days to retain daily normalized data and daily normalized
CBQoS data for each interface on a device. Daily normalized data that is older than the specified number
of days is automatically deleted. The default value is defined in the Data Retention Settings page (System >
Settings > Data Retention).
l Hourly Rollup Bandwidth Data. Number of days to retain hourly normalized data and hourly normalized
CBQoS data for each interface on a device. Hourly normalized data that is older than the specified number
of days is automatically deleted. The default value is defined in the Data Retention Settings page (System >
Settings > Data Retention).
l Raw Performance Data. Number of days to store raw performance data (usually data collected by
Dynamic Applications).

Creating a Device Template 46

 l Daily Rollup Performance Data. Number of days to retain daily normalized performance data for the
device. This setting applies to daily normalized availability data, normalized latency data, normalized file
system data, normalized data for monitoring policy statistics, and normalized data for Performance
Dynamic Applications for which a specific Daily Rollup Retention setting has not been defined. Daily
normalized performance data that is older than the specified number of days is automatically deleted. The
default value is defined in the Data Retention Settings page (System > Settings > Data Retention).
l Hourly Rollup Performance Data. Number of days to retain hourly normalized performance data for the
device. This setting applies to hourly normalized availability data, normalized latency data, normalized file
system data, normalized data for monitoring policy statistics, and normalized data for Performance
Dynamic Applications for which a specific Hourly Rollup Retention setting has not been defined. Hourly
normalized performance data that is older than the specified number of days is automatically deleted. The
default value is defined in the Data Retention Settings page (System > Settings > Data Retention).
l Journal Data. Number of days to retain raw collected data from Dynamic Applications of type "journal."
The default value is defined in the Data Retention Settings page (System > Settings > Data Retention).
l Configuration Data. Number of days to retain data from Dynamic Applications of type “configuration.”
The default value is defined in the Data Retention Settings page (System > Settings > Data Retention).
l SSL Certificate Purge Timeout. Specifies the number of days after which SSL certificate data will be
purged. The default value is 0 days.

NOTE: In SL1, normalized data does not include polling sessions that were missed or skipped. So for
normalized data, null values are not included when calculating maximum values, minimum values,
or average values.

TIP: You might want to retain normalized data for longer periods of time and non-normalized data for shorter
periods of time. This allows you to save space and still create historical reports.

l Interface Inventory Timeout. Specifies the maximum amount of time that the discovery processes will
spend polling a device for the list of interfaces. After the specified time, SL1 will stop scanning the device,
will not update the device, and will continue with discovery. When a value for this setting is specified for a
device in the Device Thresholds page or applied to a device using a device template, this setting is used
during re-discovery (clicking the binoculars icon ( ) in the Device Properties page) and during nightly
auto-discovery (run automatically by SL1 every night, to update device information). The default value is
600,000 ms (10 minutes).
l Maximum Allowed Interfaces. Maximum number of interfaces per device. If a device exceeds this number
of interfaces, SL1 will stop scanning the device, will not update the device, and will continue with discovery.
When a value for this setting is specified for a device in the Device Thresholds page or applied to a device
using a device template, this setting is used during re-discovery (clicking the binoculars icon ( ) in the
Device Properties page) and during nightly auto-discovery (run automatically by SL1 every night, to update
device information). The default value is 10,000.

47 Creating a Device Template

Defining Interface Monitoring in the Interface Tab
The [Interface] tab allows you to define one or more fields from the Interface Properties page; these fields
define how SL1 will monitor one or more network interfaces and the thresholds for those network interfaces. Each
field that you define will be applied to all the devices that use the template.

In the [Interface] tab, you can define one or more of the following fields:

l Apply Settings To. Specifies which interfaces should use the settings defined in this tab. The choices are:

o All Interfaces on device. Applies the settings to all discovered network interfaces on each member
device.
o Management interface only. Applies the settings only to the interface that SL1 uses to communicate
with each member devices.

l Collection State. This field can have one of two values:

o Enabled: SL1 monitors the network interface and collects data on the network interface for reports.
o Disabled: SL1 does not monitor the network interface or collect data on the network interface for
reports.

l Collection Frequency. When you enable monitoring (collection) for an interface, you must specify how
frequently you want SL1 to collect data from the interface. Your choices are every:

o 1 Minute
o 5 Minutes
o 10 Minutes
o 15 Minutes
o 30 Minutes
o 60 Minutes
o 120 Minutes

The Network Interface reports will display the average incoming and outgoing bandwidth-usage for the
current day in the selected intervals.

l Interface Alerting. Alerting for this interface can be enabled or disabled. When disabled, the interface is
monitored, but events are not generated for the interface.
l Rollover Alerting. Specifies whether or not SL1 will generate an event when the counter for the interface
rolls over. This field does not affect the Network Usage graphs. This field is most helpful for interfaces that
are busy and require frequent monitoring, but for which the device supports only 32-bit counters (instead of
64-bit counters). The counters on such interfaces rollover frequently.

Creating a Device Template 48

 l Collect Errors. Specifies whether or not SL1 will collect data on packet errors on the interface. Packet errors
occur when packets are lost due to hardware problems such as breaks in the network or faulty adapter
hardware.
l Collect Discards. Specifies whether or not SL1 will collect data on interface discards. Discards occur when
an interface receives more traffic than it can handle (either very large message or many messages
simultaneously). Discards can also occur when an interface has been specifically configured to discard. For
example, a user might configure a router's interface to discard packets from a non-authorized IP.
l Measurement Scale. Unit of measurement for bandwidth reports for the interface. The choices are:

o Mega
o Giga
o Kilo
o Tera
o Peta
l Percentile Calculation. The basis for bandwidth billing for this interface. The choices are:

o Accumulative. Customer is billed for total inbound and outbound bandwidth for all applicable
interfaces. Billing is at the specified percentile point.
o Inbound. Customer is billed for the total inbound bandwidth for all applicable interfaces. Billing is at
the specified percentile point.
o Outbound. Customer is billed for the total outbound bandwidth for all applicable interfaces. Billing is
at the specified percentile point.
o Highest Poll. Customer is billed for either the total inbound or total outbound, whichever is highest,
for each applicable interfaces. Billing is at the specified percentile point.

l Counter Type. Specifies whether the interface uses a 32-bit counter or a 64-bit counter to measure
bandwidth on the interface. During discovery, SL1 automatically discovers which type of counter is
associated with each interface. A 32-bit counter will roll-over (restart at 0) after about four billion octets
(bytes) have passed through the interface. A 64-bit counter will roll-over after 1.85 x 1016 octets (bytes)
have passed through the interface. Most high-speed interfaces use a 64-bit counter to measure bandwidth
on the interface. If a 64-bit counter is available, SL1 will use it by default.

o Counter 32. Specify that the interface uses a 32-bit counter.

o Counter 64. Specify that the interface uses a 64-bit counter.

l Percentile Factor. Many service providers use a percentile bandwidth measure when billing customers for
bandwidth usage. In this field, you can select the percentile factor, and SL1 will perform the calculations for
you at billing time. For example, if a provider chose the percentile factor "95", SL1 would collect bandwidth
data every five minutes for an entire month. At billing time, the highest 5% of readings are dropped. The
customer is charged for the 95% highest reading. This prevents customers from being billed for unusual
spikes. The choices for percentile factor are:

49 Creating a Device Template

 o 100% -1%, in increments of 1%.

l Auto Name Update. Specifies whether SL1 should update or overwrite the interface name during nightly
discovery.
l Interface Name Format. Specifies the format of the network interface name that you want to appear in
events. If you selected Interface Alias for the deprecated Interface Name Precedence field in a previous
release of SL1, the format for existing interfaces is set to {alias}. If you selected “Interface Name” for the
deprecated Interface Name Precedence field in a previous release of SL1, the format for existing
interfaces is set to {name}. The default format is {name}. You can use a combination of string text and the
following tokens to define the interface name format for events, such as string_{name}, string_{alias},
{name}{alias}, or {ifdesc}:

o {alias}
o {name}
o {state}
o {ifdescr}
o {if_id}
o {did}
o {ifindex}
o {ifphysaddress}
o {iftype}
o {ifspeed}
o {ifhighspeed}
o {ifoperstatus}
o {ifadminstatus}

NOTE: If Disable Discovery Name Update is selected for an interface in its Interface Properties page,
SL1 cannot change the interface name during nightly auto-discovery and during re-discovery,
regardless of the settings in the Interface Event Display Name field. To apply a new naming
convention to interfaces, you must first ensure that Disable Discovery Name Update is not selected
for those interfaces. You can do this in the Network Interfaces page (Registry > Networks >
Interfaces): select the interfaces you want to rename, select the Select Actions field (in the lower
right), and choose Auto-Name Update > Enable.

If you have specified that SL1 should monitor an interface, SL1 will collect data about the interface and also
monitor performance thresholds for the interface. SL1 will use either the default threshold or the custom threshold
you define in this pane.

Creating a Device Template 50

 l Inbound %. If the rate of inbound transfer on the interface is greater than the value selected in this field, SL1
will generate an event. Possible choices are 0% through 100%. The value can include up to three digits after
the decimal point. The percentage is in relation to all traffic on the interface. So if inbound transfer on this
interface exceeds the selected percentage of all traffic, SL1 will generate an event. The default value is 65%.
l Outbound %. If the rate of outbound transfer on the interface is greater than the value selected in this field,
SL1 will generate an event. Possible choices are 0% through 100%, in increments of 1%. The percentage is
in relation to all traffic on the interface. So if outbound transfer on this interface exceeds the selected
percentage of all traffic, SL1 will generate an event. The default value is 65%. The value can include up to
three digits after the decimal point.
l Inbound Bandwidth. If the rate of inbound transfer on the interface is greater than the value selected in this
field, SL1 will generate an event. The default value is 0 Mbps (no alerting). The value can include up to three
digits after the decimal point.
l Outbound Bandwidth. If the rate of outbound transfer on the interface is greater than the value selected in
this field, SL1 will generate an event. The default value is 0 Mbps (no alerting). The value can include up to
three digits after the decimal point.
l Inbound Errors. If the number of inbound packet errors on the interface is greater than the value selected in
this field, SL1 will generate an event. The default value is 0 packets (no alerting). The value can include up
to three digits after the decimal point.

NOTE: Packet errors occur when packets are lost due to hardware problems such as breaks in the network or
faulty adapter hardware.

l Outbound Errors. If the number of outbound packet errors on the interface is greater than the value
selected in this field, SL1 will generate an event. The default value is 0 packets (no alerting). The value can
include up to three digits after the decimal point.
l Inbound Discards. If the number of inbound discards on the interface is greater than the value selected in
this field, SL1 will generate an event. The default value is 0 packets (no alerting). The value can include up
to three digits after the decimal point.

NOTE: Packet discards occur when an interface receives more traffic than it can handle (either very large
message or many messages simultaneously). Discards can also occur when an interface has been
specifically configured to discard. For example, a user might configure a router's interface to discard
packets from a non-authorized IP.

l Outbound Discards. If the number of outbound discards on the interface is greater than the value selected
in this field, SL1 will generate an event. The default value is 0 packets (no alerting). The value can include up
to three digits after the decimal point.
l Inbound Error %. If the percentage of inbound errors (that is, the percentage of all inbound traffic during a
single polling session that results in an error) on this interface is greater that the value selected in this field,
SL1 will generate an event. The value can include up to three digits after the decimal point.

51 Creating a Device Template

 l Outbound Error %. If the percentage of outbound errors (that is, the percentage of all outbound traffic
during a single polling session that results in an error) on this interface is greater that the value selected in
this field, SL1 will generate an event. The value can include up to three digits after the decimal point.
l Inbound Discard %. If the percentage of inbound discards (that is, the percentage of all inbound traffic
during a single polling session that results in a discard) on this interface is greater that the value selected in
this field, SL1 will generate an event. The value can include up to three digits after the decimal point.
l Outbound Discard %. If the percentage of outbound discards (that is, the percentage of all outbound
traffic during a single polling session that results in a discard) on this interface is greater that the value
selected in this field, SL1 will generate an event. The value can include up to three digits after the decimal
point.

Defining Web-Content Monitoring in the CV Policies Tab

The [CV Policies] tab allows you to define one or more web-content and availability policies. These policies
enable SL1 to monitor a website. SL1 will periodically check the website for specified content. If the content
cannot be found on the website, SL1 will generate an event.

In the [CV Policies] tab, you can define one or more of the following fields:

l Subtemplate Selection. In this pane, you can choose to add a new Web Content Monitoring policy to the
configuration template or edit an existing Web Content Monitoring policy in the configuration template.

Creating a Device Template 52

 o To add a new Web Content Monitoring policy to the configuration template, select Add New
CV Sub-template.
o To edit an existing Web Content Monitoring policy, highlight it. The remaining panes will be
populated with values from the selected policy.

l Policy Name. Name of the new policy. Can be any combination of letters and numbers.
l State. Specifies whether or not the policy is active. You can select one of the following:

o Enabled. Policy is active. SL1 will query the specified website every five minutes.
o Disabled. Policy is not active.

l Port. Port on web-server to which SL1 will send queries. This is usually port 80 (the HTTP port) or port 443
(the HTTPS port).
l Timeout. After specified number of seconds, SL1 should stop trying to connect to the website, or if already
connected, stop searching for content. If the timeout period elapses before SL1 can connect or find the
content, an event is generated.
l Uniform Resource Locator (URL). URL or IP address where the website is located. If the website requires
login and the login is forms-based (user enters username and password in the index page), include the
username and password in the URL. You can include the following variable in this field:

o %D. SL1 replaces this variable with the IP address of the currently aligned device.
o %N. SL1 replaces this variable with the hostname of the currently aligned device.

l Post String. If the URL is very long or requires data that cannot be transferred with a standard "GET" request
(that is, data that cannot be included in the URL), you can enter a POST string in this field. The data will be
sent with the cURL equivalent of an HTTP POST command. Data should be formatted as follows:

o variable=value
o If you are going to include more than one variable/value pair, separate each pair with an
ampersand.
o For example, suppose you want to send values for the following fields:

n Birthyear
n Value

o You could enter the following in the Post String field:

o Birthyear=1980%Value=OK

53 Creating a Device Template

 NOTE: If you want to include non-alphanumeric characters in the Post String field, make sure you encode
the characters using appropriate URL encoding.

l Cookie Value. For pages that require a cookie value to be set, enter the cookie value in this field.
l Browser Emulation. Specifies how to format the query. Select the agent that is compatible with the web
server.
l HTTP Auth Username:Password. For websites that pop-up a dialog box asking for username and
password, use this field. Enter the user name and password in this field. Use the format
"username:password".
l SSL Encryption. Specifies whether SL1 should use SSL when communicating with the website. If login for the
website is forms-based, enable this option.
l Expression Check #1. Regular expression to search for.
l Expression Check #2. Another regular expression to search for.
l Error Codes. Specifies the HTTP status code you expect to receive in the response. If any other status code
is returned, SL1 will generate an event.
l Referer String. URL of the website. Some load-balanced configurations will not allow a request for a
specific IP address. If you entered a specific IP address in the URL field, you can spoof a URL in this field.
l Host Resolution. Host name of the website. Some load-balanced configurations will not allow a request for
a specific IP address. If you entered a specific IP address in the URL field, you can spoof a fully-qualified host
name in this field. You can include the following variable in this field:

o %N. SL1 replaces this variable with hostname of the currently aligned device.

l Proxy Server:Port. For companies or organizations that use proxy servers, enter the URL and port for the
proxy server in this field. Use the format "URL:port_number".
l Proxy Username:Password. For companies or organizations that use proxy servers, enter the username
and password for the proxy server in this field. Use the format "username:password".
l Min Page size (Kb). Page size means the size of the page, in Kb, specified in the URL of the policy. If the
returned page is not at least the size specified in this field, SL1 generates an event. This threshold triggers the
event "Page size below minimum threshold."
l Max Page size (Kb). Page size means the size of the page, in Kb, specified in the URL of the policy. If the
returned page is larger than the size specified in this field, SL1 generates an event. This threshold triggers the
event "Page size above maximum threshold."
l Min Download speed (kb/s). Download speed is the speed, measured in Kb/s, at which data was
downloaded from the server (specified in the policy) to SL1. If the download speed is not at least the speed
specified in this field, SL1 generates an event. This threshold triggers the event "Download speed below
threshold."
l Max nslookup time (msec). NSlookup speed is the speed at which your DNS system was able to resolve
the name of the server specified in the policy. If the lookup time exceeded the value in this field, SL1
generates an event. This threshold triggers the event "DNS hostname resolution time above threshold."

Creating a Device Template 54

 l Max TCP connect time (msec). TCP connect time is the time it takes for SL1 to establish communication
with the external server. In other words, the time it takes from the beginning of the HTTP request to the
TCP/IP connection. If the connection time exceeds the value in this field, SL1 generates an event. This
threshold triggers the event "TCP connection time above threshold."
l Max overall transaction time (msec). Overall transaction time is the total time it takes to make a
connection to the external server, send the HTTP request, wait for the server to parse the request, receive the
requested data from the server, and close the connection. If the overall transaction time exceeds the value in
this field, SL1 generates an event. This threshold triggers the event "Total transaction time above threshold."

Defining TCP/IP Port Monitoring in the Port Policies Tab

The [Port Policies] tab allows you to define one or more TCP/IP Port policies (otherwise defined in the
Monitoring Policies page for a device). These TCP/IP Port policies tell SL1 to monitor a specified port for
availability every five minutes. Availability refers to the port's ability to accept connections and data.

In the [Port Policies] tab, you can define one or more of the following fields:

l Subtemplate Selection. In this pane, you can choose to add a new TCP/IP Port Monitoring policy to the
configuration template or edit an existing TCP/IP Port Monitoring policy in the configuration template.

o To add a new Port Monitoring policy to the configuration template, click Add New Port Sub-
template.
o To edit an existing Port Content Monitoring policy, highlight it. The remaining panes will be
populated with values from the selected policy.

l Add Policy To. Specifies how the template should apply the TCP/IP Port Monitoring policy. Choices are:

o All devices. SL1 will apply the TCP/IP Port Monitoring policy to each device aligned with this
configuration template.
o Only devices whose IP(s) have a matching port. SL1 will apply the TCP/IP Port Monitoring policy only
to those devices where the port is available.

l Per-IP Policy Creation. Specifies whether SL1 should apply the TCP/IP Port Monitoring policy to all IP
addresses on each member device or only to the Admin Primary IP address. Choices are:

o All Device IPs. SL1 will apply the TCP/IP Port Monitoring policy to all IP addresses on each member
device.
o Management IP Only. SL1 will apply the TCP/IP Port Monitoring policy only to IP address each
member device uses to communicate with SL1.

l Port/Service. Port number and the corresponding service running on the port.
l State. Can be one of the following:

55 Creating a Device Template

 o Enabled. Port is being monitored by ScienceLogic port Policy.
o Disabled. Port is not being monitored by ScienceLogic port Policy.

l Critical Poll. Frequency with which SL1 should "ping" the device. If the device does not respond, SL1 creates
an event. The choices are:

o Disabled. SL1 will not ping the device.

o Enabled. SL1 will ping the device every 60 seconds.

NOTE: SL1 does not use this ping data to create device availability reports. SL1 will continue to collect device
availability at the interval specified during discovery.

Defining Windows Services Monitoring in the Svc Policies Tab

The [Svc Policies] tab allows you to define one or more Windows service policies (otherwise defined in the
Monitoring Policies page for a device). These Windows service policies tell SL1 to monitor the device and look
for the specified service. You can define a service policy so that SL1 monitors whether or not the service is running
and then performs an action (starts, pauses, or restarts the service, reboots or shuts down the device, triggers the
execution of a remote script or program).

In the [Svc Policies] tab, you can define one or more of the following fields:

l Subtemplate Selection. In this pane, you can choose to add a new Windows Service Monitoring policy to
the configuration template or edit an existing Windows Service Monitoring policy in the configuration
template.

o To add a new Windows Service Monitoring policy to the configuration template, select Add
New Service Sub-template.
o To edit an existing Windows Service Monitoring policy, highlight it. The remaining panes will be
populated with values from the selected policy.

l Add Policy To. Specifies how SL1 should apply the template to member devices. Choices are:

o All devices. SL1 will apply the Windows Service Monitoring policy to each device aligned with this
configuration template, even if the specified Windows service is not available on each device.
o Only devices that have a matching service. SL1 will apply the Windows Service Monitoring policy only
to those member devices where the service is available.

l Service Name. Service to be monitored by the policy. Select from a list of all Windows services discovered
in the network by SL1.
l Alert if Found. Condition under which SL1 should create an event about the service. Choices are:

Creating a Device Template 56

 o Disabled. SL1 will create an event if the service is disabled.
o Enabled. SL1 will create an event if the service is enabled.

l Service Action. If the device is a Windows computer running a WMI agent, you can define some automated
actions, based on the condition specified in the Alert if Found field.

o Disabled. The Service Action field is disabled and no automated actions are performed.
o Stop Service. If the service has the condition specified in the Alert if Found field, stop the service.
o Start Service. If the service has the condition specified in the Alert if Found field, start the service.
o Pause Service. If the service has the condition specified in the Alert if Found field, pause the service.
o Restart Service. If the service has the condition specified in the Alert if Found field, restart the service.
l System Action. If the device is a Windows computer running a WMI agent, you can define some automated
actions, based on the condition specified in the Alert if Found field.

o Disabled. The System Action field is disabled and no automated actions are performed.
o Reboot System. If the service has the condition specified in the Alert if Found field, reboot the
computer.
o Shutdown System. If the service has the condition specified in the Alert if Found field, shutdown the
computer.
l Action Script. If the device is a Windows computer running a WMI agent, you can execute a script on the
computer, based on the condition specified in the Alert if Found field. For example, you might want to
execute a script if a service crashed; the script could execute the steps required to cleanup any problems
before restarting the service. In this field, you can specify the script to execute. The script must reside on the
managed device, in the directory c:/program files/snmp informant/operating_system/spawn.

Defining Process Monitoring in the Proc Policies Tab

The [Proc Policies] tab allows you to define one or more Process policies (otherwise defined in the Monitoring
Policies page for a device). These Process policies tell SL1 to monitor the device and look for the process. You
can define a process policy so that SL1 monitors whether or not the process is running and optionally, how much
memory a process can use and how many instances of a process can run simultaneously.

In the [Proc Policies] tab, you can define one or more of the following fields:

l Subtemplate Selection. In this pane, you can choose to add a new Process Monitoring policy to the
configuration template or edit an existing process Monitoring policy in the configuration template.

o To add a new Process Monitoring policy to the configuration template, click Add New Service
Sub-template.
o To edit an existing Process Monitoring policy, highlight it. The remaining panes will be populated
with values from the selected policy.

57 Creating a Device Template

 l Add Policy To. Specifies how SL1 should apply the template to member devices. Choices are:

o All devices. SL1 will apply the Process policy to each device aligned with this configuration template,
even if the specified process is not available on each device.
o Only devices that have a matching service. SL1 will apply the Process Monitoring policy only to those
member devices where the process is available.

l Process Name. The name of the process. Select from a list of all processes running on this device.
l Process Argument. The arguments with which the process is invoked.
l Memory Limit. The amount of memory each instance of the process is allowed to use. If an instance of this
process exceeds this memory limit, SL1 will generate an event. The event will have a severity of "Major" and
will say "process using too much memory". This is an optional field.
l Minimum Instances. The minimum number of instances of the process that should be running. If the
minimum instances are not running, SL1 generates an event. The event will be of severity "Major" and will
say "too few processes running."
l Maximum Instances. The maximum number of instances of the process you will allow to run. If the
maximum number of instances is exceeded, SL1 generates an event. The event will be of severity "major"
and will say " "too many processes process running."
l Process User. Search for the following process user or process owner when the process is running. This field
is helpful for finding processes running as root or su which should not be.

NOTE: Some hardware includes information about a process user or owner for each process in the SNMP
data; some do not. Do not specify a value in the Process User field if the device does not include
process user or process owner information in its SNMP data. If you specify a process user, and a
device does not include process user in its SNMP data, SL1 will not generate an alert, even if it finds
this process running.

l Alert if Found. If you enable this option, SL1 generates an event when this process runs. The event will be of
severity "major" and will say "Illicit process running."

Aligning Dynamic Applications and Defining Thresholds in the

Dynamic Apps Tab
The [Dynamic Apps] tab allows you to select one or more Dynamic Applications to align with devices that use
the device template. Dynamic Applications define which data will be collected from a device, the frequency of
collection, and how the data will be displayed. When you apply a device template to a device group or selected
devices, you do not have to manually align the Dynamic Applications with the devices that use the template. All
devices that use the template will be aligned with the Dynamic Applications specified in the device template.

Creating a Device Template 58

 If you select a Dynamic Application in a Device Template, and that Dynamic Application has associated
thresholds, you can change one or more of those thresholds in the Device Template. The thresholds in the Device
Template will override the thresholds defined in the Dynamic Application. When you apply a device template to
devices, you do not manually have to edit the Dynamic Application Thresholds in the Device Thresholds page
for the devices that use the template. All devices that use the template will inherit the Dynamic Application
Thresholds specified in the device template.

In the [Dynamic Apps] tab, you can define one or more of the following fields:

l Subtemplate Selection. In this pane, you can choose to add one or more existing Dynamic Application to
the configuration template.

o
To select the Dynamic Application, click on the green plus-sign ( ) and then select the Dynamic
Application in the Dynamic Application field.

l Align Dynamic Application With. Specifies how SL1 should apply the template to member devices.
Choices are:

o All devices (align new applications and update collection states). SL1 will align the Dynamic
Application with each device that uses the template, even if the SL1 cannot use the Dynamic
Application to retrieve data from one or more of those devices.
o Only devices that are already aligned to this application (update collection states only). SL1 will apply
the settings for this Dynamic Application only to each device that both uses this template and is
already aligned with the specified Dynamic Application.

l Dynamic Application. Select the Dynamic Application to include in the device template. You can select
from a list of all Dynamic Applications.
l Credentials. Select a credential for the selected Dynamic Application. You can select from a list of
credentials that are appropriate for the Dynamic Application. For example, if you select a Dynamic
Application of type "SNMP Performance", the Credentials field will allow you to select from a list of SNMP
credentials.
l Poll Rate. Frequency, in minutes, at which SL1 will poll all devices that use this device template and retrieve
the information specified in this Dynamic Application. You can use this field to set a custom polling
frequency for one or more devices.This value over-rides the default value for the Dynamic Application
(defined in the Dynamic Applications Properties Editor page). The default value is "1". Select from the
pull-down menu. The choices range from 1 minute to 24 hours.
l Dynamic Application Presentation Object(s). This pane displays a list of presentation objects (for
Dynamic Applications of type "Performance") or collection objects (for Dynamic Applications of type
"Configuration").

o A collection object is a data point that is monitored by the Dynamic Application. At the polling
frequency specified in the Dynamic Application, SL1 will retrieve a value for that data point.

For example, suppose you have a Dynamic Application named "Cisco: Environmental Status".

59 Creating a Device Template

 o This Dynamic Application contains a collection object named "fan_state". The collection object will
contain the current status of a fan.
o This Dynamic Application is aligned with the device "cisco_catalyst".
o The Dynamic Application will retrieve data from member devices every 30 minutes. This means
that every 30 minutes SL1 will connect to the device "cisco_catalyst" and retrieve the value for fan
status; possible values could be normal, warning, critical, and shutdown. This value will be stored
in the collection object "fan_state".

For each aligned device, SL1 displays the latest value for each collection object in the
Configuration Report page.

o You can enable or disable each collection object that appears in the Dynamic Object Collection
pane.

n Enabled. SL1 will try to collect data for this collection object at the frequency specified in the
Dynamic Application. SL1 will try to collect data for this collection object from each device that
uses the device template.
n Disabled. SL1 will not try to collect data for this collection object.

o A presentation object is a definition of a report. The definition is stored in an object (a presentation

object). The definition of the report is based on data retrieved with the Dynamic Application and
stored in collection objects. These reports appear in the Performance page for each aligned device.

For example, suppose you have a Dynamic Application named "Cisco: Summary Statistics".
Suppose this Dynamic Application includes the presentation object "% I/O Memory Used".

Suppose that the definition of this presentation object is "(number of broadcast packets/number of
multicast packets) / 100", where "number of broadcast packets" is a collection object and "number
of multicast packets" is a collection object.

Suppose that this Dynamic Application has a polling frequency of every 30 minutes and is aligned
with the device "cisco_router". This means that every 30 minutes, SL1 will connect to the device
"cisco_router" and retrieve the collection objects for the Dynamic Application.

SL1 will then use the values from the collection objects "number of broadcast packets" and "number
of multicast packets" to calculate the value of the presentation object and then graph that value. SL1
will graph the value that results from each polling session in the Performance page for the aligned
device.

o You can enable or disable each presentation object.

n Enabled. This is the default value. For each device that uses the device template, SL1 will try to
generate the report defined by the presentation object. If SL1 can successfully retrieve the data
(from the collection objects specified by the presentation object) from the device, the report will
appear in the Performance page.
n Disabled. SL1 will not try to generate the report defined by the presentation object.

Creating a Device Template 60

 NOTE: As you disable a presentation object, SL1 checks the collection objects associated with the
presentation object. If a collection object is used in only one presentation object, and that
presentation object is disabled, SL1 will no longer collect data for the associated collection object. If
a collection object is used in multiple presentation objects, and one or more of those presentation
objects is still enabled, SL1 will continue to collect data for the associated collection object. If a
collection object is used in multiple presentation objects, and all those presentation objects are
disabled, SL1 will no longer collect data for that collection object.

l Dynamic Application Thresholds. This pane displays a list of threshold objects associated with the
Dynamic Application. You can accept the default value as defined in the Dynamic Application, or you can
manually change the value within this template.

o A threshold object is a variable that contains a threshold value. SL1 can use this threshold value
when defining alerts and presentation objects.

For example, suppose we have a Dynamic Application named "Cisco:Swap". Suppose this Dynamic
Application includes two collection objects: "Free Swap", and "Used Swap". Suppose this Dynamic
Application also includes a threshold object called "high_swap" with a value of "80".

We could then create an alert that uses the collection objects to specify "when swap usage exceeds
the value of the threshold object (80%), trigger an alert".

We could define an event policy, based on this alert.

For each aligned device, this swap threshold will also appear in the Device Thresholds page.

o To change the value of a threshold object, click on the name of the threshold and then move the
slider. The new threshold value will be used for each device that uses the device template.

l Raw Data Retention. Number of days to retain raw data collected from the device using this Dynamic
Application. Raw data that is older than the specified number of days is automatically deleted. The default
value is defined in the Data Retention Settings page.
l Crunched Data Retention. Appears only for Journal Dynamic Applications. Number of days to retain data
that has been processed using the presentation objects in this Dynamic Application. The default value is
defined in the Data Retention Settings page.
l Hourly Rollup Retention. Appears only for performance Dynamic Applications. Number of days to retain
hourly normalized data for this Dynamic Application. Hourly normalized data that is older than the specified
number of days is automatically deleted. The default value is defined in the Data Retention Settings page.
l Daily Rollup Retention. Appears only for performance Dynamic Applications. Number of days to retain
daily normalized data for this Dynamic Application. Daily normalized data that is older than the specified
number of days is automatically deleted. The default value is defined in the Data Retention Settings page.

Aligning Log File Monitoring Policies in the Logs Tab

Log File Monitoring policies can be aligned to devices using a Device Template.

61 Creating a Device Template

 The Logs tab allows you to align one or more Log File Monitoring Policies with the devices that use the device
template. A Log File Monitoring Policy specifies a log file or Windows log that the SL1 agent will monitor on a
device and the logs that the agent will send to SL1. When the SL1 agent sends a log to SL1, SL1 displays the log
entry in the Device Logs & Messages page for the associated device. SL1 can then use that log entry to trigger
events.

In the Logs tab, you can:

l Apply an existing Log File Monitoring Policy to each device that uses the device template.
l Override one or more of the parameters of the selected Log File Monitoring Policy. These overrides will
apply only to the devices that use this device template.

In the Logs tab, you can define one or more of the following fields:

l Subtemplate Selection. In this pane, you can choose to add one or more existing Dynamic Application to
the configuration template.

o
To align an existing Log File Monitoring Policy with the device template, click the plus icon (
) in the Subtemplate pane and then supply values in one or more of the fields.
o To edit a Log File Monitoring Policy in device template, go to the Subtemplate Selection pane
and select the Log File Monitoring Policy you want to edit. The field in the right pane will be
populated with values from the selected policy. You can then edit one or more values for the policy.

The Logs tab includes the following fields in the right pane:

l Align Log Monitoring Policy With. Select how to align the Log File Monitoring Policy. Choices are:

o All compatible devices. Apply the Log File Monitoring Policy to all devices that include the SL1 agent
and use an operating system supported by the type of Log File Monitoring Policy.
o Only devices that are already aligned to this log policy. Apply the edited Log File Monitoring Policy
only to devices that are already aligned with the Log File Monitoring Policy.

l Log Monitoring Policy. Select from a list of existing Log File Monitoring policies. Select the Log File
Monitoring Policy you want to align with devices to which the template is applied.

The following fields allow you to override one or more settings in the Log File Monitoring Policy you selected in
the Log Monitoring Policy field. These overrides apply only to devices that use the device template:

l File Path. If you selected File in the Type field, this field is displayed. Enter the full path of the file to monitor.
l Limit. The maximum log messages the agent sends to SL1 per minute. If the number of matching logs
exceeds this value, the agent will stop sending logs to the platform for the remainder of the minute. The limit
resets at the beginning of the next minute. For example, suppose you set this field to 10,000. Suppose the
agent monitors a device that has 30,000 log messages. The agent will retrieve 10,000 logs and then wait
until the beginning of the next minute. The agent will then retrieve the next 10,000 logs and then wait until
the beginning of the next minute. The agent will continue to retrieve 10,000 logs per minute until it has
retrieved all the logs from the device.

Creating a Device Template 62

 l Filter. Specify a regular expression that will be used to evaluate the log messages in the specified file or
Windows log. If a log message matches this regular expression, the SL1 agent will send that log message to
SL1. If a log message does not match this regular expression, the SL1 agent will not send that log message
to SL1.

Creating a New Device Template Based on an Existing Device

Template
To define a new device template based on an existing template, perform the following steps:

1. Go to the Configuration Templates page (Registry > Devices > Templates).

2. In the Configuration Templates page, find the device template you want to use as a template to create a
new device template. Click its wrench icon ( ).
3. In the Device Template Editor page, supply a new value in the Name field.

CAUTION: If you do not enter a new value in the Name field, SL1 will save the new device template under
the same name as the existing device template, but with a different ID number. In some cases,
this could make management of device templates difficult. Best practice is to supply a new name
for the new device template.

4. Edit one or more fields, if desired.

5. Click the [Save As] button.
6. The new device template will appear in the Configuration Templates page.

Editing an Existing Device Template

You can edit an existing device template and change one or more of its parameters.

NOTE: Device templates are not dynamic. That is, when you update or change a device template, no
changes are made to any devices that have used the template in the past.

To edit a device template:

1. Go to the Configuration Templates page (Registry > Devices > Templates).

2. In the Configuration Templates page, find the device template you want to edit. Click its wrench ( )
icon.
3. The Device Template Editor page appears, populated with values from the selected device template.

63 Creating a New Device Template Based on an Existing Device Template

 4. If you see a grayed-out field in a device template, this means that when the template is applied to a device,
the value for that field will not be changed. The device will either retain its current value for that field or will
use the default value for that field. To change the value of a grayed-out field, simply click on the name of the
field and edit the value.
5. In each tab, you can change one or more parameters. For a description of each field, see the previous
sections in this chapter.
6. Click the [Save] button to save your changes to the device template.

Editing an Existing Device Template 64

 Chapter

5
Using Device Templates

Overview
This chapter describes how to use a device template.

Device templates allow you to save a device configuration, apply it to one or more devices, and reuse the same
configuration over and over again.

When you apply a device template to a device group or to selected devices, all the devices in the device group or
all the selected devices will inherit the field values from the device template. Therefore, you will not need to
manually define settings for each device in the affected pages.

You can use a device template in multiple ways:

l You can apply a device template to a device group to automate the configuration of all devices in the
device group.
l From the Device Manager page (Registry > Devices > Device Manager), you can apply a device template
to one or more selected devices to automate the configuration of the selected devices.
l From the Device Groups page (Registry > Devices > Device Groups), you can use the bulk configuration
tool to apply configuration settings to all the devices in a device group. These configuration settings do not
have to be defined or saved in a device template.
l From the Device Manager page (Registry > Devices > Device Manager), you can use the bulk
configuration tool to apply configuration settings to one or more selected devices. These configuration
settings do not have to be defined or saved in a device template.

NOTE: Any policies configured with a device template cannot be removed. The only action available after a
policy is added to a template is editing the policy with the same device template. There is no bulk
action option to add or edit policies, and no way to remove policies using a device template.

65
 Use the following menu options to navigate the SL1 user interface:

l To view a pop-out list of menu options, click the menu icon ( ).

l To view a page containing all of the menu options, click the Advanced menu icon ( ).

This chapter covers the following topics:

Before You Start 66

Using a Device Template to Edit the Configuration of the Devices in a Device Group 66
Using a Configuration Template to Edit the Configuration of One or More Individual Devices 68
Using the Bulk Configuration Tool to Apply Ad Hoc Settings to a Device Group 69
Using the Bulk Configuration Tool to Apply Ad Hoc Settings to One or More Devices 70
Example Device Group and Device Template 71

Before You Start

Before you start creating and working with device templates, consider the following:

l How have you defined device groups? Can you apply a uniform set of configuration settings to all the
devices in a device group?
l Are there multiple devices that require the same set of configuration settings? Could you create a device
template to configure these devices?
l Do most of the devices in a device group require a uniform set of configuration settings, yet there are a few
devices that require a different set of configuration settings? If so, you could create a child device group for
the few devices that require a different set of configuration settings. You could apply one device template to
the parent device group and another device template to the child device group.

Using a Device Template to Edit the Configuration of the

Devices in a Device Group
When you define a device group, you can select one or more devices to include in the device group. These
devices have already been discovered by SL1 and include the default configuration that is applied to a device
when it is initially discovered.

Device groups can also include devices that are automatically added to the device group upon discovery.
These devices also include the default configuration that is applied to a device when it is initially discovered.

You can use a device template to change the configuration of all devices in a device group.

When you apply a device template to a device group, you can avoid manually defining the following for the
member devices:

66 Before You Start

 l Settings in the Device Properties page or the Device Thresholds page.
l Interface monitoring policies.
l Web-content monitoring policies.
l Port monitoring policies.
l Windows service monitoring policies.
l Process monitoring policies.
l Aligning Dynamic Applications, enabling and disabling object collection, and changing thresholds
associated with Dynamic Applications.

All the devices in the device group will inherit the field values from the device template.

NOTE: If the definition for a device group in the Device Group Editor page does not include Config
Policies/Bulk Edit in the Visibility field, you cannot apply a device template to the device group.

To use a device template to change the configuration of all devices in a device group:

1. Go to the Device Groups page (Registry > Devices > Device Groups).
2. In the Device Groups page, find the device group to which you want to apply a device template. Click its
building blocks icon ( ).
3. The Bulk Device Configuration page appears.

l In the Template field, select an existing device template.

l Save When Applied & Confirmed. From the Bulk Device Configuration page, you can edit the
value in any of the fields in any of the tabs of the device template.

o If you select this field, any changes you make to fields in the Bulk Device Configuration page
will be saved to the template.
o If you don't select this field, you can edit the values in any of the fields, and the edited values won't
be saved in the device template, but will be applied to the selected devices.

4. Click the [Apply] button to apply the device template and any changed field values to the device group.
5. The Device Setting Confirmation page appears.

l In this page you can view any settings in the device template that are different from SL1 default
settings.
l You can click a field to disable it. When you disabled a field, its value will not be applied to the
selected device group or selected devices.
l You can also view a list of devices to which the device template will be applied.
6. To approve the changes and the device list, click the [Confirm] button in the Device Setting
Confirmation page.
7. The settings in the device template will be applied to the selected devices in the device group.

Using a Device Template to Edit the Configuration of the Devices in a Device Group 67
Using a Configuration Template to Edit the Configuration of
One or More Individual Devices
You can apply a device template to one or more devices individually, rather than as part of a device group.

When SL1 discovers a device, SL1 applies some default configuration settings to that device. You can edit these
settings or use a device template to edit the settings for one or more devices.

You can use a device template to change the configuration of one or more selected devices.

When you apply a device template to one or more devices, you can avoid manually defining the following for the
devices:

l Settings in the Device Properties page or the Device Thresholds page.

l Interface monitoring policies.
l Web-content monitoring policies.
l Port monitoring policies.
l Windows service monitoring policies.
l Process monitoring policies.
l Aligning Dynamic Applications, enabling and disabling object collection, and changing thresholds
associated with Dynamic Applications.
All the selected devices will inherit the field values from the device template.

To use a device template to change the configuration of one or more devices:

1. Go to the Device Manager page (Registry > Devices > Device Manager).
2. In the Device Manager page, select the checkbox for each device you want to apply a device template to.
3. In the Select Actions field, in the lower right, select the option Modify by Template. Click the [Go] button.
4. The Bulk Device Configuration page appears.

l In the Template field, select an existing device template.

l Save When Applied & Confirmed. From the Bulk Device Configuration page, you can edit the
value in any of the fields in any of the tabs of the device template.

o If you select this field, any changes you make to fields in the Bulk Device Configuration page
will be saved to the template.
o If you don't select this field, you can edit the values in any of the fields, and the edited values won't
be saved in the device template, but will be applied to the device group.

5. Click the [Apply] button to apply the device template and any changed field values to the selected devices.
6. The Device Setting Confirmation page appears.

68 Using a Configuration Template to Edit the Configuration of One or More Individual

 l In this page, you can view any settings in the device template that are different from SL1 default
settings.
l You can click a field to disable it. When you disabled a field, its value will not be applied to the
selected device group or selected devices.
l You can also view a list of devices to which the device template will be applied.
7. To approve the changes and the device list, click the [Confirm] button in the Device Setting
Confirmation page.
8. The device template will be applied to the selected devices.

Using the Bulk Configuration Tool to Apply Ad Hoc Settings to

a Device Group
You can use the bulk configuration tool ( ) in the Device Groups page to apply one or more settings that are
usually defined in a device template to a device group. You can apply settings that are not currently saved in a
device template and then exit the bulk configuration tool without saving the settings as a device template. In
effect, you can manually apply configuration settings to one or more devices, without creating or saving a device
template.

NOTE: If the definition for a device group in the Device Group Editor page does not include Config
Policies/Bulk Edit in the Visibility field, you cannot perform bulk configuration to the device group.

To use the bulk configuration tool to apply settings to a device group:

1. Go to the Device Groups page (Registry > Devices > Device Groups).
2. In the Device Groups page, find the device group to which you want to apply configuration settings. Click
its building blocks icon ( ).
3. The Bulk Device Configuration page appears.

l In the Template field, select New/One-Off Template

l Save When Applied & Confirmed. From the Bulk Device Configuration page, you can edit the
value in any of the fields in any of the tabs of the device template. The edited values will be applied to
the selected device group. You do not have to save the edited values in a device template; they can
be for one-time only use.

o If you select this field, any changes you make to fields in the Bulk Device Configuration page
will be saved to a new template.
o If you don't select this field, you can edit the values in any of the fields, and the edited values won't
be saved in the device template, but will be applied to the device group.

4. Click the [Apply] button to apply the settings to the device group.
5. The Device Setting Confirmation page appears.

Using the Bulk Configuration Tool to Apply Ad Hoc Settings to a Device Group 69
 l In this page, you can view any settings in the device template that are different from SL1 default
settings.
l You can click a field to disable it. When you disabled a field, its value will not be applied to the
selected device group.

l You can also view a list of devices to which the device template will be applied.

6. To approve the changes and the device list, click the [Confirm] button in the Device Setting
Confirmation page.
7. The settings from the Bulk Device Configuration page will be applied to the selected devices in the device
group.

Using the Bulk Configuration Tool to Apply Ad Hoc Settings to

One or More Devices
You can use the Modify by Template action in the Device Manager page to apply one or more settings that are
usually defined in a device template to one or more devices. You can apply settings that are not currently saved in
a device template and then exit the bulk configuration tool without saving the settings as a device template.

To use the Modify by Template action to apply settings to one or more devices:

1. Go to the Device Manager page (Registry > Devices > Device Manager).
2. In the Device Manager page, select the checkbox for each device you want to apply configuration settings
to.
3. In the Select Actions field, in the lower right, select the option Modify by Template.
4. The Bulk Device Configuration page appears.

l In the Template field, select New/One-Off Template

l Save When Applied & Confirmed. From the Bulk Device Configuration page, you can edit the
value in any of the fields in any of the tabs of the device template. The edited values will be applied to
the selected devices. You do not have to save the edited values in a device template; they can be for
one-time only use.

o If you select this field, any changes you make to fields in the Bulk Device Configuration page
will be saved to a new template.
o If you don't select this field, you can edit the values in any of the fields, and the edited values won't
be saved, but will be applied to the selected devices.

5. Click the [Apply] button to apply the field values to the selected device(s).
6. The Device Setting Confirmation page appears.

l In this page, you can view any settings in the device template that are different from SL1 default
settings.

70 Using the Bulk Configuration Tool to Apply Ad Hoc Settings to One or More Devices
 l You can click a field to disable it. When you disabled a field, its value will not be applied to the
selected device group or selected devices.
l You can also view a list of devices to which the device template will be applied.

7. To approve the changes and the device list, click the [Apply] button in the Device Setting Confirmation
page.
8. The settings from the Bulk Device Configuration page will be applied to each selected device.

Example Device Group and Device Template

In this section, we'll create an example device group and an example device template. We'll then apply the device
template to the device group.

Suppose we want to manage all Windows servers running Windows 2000 or later. We will create a device group
that contains those servers.

Suppose we want to create a device template for all Windows servers running Windows 2000 or later. We want
to use a single credential for each Windows server and apply consistent ScienceLogic settings to each server. We
will create a device template for those servers.

Example Device Group

Example Device Group and Device Template 71

 Here is our example device group:

l Title. We named our device group "win2k+_servers".

l Icon. We accepted the default icon.
l Force Child Visibility. We selected "Yes", so that the settings for the device group will apply to any future
child device groups.
l Visibility. We selected all options, so our new device group is visible in all areas of SL1.
l Sharing Permissions. We selected "Shared with users in your organization", so other users can view the use
the device group.
l Permission Keys. We did not select any permission keys for the device group. This means that any user who
has permission to view the Device Groups page and is a member of the same organization as the creator
of the device group can view the device group.
l Add/Remove Devices. We selected four Windows servers to be members of this device group.

Example Configuration Template

Here is our example device template. We defined fields only in the Config tab:

l Template Name. We named our template "win2k+_server_settings".

l Device Organization. We selected the organization "NOC". Each device to which we apply this template
will become a member of that organization.

72 Example Device Group and Device Template

 l SNMP Read. We selected the credential named "EM7 Default V2" as our SNMP Read credential.
l SNMP Write. We did not select a write credential, because we do not need SL1 to write to the devices.
l Availability Protocol. We selected ICMP (ping) as our availability protocol. This means that SL1 will ping a
device to determine its availability.
l Latency Protocol. We selected ICMP (ping) as our latency protocol. This means that SL1 will ping a device
to determine its latency.
l Collection. We selected Enabled, so that SL1 will collect data from the devices that use this template.
l Collector Group. We did not enable this field. When this template is applied, the devices that use this
template will use the existing value for this field or the default value for this field.
l Coll. Type. We selected Standard because our network does not use DHCP.
l Critical Ping. We did not enable this field. When this template is applied, the devices that use this template
will use the existing value for this field or the default value for this field.
l Event Mask. We selected Group in blocks every 1 minute. This means that events that occur on a single
device within a single minute are grouped together under a single description.
l Auto-Clear Events. We enabled this option. Auto Clear automatically removes an event from the Event
Console if a specified succeeding event occurs. For example, suppose the event "Device not responding to
ping" occurs. If the next polling session produces the event "Device now responding normally to ping", the
Auto Clear feature could clear the event.
l Scan All IPs. We did not enable this field. When this template is applied, the devices that use this template
will use the existing value for this field or the default value for this field.
l Accept All Logs. We enabled this option. For each member device, all logs will be saved, not just event
logs.
l Dynamic Discovery. We enabled this option. During discovery, SL1 will automatically assign the
appropriate Dynamic Applications to each device that uses this template.
l Daily Port Scans. We enabled this option. SL1 will perform a daily scan of each member device for open
ports.
l Preserve Hostname. We enabled this option. For each member device, the name of the device will not be
updated in SL1 if the name of the device is changed on the device.
l Auto-Update. We enabled this option. SL1 will perform a nightly discovery of the device and update
records with changes to the device.
l Disable Asset Update. We did not enable this field. When this template is applied, the devices that use this
template will use the existing value for this field or the default value for this field.
l System Latency. We did not enable this field. When this template is applied, the devices that use this
template will use the existing value for this field or the default value for this field.
l Device Logs Max. We did not enable this field. When this template is applied, the devices that use this
template will use the existing value for this field or the default value for this field.
l Log Age Max. We did not enable this field. When this template is applied, the devices that use this template
will use the existing value for this field or the default value for this field.
l Bandwidth Data. We did not enable this field. When this template is applied, the devices that use this
template will use the existing value for this field or the default value for this field.

Example Device Group and Device Template 73

 l Normalized BW Data. We did not enable this field. When this template is applied, the devices that use this
template will use the existing value for this field or the default value for this field.
l Performance Data. We did not enable this field. When this template is applied, the devices that use this
template will use the existing value for this field or the default value for this field.
l Normalized Perf Data. We did not enable this field. When this template is applied, the devices that use this
template will use the existing value for this field or the default value for this field.

74 Example Device Group and Device Template

 Chapter

6
Using Device Group Maps and Views

Overview
This chapter describes views and maps for device groups.

There are three types of views and maps for each device group:

l From the Device Groups page (Registry > Devices > Device Groups), you can view a hierarchical report
on each device group. The Device Group Map page allows you to view devices by device group and also
view the relationships between device groups and child-groups. This makes it easy to visualize and manage
device groups.
l From the Classic Maps (Maps > Classic Maps or the [Views] tab in the classic user interface) you can view
an icon-based view of a device group from the Device Maps > Device Groups view. This page allows you
to easily identify the devices in a device group, sort that list of devices, and quickly determine the status of
each device.
l From the Classic Maps (Maps > Classic Maps or the [Views] tab in the classic user interface), you can also
view a topology-based view of a device group from the Topology Maps view. This view includes all layer-2,
layer-3, CDP, LLDP, and event correlation relationships.

NOTE: If the definition for a device group in the Device Group Editor page does not include Maps/Views in
the Visibility field, SL1 will not create a device group View for the device group.

Use the following menu options to navigate the SL1 user interface:

l To view a pop-out list of menu options, click the menu icon ( ).

l To view a page containing all of the menu options, click the Advanced menu icon ( ).

This chapter covers the following topics:

75
 Viewing the Device Maps for a Device Group 76
Viewing the Device Group Map Page for a Single Device Group 76
Viewing the Classic Views of a Device Group 76
Viewing Custom Device Maps 77
Using the Interface for Device Group Views 77

Viewing the Device Maps for a Device Group

In the Device Group Map page, you can select from a list of device groups and then view a graphical
representation of the selected device group.

To access the Device Group Map page and view a map for any device group:

1. Go to the Device Group Map page (Classic Maps > Device Maps > Device Groups).
2. From the NavBar, select the device group you want to view.
3. The Device Group Map page displays the selected device group. For details on this page, see the section
on Using the Interface for Device Group Views.

Viewing the Device Group Map Page for a Single Device

Group
In the Device Groups page, you can view a hierarchical representation of a selected device group. To access
the Device Group Views page and view a map for a single device group:

1. Go to the Device Groups page (Registry > Devices > Device Groups).
2. In the Device Groups page, find the device group for which you want to view a map and click its map icon (
). The map opens in a new window:
3. The Device Group Views page displays the selected device group. For details on this page, see the section
on Using the Interface for Device Group Views.

Viewing the Classic Views of a Device Group

From the [Views] tab you can view an icon-based view of a device group. This page allows you to easily identify
the devices in a device group, sort that list of devices, and quickly determine the status of each device. To view an
icon-based view of a device group:

1. Go to the Device Group Map page (Classic Maps > Classic Views > Device Groups).
2. The Device Group Views page appears. In the drop-down list in the upper left, select a device group view
to view.

76 Viewing the Device Maps for a Device Group

Viewing Custom Device Maps
From the [Views] tab, you can also view a topology-based view of a device group. This view includes all layer-2,
layer-3, CDP, LLDP, and event correlation relationships.

To view a topology map of a device group:

1. Go to Classic Maps > My Customized Maps and click the name of the device group you want to view.
2. The Custom Device Group Map page appears, where you can view the devices and network relationships
in the device group.

Customized maps appear in the following sections in the left NavBar:

l My Customized Maps. Personalized maps that you create.

l User Customized Maps. If you are a user of type "administrator", you can navigate to the maps in this
section to view and edit all customized maps in SL1, even if the device group associated with the map was
defined with the field Shared (visible to all users) set to no.
l Shared Customized Maps. If a customized map or device group is defined as "shared", you can view the
maps in this section. The maps in Shared Customized Maps require the same Access Hooks and Access
Keys as device groups. Depending upon the Access Keys assigned to your account, you might be able to
edit Shared Customized Maps created by other users. To learn more about Access Hooks and Access Keys,
see the manual Access Permissions..

NOTE: If you create a device group from the Device Groups page and set theVisibility field to include
Maps/Views, the device group will appear as a map in Custom Device Group Map page (Classic
Maps > My Customized Maps). If you set the Shared field to yes, the device group will appear for
other users as a map in the Shared Customized Maps page (Classic Maps > Shared Customized
Maps).

Using the Interface for Device Group Views

When viewing a map of a device group, you can edit the display by using the drag-and-drop editing features and
using the fields in the page. The following sections describe how to use the tools available in the map page.

Drag-and-Drop Editing
A node is a connection point—either a redistribution point or communication endpoint. Each device in the maps
page is an individual node that can be placed in different areas of the map while retaining its link to other
devices. You can drag-and-drop nodes to reposition them on the map to make viewing and managing devices
easier. You can use drag-and-drop editing in the following ways:

Viewing Custom Device Maps 77

 l You can move the entire map around the pane by clicking in any spot in the background, holding down the
left-mouse key and dragging the mouse. The map will be dragged around by the spot you initially clicked
on.
l You can use your mouse to select and move nodes within a map. To edit and move nodes around the map,
first enter Nodes mode by clicking the [Edit: Nodes] button.

Fields and Buttons

The blue navigation bar at the top of a map on the Classic Maps page includes the following:

l Search. Type some or all of a node name in this field to search for specific nodes on the current map.
Nodes that match the search criteria are highlighted in the map. Delete the search text to clear the search.
l [Selections] button( ). After you select one or more nodes, you can click this button to show the details of
that node or nodes in a Details pane to the right of the map. If you have more than one node selected, click
the down arrow icon to select the node for which you want to view the Details pane. You can view the status
for that node and the events associated with that node on the Details pane.

NOTE: The number in the red circle on Selections ( ) shows how many items are currently selected.
If you selected more than one node, use the [Previous] and [Next] buttons at the bottom of
the Details pane to view properties for the other nodes.

NOTE: If you select two device nodes, you can click [Selections] ( ) and select Create Relationship
to create a relationship between those two device nodes in the map.

l [Settings] button ( ). This drop-down contains tabs for nodes, links, map settings, and edit shapes.
l [Reset] button ( ). Click to revert any unsaved changes you have made to your map.
l [Save] button ( ). Click to save any changes you have made to your map.

78 Using the Interface for Device Group Views

 Chapter

7
Scheduling Downtime for a Device Group

Overview
This chapter describes how to schedule maintenance times for device groups.

You can use the Schedule Manager page to schedule downtime for an entire device group. This allows you to
schedule maintenance and update tasks for all the devices in the device group and also inform other users of the
scheduled downtime.

When the scheduled downtime occurs, each device in the device group will have a collection status of
"maintenance".

You can specify whether or not you want SL1 to collect data from the devices in the device group during the
scheduled maintenance. During scheduled maintenance, no events will be triggered for the devices in the device
group.

NOTE: If the definition for a device group in the Device Group Editor page does not include Device
Schedules in the Visibility field, you will not be able to schedule downtime and maintenance for the
device group.

Use the following menu options to navigate the SL1 user interface:

l To view a pop-out list of menu options, click the menu icon ( ).

l To view a page containing all of the menu options, click the Advanced menu icon ( ).

This chapter covers the following topics:

Viewing the Schedule Manager 80

Defining a Scheduled or Recurring Device Group Maintenance Window 80

79
 Enabling or Disabling One or More Scheduled Device Group Maintenance Windows 84
Deleting One or More Scheduled Device Group Maintenance Windows 84

Viewing the Schedule Manager

The Schedule Manager page (Registry > Devices > Device Groups > calendar icon) displays the following
information about each scheduled or recurring device group maintenance window:

l Schedule Summary. Displays the name assigned to the scheduled process.

l Schedule Description. Displays a description of the scheduled process.
l Event ID. Displays a unique, numeric ID for the scheduled process. SL1 automatically creates this ID for
each scheduled process.
l sch id. Displays a unique, numeric ID for the schedule. SL1 automatically creates this ID for each schedule.
l Context. Displays the area of SL1 upon which the schedule works.
l Timezone. Displays the time zone associated with the scheduled process.
l Start Time. Displays the date and time at which the scheduled process will begin.
l Duration. Displays the duration, in minutes, which the scheduled process occurs.
l Recurrence Interval. If applicable, displays the interval at which the scheduled process recurs.
l End Date. If applicable, displays the date and time on which the scheduled process will recur.
l Last Run. If applicable, displays the date and time the scheduled process most recently ran.
l Owner. Displays the username of the owner of the scheduled process.
l Organization. Displays the organization to which the scheduled process is assigned.
l Visibility. Displays the visibility level for the scheduled process. Possible values are "Private", "Organization",
or "World".
l Enabled. Specifies if the scheduled process is enabled. Possible values are "Yes" or "No".

To edit a scheduled or recurring device group maintenance window, click its wrench icon ( ) and update the
settings as needed on the Schedule Editor modal page. (For more information, see the section Defining a
Scheduled or Recurring Device Group Maintenance Window.)

Defining a Scheduled or Recurring Device Group

Maintenance Window
You can schedule a device group maintenance window in SL1 from the Schedule Manager page. SL1 will
automatically set the status of each device in the device group to "maintenance" at the scheduled time.

To define a scheduled or recurring device group maintenance window:

80 Viewing the Schedule Manager

 1. Go to the Schedule Manager page (Registry > Devices > Device Groups > calendar icon).
2. Click [Create]. The Schedule Editor modal appears.
3. On the Schedule Editor modal, make entries in the following fields:
Basic Settings

l Schedule Name. Type a name for the scheduled process.

l Schedule Type. Indicates the scheduled process type (such as Tickets, Reports, or Devices).
l Visibility. Select the visibility for the scheduled process. You can select one of the following:

o Private. The scheduled process is visible only to the owner selected in the Owner field.
o Organization. The scheduled process is visible only to the organization selected in the
Organization field.
o World. The scheduled process is visible to all users.

l Organization. Select the organization to which you want to assign the scheduled process.
l Owner. Select the owner of the scheduled process. The default value is the username of the user who
created the scheduled process.
l Preserve Schedule. Select this checkbox to exclude this schedule from being pruned after expiration.
l Description. Type a description of the scheduled process.

Time Settings

l Start Time. Click in the field and select the date and time you want the scheduled process to start.
l End Time. Click in the field and select the date and time you want the scheduled process to end.
l Time Zone. Select the region or time zone for the scheduled start time.

NOTE: If you want SL1 to automatically adjust for daylight savings time (if applicable), then you must select
a named region (such as America/New York) in the Time Zone field. If you select a specific time
zone (such as EST) or a specific time offset (such as GMT-5), then SL1 will not automatically adjust
for daylight savings time.

l All Day. Select this checkbox if the scheduled process occurs all day rather than during a specific
period of time. If you do so, the End Time field becomes disabled.

Defining a Scheduled or Recurring Device Group Maintenance Window 81

 l Recurrence. Select whether you want the scheduled process to occur once or on a recurring basis.
You can select one of the following:

o None. The scheduled process occurs only once.

o By Interval. The scheduled process recurs at a specific interval.
o Every Xth day of the Week. The scheduled process occurs at a monthly interval based on a day of
the week. The day of the week displayed in this option matched the day selected in the Start Time
field. For example, if you set the Start Time to Thursday, August 5th and that day is the first
Thursday of the month, then the recurrence option will be Every 1st Thursday, and the scheduled
process will occur monthly on the first Thursday of the month.

If you select By Interval, the following additional fields appear:

l Interval. In the first field, enter a number representing the frequency of the scheduled process, then
select the time interval in the second field. Choices are Minutes, Hours, Days, Weeks, or Months. For
example:

o If you specify "6 Hours", then the scheduled process recurs every six hours from the time listed in
the Start Time field.
o If you specify "10 Days", then the scheduled process recurs every 10 days from the date listed in the
Start Time field.
o If you specify "2 Weeks", then the scheduled process recurs every two weeks, on the same day of
the week as the Start Time.
o If you specify "3 Months" the ticket recurs every three months, on the same day of the month as the
Start Time.

l Recur Until. Specifies when the scheduled process stops recurring. You can select one of the
following:

o No Limit. The scheduled process recurs indefinitely until it is disabled.

o Specified Date. The scheduled process recurs until a specific date and time. If you select Specified
Date, you must select a date and time in the Last Recurrence field.

l Last Recurrence. Click in the field and select the date and time you want the scheduled process to
stop recurring.

Action Settings

l Scope. Select if the scheduled maintenance will affect only the group or both the group and children
devices.

82 Defining a Scheduled or Recurring Device Group Maintenance Window

 l Collection Polling. Specifies whether SL1 should perform collection on the device during the
scheduled maintenance. Choices are:

o Enabled. During scheduled maintenance, SL1 will collect data from the device, but no events will
be triggered for the device.
o Disabled. During scheduled maintenance, SL1 will not collect data from the device. No events will
be triggered for the device.

NOTE: If a patch window is set, data collection will continue when a maintenance window
opens and stop only during the patch window instead.

l Patch Window. You can specify a "patch window" within the larger maintenance period. The "patch
window" allows SL1 to limit the suppression of events to a small time-frame within the larger
maintenance window. Your choices are:

o None
o Between 5 minutes and 60 minutes, in five-minute intervals.

For example:

Suppose you have to patch a server that is monitored by SL1. Suppose you know you will perform
this task sometime between midnight and 6:00 AM. Suppose you know that the actual patch
process requires only 15 minutes of downtime for the server. In SL1, you would define a
maintenance window of 24:00 - 6:00 and a patch window of 15 minutes. In this scenario:

1. At 24:00, SL1 generates an event saying that the server is going into maintenance mode. Because
you have defined a patch window, SL1 continues to monitor this server as normal.
2. At 3:00, you apply the patch to the server. The server reboots, and SL1 generates an event saying
that the server is offline. The first event that both matches or exceeds the Patch Maintenance
Minimum Severity in the Behavior Settings page (System > Settings > Behavior) and occurs
within the larger maintenance window triggers the start of the patch window.
3. SL1 suppresses the event that triggered the patch maintenance window and instead generates an
event "Patch Maintenance Window Opened".
4. For the next 15 minutes, SL1 will suppress all events for the device.
5. At 3:15, SL1 will generate an event for "Patch Maintenance Window Closed". This event clears the
previous event "Patch Maintenance Window Opened".
6. SL1 will now generate events for the device, even though the maintenance window extends until
6:00.

NOTE: If the patch was applied at 5:50, the server was rebooted, and SL1 generated an event saying that the
server is offline, events would be suppressed only until the end of the maintenance window, 6:00,
even though the patch window is 15 minutes.

Defining a Scheduled or Recurring Device Group Maintenance Window 83

 4. Click [Save].

Enabling or Disabling One or More Scheduled Device Group

Maintenance Windows
You can enable or disable one or more scheduled or recurring device group maintenance windows from the
Schedule Manager page (Registry > Devices > Device Groups > calendar icon).

NOTE: If you remove a static device from a device group while the device is in maintenance mode, the
device will stay in maintenance mode until you disable it. You must disable the maintenance
schedule on the device itself in the Device Manager (Registry > Devices > Device Manager by
clicking on its calendar ( ) icon. For more information, see the chapter on "Device Maintenance" in
the Device Management manual.

To enable or disable one or more scheduled or recurring device group maintenance windows:

1. Go to the Schedule Manager page (Registry > Devices > Device Groups > calendar icon ).
2. Select the checkbox icon for each scheduled process you want to enable or disable.
3. Click the Select Action menu and choose Enable Schedules or Disable Schedules.
4. Click the [Go] button.

Deleting One or More Scheduled Device Group Maintenance

Windows
You can delete one or more scheduled or recurring device group maintenance windows from the Schedule
Manager page (Registry > Devices > Device Groups > calendar icon). To do this:

1. Go to the Schedule Manager page (Registry > Devices > Device Groups > calendar icon).
2. Select the checkbox icon for each scheduled process you want to delete.
3. Click the Select Action menu and choose Delete Schedules.
4. Click the [Go] button.

84 Enabling or Disabling One or More Scheduled Device Group Maintenance Windows

 Chapter

8
Events and Device Groups

Overview
This chapter describes how to suppress an event for a device group.

Events are messages that are triggered when a specific condition is met. For example, an event can signal a
server has gone down, that a device is exceeding CPU or disk-space thresholds, that communication with a
device has failed, or simply display the status of a managed element.

Events are displayed in the [Events] tab in SL1, in the Event Console page. When you suppress an event, you
are specifying that in the future, if this event occurs again on the same device, the event will not appear in the
Event Console page. Basically, you are saying that if the event occurs again on the same device, you do not
want to be notified.

If a suppressed event occurs on a different device, it will appear in the Event Console page.

You can suppress an event for a device group. The event will then be suppressed for all devices in the device
group. The event will also be suppressed for all child device groups and their devices.

NOTE: For general details on events, see the manual Events.

Use the following menu options to navigate the SL1 user interface:

l To view a pop-out list of menu options, click the menu icon ( ).

l To view a page containing all of the menu options, click the Advanced menu icon ( ).

This chapter covers the following topics:

Searching Events by Device Group 86

85
 Suppressing an Event for a Device Group 87

Searching Events by Device Group

Events are messages that are triggered when a specific condition is met. For example, an event can signal a
server has gone down, that a device is exceeding CPU or disk-space thresholds, that communication with a
device has failed, or simply display the status of a managed element.

Events are displayed in the [Events] tab in SL1, in the Event Console page. In the Event Console page you can
search for Device Group Names and Device Group IDs to find events that occurred on devices that are members
of the specified Device Group.

The Global Search field in the upper left of the page allows you to filter the entire list of displayed events by a
single parameter. SL1 will update the Event Console and display only events that have a matching parameter.

To use the Global Search field, enter values in the Search drop-down list and the Text field:

l Search. You can select from a number of parameters, that include:

o Device Group ID. Unique ID for the device group associated with the event.
o Device Group Name. Name of the device group associated with the event.

l Text. For each search parameter, you must enter text to match against. SL1 will search for events that match
the text, including partial matches. Text matches are not case-sensitive. You can use the following special
characters in each filter:

o , (comma). Specifies an "or" operation. For example:

"dell, micro" would match all values that contain the string "dell" OR the string "micro".

o & (ampersand). Specifies an "and" operation. For example:

"dell & micro" would match all values that contain the string "dell" AND the string "micro".

o ! (exclamation mark). Specifies a "not" operation. For example:

"!dell" would match all values that do not contain the string "dell".

To perform another search on the results of the previous search:

1. Click the plus sign ( ) to the left of the Refresh Timer.

2. This adds another Search field and Text field to the top of the page. This second search will search only the
results from the first search.
3. You can add as many Search and Text fields as you need.

86 Searching Events by Device Group

 NOTE: You can save the results of a Global Search as a Custom View.

Suppressing an Event for a Device Group

You can suppress an event for a device group. When you do so, you are suppressing the event for all devices in
the device group (and optionally, any child device groups).

NOTE: If the definition for a device group, in the Device Group Editor page, does not include Event
Suppression in the Visibility field, you will not be able to suppress an event for the device group.

To suppress an event for a device group:

1. Go to the Event Policy Manager page (Registry > Events > Event Manager).

2. In the Event Policy Manager page, find the event you want to suppress. Click its wrench icon ( ).
3. When the Event Policy Editor page appears, select the [Suppressions] tab.
4. In the [Suppressions] tab, you can define or edit the following:
l Available Device Groups. Device groups for which you can suppress the event.
l Suppressed Device Groups. Device groups for which the event is already suppressed.
5. You can use the arrow buttons ([<<] and [>>]) to move device groups from the Available and Suppressed
lists.
6. Click the [Save] button to save your suppressions.

Suppressing an Event for a Device Group 87

 Chapter

9
Automation Policies and Tickets

Overview
This chapter describes how to use run book automation and action policies with device groups in SL1.

SL1 includes automation features that allow you define specific conditions and the actions you want SL1 to
execute when those conditions are met. These features can be found in the Registry > Run Book pages. (For more
details on automation policies and action policies, see the manual Run Book Automation.)

SL1 also allows you to align a ticket with a device group when creating a ticket. You can align a ticket with a
device group from the Ticket Console page.

Use the following menu options to navigate the SL1 user interface:

l To view a pop-out list of menu options, click the menu icon ( ).

l To view a page containing all of the menu options, click the Advanced menu icon ( ).

This chapter covers the following topics:

What is an Automation Policy? 89

Aligning an Automation Policy with a Device Group 89
What is an Action Policy? 90
Aligning a Ticket with a Device Group 91
Searching for a Ticket Aligned with a Device Group 91

88
What is an Automation Policy?
An automation policy allows you to define automatic actions that should be executed in response to events. The
automation policy defines the conditions under which an automatic action should be executed.

When the criteria in an automation policy is met, an action is executed. This action is defined in an action policy.
To view a list of action policies or edit or create an action policy, go to the Action Policy Manager page
(Registry > Run Book > Actions).

For example, an automation policy might specify: If the event "illicit process" occurs on all the devices in device
group "mailservers", and the event is not cleared within five minutes, execute the action policy "email NOC". The
action policy "email NOC" could email all NOC staff about the "illicit process" event.

Automation policies can describe the criteria described below. One or more of these criteria must be met before
an action is executed:

l One or more specified events must have occurred.

l Events must have occurred on one or more specified devices or all devices in one or more specified
device groups.
l Event(s) must have specified severity (critical, major, minor, notice, or healthy).
l Events must have specified status (event is not cleared, event is now acknowledged, ticket is not created for
event).
l Specific amount of time that must elapse while severity and status do not change.

When the criteria are met, the automation policy triggers the execution of one or more specified action policies.

Aligning an Automation Policy with a Device Group

When you align an automation policy with a device group, you specify that all the conditions in the automation
policy must occur on at least one device in that device group before an action policy is executed. This is quicker
and easier than manually selecting individual devices.

When you align a device group with an automation policy, all the devices in the device group and all child device
groups and their devices are included in the automation policy.

To align an automation policy with a device group, perform the following:

NOTE: If the definition for a device group in the Device Group Editor page does not include
Notification/Automation in the Visibility field, you will not be able to align an automation policy with
the device group. Instead, you will have to manually select each device in the device group.

89 What is an Automation Policy?

 1. Go to the Automation Policy Manager page (Registry > Run Book > Automation).
2. In the Automation Policy Manager page, you can:

l Edit an existing automation policy. To do so, find the policy you want to edit and click its wrench icon
( ).
l Create a new automation policy. To do so, click the [Create] button.

3. When the Automation Policy Editor page appears, you can use the following fields to align the
automation policy with a device group:

l Align With. Specifies whether to align this automation policy with one or more devices or one or
more device groups.
l Available Device Groups. If you selected Device Groups in the Align With field, this field displays a
list of all device groups in SL1. You can select one or more device groups in this field. The selected
event(s) and event criteria must occur on each selected device in each selected device group before
the automation policy will be executed. To select a device group, highlight it and click the right-arrow
button (>>).
l Aligned Device Groups. This pane displays a list of all device groups aligned with this automation
policy. To deselect a device group, highlight it and click the left-arrow button (<<).

What is an Action Policy?

An action policy is an action that can be automatically triggered in SL1 when certain criteria are met. The
triggers are defined in an automation policy in the Automation Policy Manager page (Registry > Run Book >
Automation).

An action policy can perform one of the following tasks:

l Send an email message to a pre-defined list of users.

l Send an SNMP trap from SL1 to an external device.
l Create a new ticket (using ticket templates defined in Ticket Templates page [Registry > Ticketing >
Templates])
l Update an existing ticket. An action policy can change the status and/or severity of an existing ticket and/or
add a note to an existing ticket. For this action policy to trigger successfully, a ticket must be associated with
the event that triggered the action.
l Write an SNMP value to an existing SNMP object on an external device.
l Query a database.
l Run a custom python script, called a snippet.
l Write an SNMP value to an existing SNMP object on an external device.

To create an action policy, go to the Action Policy Manager page (Registry > Run Book > Actions) and click the
[Create] button.

What is an Action Policy? 90

Aligning a Ticket with a Device Group
A ticket is a request for work. This request can be in response to a problem that needs to be fixed, for routine
maintenance, or for any type of work required by your enterprise. When creating a ticket you can align that ticket
with a device group. To align a ticket with a device group:

1. Go to the Ticket Console page ([Tickets] tab).

2. In the Ticket Console page, click the [Create] button.
3. The Ticket Editor page appears. In the Ticket Editor page, the Element field allows you to select the
element where the problem occurred. To select a device group, click the binoculars ( ) to the right of the
field.
4. The Finder page appears, where you can select the device group to align with the ticket.
5. To search for a device group, select the Device Group checkbox. To exclude an element from the search,
unselect its checkbox.
6. In the Search field you can also enter a whole or partial string of text for the device group you want to find.
7. Click the [Search] button.
8. Click on the device group to align the device group to the ticket.

Searching for a Ticket Aligned with a Device Group

In the Ticket Console page you can search for existing tickets aligned with a device group. The Ticket Console
page contains "filter-while-you-type" fields at the top of the page that allow you to filter the list of tickets by one
more parameters. To search for a ticket aligned with a device group:

1. Go to the Ticket Console page ([Tickets] tab). In the Ticket Console page, the Element Name field allows
you to search for device groups aligned with a ticket.
2. Enter a full or partial search string in the Element Name field. The list of tickets will be filtered to display the
element(s) that meet your search criteria.
3. You can access the Device Group Editor page for each ticket aligned with a device group by selecting its
device icon ( ) in the Element field. For more information on device groups, see the section on Creating
and Editing Device Groups.
For more information on tickets, see the manual Ticketing.

91 Aligning a Ticket with a Device Group

 Chapter

10
Assigning Device Groups and Applying Device
Templates During Discovery

Overview
This chapter describes how to assign device groups and apply device templates during discovery.

Use the following menu options to navigate the SL1 user interface:

l To view a pop-out list of menu options, click the menu icon ( ).

l To view a page containing all of the menu options, click the Advanced menu icon ( ).

This chapter covers the following topics:

What is Discovery? 92
Assigning Devices to a Device Group During Discovery 93
Applying a Device Template to Devices During Discovery 94

What is Discovery?
Discovery is the process by which SL1 retrieves data from the devices and applications in the network. SL1 runs
discovery to perform the initial discovery of your network and then nightly to collect and update information about
your network. You can also manually initiate discovery for a single device, one or more device groups, or for the
whole network, at any time.

SL1's Discovery tool automatically finds all the devices and components in your network. You must provide the
Discovery tool with one or more IP addresses, and SL1 then finds all the devices and components in the IP range.
For each discovered device or component, SL1 gathers detailed data. This data is used throughout SL1.

What is Discovery? 92
 In SL1, discovery includes two steps: Identification followed by Modeling.

l During the initial identification step, SL1 divides and distributes the list of IPs among the collection processes
running on the Data Collectors in a collector group. Each collection process works independently to
discover each device and determine the device name, hostname, MAC address, and IP address of each
discovered device.
l After each device has been discovered, the modeling phase beings. During the modeling phase, SL1
generates a unique identifier for each new device, assigns the device to a Device Class and a Device
Category, and optionally can assign each device to a specific Device Group and optionally can
apply a device template to each device. SL1 then reexamines each device in-depth, to align monitoring
and collection tasks that correlate to the device type and the applications running on the device. SL1 then
uses the appropriate Dynamic Applications to retrieve detailed configuration and performance data from
the device.

During discovery, SL1 can gather the following types of information:

l For each device, performs detailed modeling of hardware, operating systems, applications, process, and
services.
l Detects open network ports and generates alerts when illicit ports are found open.
l Recognizes and classifies all IANA interface types.
l Detects and models layer-2 and layer-3 networks.
l Maps and models virtual infrastructure, including VMware ESX servers and their guest operating systems.
l Automatically catalogs all discovered IP addresses, and categorizes IP networks and subnets.

Assigning Devices to a Device Group During Discovery

During discovery, you can specify that each device discovered during the discovery session be assigned to a
selected device group. You can then configure and manage the devices as a device group, as described in the
previous chapters of this manual.

NOTE: If the definition for a device group in the Device Group Editor page does not include Discovery in
the Visibility field, you will not be able to automatically add all discovered devices to the device
group. The device group will not appear in the list of device groups in the Discovery Control Panel
page.

To automatically assign devices to a device group during discovery:

1. Go to the Discovery Control Panel (System > Manage > Classic Discovery).
2. The Discovery Control Panel page appears.
3. Click the [Create] button to bring up the Discovery Session Editor modal page.
4. In the editor pane, enter values in each field. For more information on discovery, see the manual on
Discovery and Credentials.
5. To assign devices from this discovery session to a selected device group, use the following field:

93 Assigning Devices to a Device Group During Discovery

 l Add Devices to Device Group(s). As SL1 discovers a device in the IP discovery list, that device is
added to each selected device group. You can select one or more device groups from a list of device
groups in SL1 that have "Discovery" selected in the Visibility field.

NOTE: A single device can be a member of multiple device groups.

6. Click the [Save] button to save your discovery settings. If no other discovery sessions are currently running,
the session will be executed immediately. If another discovery session is currently running, this session will be
queued.

Applying a Device Template to Devices During Discovery

During discovery, you can specify that a device template be applied to each device discovered during the
discovery session. Normally, these devices would be automatically configured with ScienceLogic's default
settings. When you specify a device template, these devices are automatically configured with the settings
specified in the device template.

To automatically apply a device template to devices during discovery:

1. Go to the Discovery Control Panel page (System > Manage > Classic Discovery).
2. Click the [Create] button to bring up the Discovery Session Editor modal page.
3. In the editor pane, enter values in each field. For more information on discovery, see the manual on
Discovery and Credentials.
4. To apply a device template to all devices from this discovery session, use the following drop-down list:

l Apply Device Template. As SL1 discovers a device in the IP discovery list, that device is configured
with the selected device template. You can select from a list of all device templates in SL1.
5. Click the [Save] button to save your discovery settings. If no other discovery sessions are currently running,
the session is executed immediately. If another discovery session is currently running, this session is queued.

Applying a Device Template to Devices During Discovery 94

© 2003 - 2023, ScienceLogic, Inc.
All rights reserved.
LIMITATION OF LIABILITY AND GENERAL DISCLAIMER
ALL INFORMATION AVAILABLE IN THIS GUIDE IS PROVIDED "AS IS," WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESS OR IMPLIED. SCIENCELOGIC™ AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT.
Although ScienceLogic™ has attempted to provide accurate information on this Site, information on this Site
may contain inadvertent technical inaccuracies or typographical errors, and ScienceLogic™ assumes no
responsibility for the accuracy of the information. Information may be changed or updated without notice.
ScienceLogic™ may also make improvements and / or changes in the products or services described in this
Site at any time without notice.

Copyrights and Trademarks

ScienceLogic, the ScienceLogic logo, and EM7 are trademarks of ScienceLogic, Inc. in the United States,
other countries, or both.
Below is a list of trademarks and service marks that should be credited to ScienceLogic, Inc. The ® and ™
symbols reflect the trademark registration status in the U.S. Patent and Trademark Office and may not be
appropriate for materials to be distributed outside the United States.
l ScienceLogic™
l EM7™ and em7™
l Simplify IT™
l Dynamic Application™
l Relational Infrastructure Management™
The absence of a product or service name, slogan or logo from this list does not constitute a waiver of
ScienceLogic’s trademark or other intellectual property rights concerning that name, slogan, or logo.
Please note that laws concerning use of trademarks or product names vary by country. Always consult a
local attorney for additional guidance.

Other
If any provision of this agreement shall be unlawful, void, or for any reason unenforceable, then that
provision shall be deemed severable from this agreement and shall not affect the validity and enforceability
of any remaining provisions. This is the entire agreement between the parties relating to the matters
contained herein.
In the U.S. and other jurisdictions, trademark owners have a duty to police the use of their marks. Therefore,
if you become aware of any improper use of ScienceLogic Trademarks, including infringement or
counterfeiting by third parties, report them to Science Logic’s legal department immediately. Report as much
detail as possible about the misuse, including the name of the party, contact information, and copies or
photographs of the potential misuse to: [email protected]. For more information, see
https://sciencelogic.com/company/legal.
800-SCI-LOGIC (1-800-724-5644)

International: +1-703-354-1010