This manual describes how a service provider might configure SL1 to offer their customers a managed service for the devices that are hosted by the provider or on a customer site. In this example, there are three initial configuration steps:
Creating Product SKUs
Creating Device Templates
Creating User Policies
After performing the initial configuration, you can provision a new customer by:
Creating an Organization record.
Aligning Product SKUs to the Organization record.
Creating and running a Discovery Session that includes the appropriate device template.
Creating a user account for the customer.
Navigation tips for the SL1 user interface:
To access a list of menu options, click the menu icon ().
To view a page containing all of the menu options, click the Advanced menu icon ().
This section covers the following topics:
Levels of Service
In this example, customers will be offered three tiers of service:
Bronze, which includes the availability and latency monitoring that SL1 automatically performs for every device.
Silver, which includes additional monitoring capabilities, including CPU, physical memory, file system and interface statistics collection.
Gold, which includes more frequent Interface statistics collection and additional, device/application specific, collection. For example, gold-level monitoring for an Apache Web Server might include:
Port monitoring policies for ports 80 and 443.
A web content verification policy.
A system process monitoring policy for the "httpd" process.
Steps to Configure the Tiered Service
This manual describes the following steps for creating and offering the example service:
Creating Product SKUs. In SL1, product SKUs are used to track the products and services that are associated with the devices, organizations, interfaces, and assets in the system. In this example, a product SKU is created for each type of device for each level of service. For example, this example includes a product SKU for "Gold Level Apache/Linux Server Monitoring". When a new customer is provisioned, the product SKUs for the services that they subscribed to are manually aligned with that customer's organization record.
Creating Device Templates. In SL1, device templates are used to save a set of parameters for monitoring a device. For example, a device template can specify the availability protocol, interface monitoring settings, and device/application-specific monitoring settings for a device. The device template can then be used to reconfigure multiple devices or device groups, or to specify the initial configuration for all devices discovered using a specific discovery session. In this example, a device template is configured for each type of device for each level of service. For example, this example includes a device template for "Gold Level Apache/Linux Web Servers". When a new customer is provisioned, the appropriate device template is selected in the discovery session(s) that will discover that customer's devices. If you select a device template in a discovery session, all monitoring settings in the device template are automatically applied to each discovered device.
Creating User Policies. In SL1, user policies allow you to define a set of user account properties and permissions to re-use for multiple user accounts. When you create a user account, you can use a user policy to quickly apply settings to the new user account. User policies have a dynamic relationship with their member user accounts. When you make a change to a user policy, the user accounts associated with that user policy are automatically updated. In this example, a single user policy is defined that grants customer-level access to the system. When a new customer is provisioned, the user policy is used to create a user account for the new customer.
Provisioning a New Customer. The following provisioning process is used in this example:
An organization is created for the customer.
The product SKUs for the services the customer subscribed to are aligned with the organization. Because each product SKU in this example specifies a service level and a type of device, a customer could subscribe to a different service level for each type of device. For example, a customer might subscribe to gold service for their MySQL Database Servers and silver service for their Apache/Linux Web Servers.
A discovery session is created for each type of customer device. For example, one discovery session that includes all the customer's Apache Web Servers, one discovery session that includes all the customer's MySQL Database Servers, etc. The appropriate device template is selected based on the product SKU's listed in the customer's organization record.
A user account is created for the customer. The pre-configured user policy is used to create the user account.
This manual describes how to provision devices manually. You could configure an automatic provisioning process using the ScienceLogic API.