Example of a Database Performance Dynamic Application

Download this manual as a PDF file

In this section, we will walk through a Dynamic Application that monitors the performance of a MySQL database.

The MySQL DB Performance Dynamic Application makes multiple queries to an internal table in MySQL. This internal table stores status information about the MySQL server, such as number of connections, information about index scans, information about pages in the buffer pool, reads and writes to key blocks, number of open files, information on the query cache, number of slow queries, information about table locks, and information about threads.

The MySQL DB Performance Dynamic Application includes presentation objects, threshold objects, and alert definitions that allow you to monitor the status of a MySQL server.

In this section, we have aligned the Dynamic Application with the Database Server. The Database Server uses a MySQL database.

NOTE: The MySQL DB Performance Dynamic Application includes multiple Collection Objects, Presentation Objects, Threshold Objects, and Alerts. This section will walk you though only two of each type of object.

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

  • To view a pop-out list of menu options, click the menu icon ().
  • To view a page containing all of the menu options, click the Advanced menu icon ().

Defining the Basic Properties for the Dynamic Application

To create the container for this Dynamic Application and define its general properties, perform the following:

NOTE: For details on each field and its possible options, see the section on Creating Dynamic Applications.

  1. Go to the Dynamic Applications Manager page (System > Manage > Applications).
  2. Click the Actions button, and then select Create New Dynamic Application. The Dynamic Applications Create New Application page appears.
  3. Supply values in the following fields:
  • Application Name. Enter MySQL:DBPerformance.
  • Application Type. The protocol SL1 will use and the type of data that will be collected. Select Database Performance.
  • Version Number. Accept the default value. You can customize this value and increment it according to your change-management policies.
  • Operational State. Specifies whether SL1 will collect data from devices using this Dynamic Application. This field also specifies whether SL1 will automatically align this Dynamic Application to devices during discovery, re-discovery, and nightly auto-discovery. Select Enabled.
  • Poll Frequency. Frequency at which SL1 will poll devices that use this Dynamic Application. Select "Every 5 Minutes", so we can quickly view retrieved data in this example.
  • Abandon Collection. Accept the default value. Specifies how many collection objects must be unavailable before the Dynamic Application should stop trying to collect data and wait until the next scheduled collection session. Default specifies a threshold of two collection objects.

NOTE: For all objects except those retrieved from a database, the timeout limit is specified in the credential. For database objects, the timeout limit is specified internally by SL1.

  • Context. Leave this field blank.

  1. Click the Save button to save the Dynamic Application.

Defining the Discovery Object for the Dynamic Application

A discovery object is a type of collection object. If you want SL1 to automatically align devices with a Dynamic Application during discovery, you must include a discovery object in that Dynamic Application.

NOTE: For more details on discovery objects, see the section on Collection Objects.

To create a discovery object for the Dynamic Application MySQL:DBPerformance, we will write a query that will return a value only if MySQL is running on a device.

To create the discovery object:

  1. Go to the Dynamic Applications Manager page System > Manage > Applications).
  2. Click the wrench icon ( ) for the Dynamic Application named MySQL:DBPerformance.
  3. Click the Collections tab. The Dynamic Applications | Collections Objects page (System > Manage > Applications > Collections) appears.
  4. Supply values in the following fields:
  • Object Name. Enter Discovery Object.
  • SQL Query. This field specifies the query that SL1 will use to collect the discovery object. We will query a value that indicates that a MySQL database exists, regardless of the status of the data in the database. Enter the following query:

show global status like 'Connections'

  • This query searches an internal table that stores information about all connections to the MySQL database (show global status).
  • The query retrieves the value of the status variable "Connections" (like 'Connections').
  • The variable "Connections" contains the number of connection attempts (successful or not) to the MySQL server. The value can be zero ("0") or greater.
  • This query will return a value even if no connections have been made previously.
  • Class Type. Select [100] Discovery.
  1. Click the Save button to save the collection object. Because this collection object has been defined with a Class Type of [100] Discovery, the user interface displays additional fields that are specific to discovery objects.
  2. Enter values in the following fields:
  • Alignment Condition. Specifies how this discovery object should be evaluated. Select Align if OID is present. This choice tells SL1 to automatically align the Dynamic Application with each device that returns a value for the query in the SQL Query field.
  • Validity Check. Leave blank.

Defining the Collection Objects

The MySQL:DBPerformance Dynamic Application on the ScienceLogic Support Site includes 27 Collection Objects. This section will walk you through the creation of only two collection objects.

NOTE: For more details on collection objects, see the section on Collection Objects.

In this section, we will create the following collection objects:

  • Key_reads. This collection object monitors the MySQL status variable key_reads. This status variable specifies the number of times MySQL had to access the file system (instead of the key cache) to fetch database indexes. If key_reads is large, then the key buffer is probably too small.
  • Key_read_requests. This collection object monitors the MySQL status variable key_read_requests. This status variable specifies the total number of requests to read a key block from the cache.

If MySQL must fetch database indexes from the filesystem, queries to that database will be slower than usual. If your MySQL server must frequently fetch database indexes from the filesystem, you should increase the size of the key buffer.

To create these two collection objects, perform the following:

  1. Go to the Dynamic Applications Manager page (System > Manage > Applications).
  2. Click the wrench icon ( ) for the Dynamic Application named MySQL:DBPerformance.
  3. Click the Collections tab. The Dynamic Applications | Collections Objects page (System > Manage > Applications > Collections) appears.
  4. First, we will define the Key_reads collection object. This collection object monitors the MySQL status variable key_reads. This status variable specifies the number of times MySQL had to access the file system (instead of the key cache) to fetch database indexes.
  5. Supply values in the following fields:
  • Object Name. Enter Key_reads.

  • SQL Query. Enter the following:

show global status like 'Key_reads'

  • This query searches an internal table that stores information about the MySQL server (show global status).
  • The query retrieves the value of the status variable "Key reads" (like 'Key_reads').
  • The variable Key_reads contains the number of times MySQL had to access the file system (instead of the key cache) to fetch database indexes.

  • Class Type. Select 1 Performance Counter.
  • Group Number. Select No Group, and leave the second drop-down as Standard.
  • Trended Column. Enter Value. The query returns two columns: Variable_name, which contains the name of the variable (Key_reads) and Value, which contains the value of the variable. We are interested only in the value in the Value column. We want SL1 to graph the value from the Value column.
  • Enable Deviation Alerting. Do not select these checkboxes.
  • Description. Leave blank.
  • Formula. Leave blank.
  1. Click the Save button to save the new collection object.
  2. Next, we will define the Key_read_requests collection objects. This collection object monitors the MySQL status variable key_read_requests. This status variable specifies the total number of requests to read a key block from the cache.
  3. Supply values in the following fields:
  • Object Name. Enter Key_read_requests.

  • SQL Query. Enter the following:

show global status like 'Key_read_requests'

  • This query searches an internal table that stores information about the MySQL server (show global status).
  • The query retrieves the value of the status variable "Key_read_requests" (like 'Key_read_requests').
  • The variable Key_read_requests contains the total number of requests to read a key block from the cache.

  • Class Type. Select 1 Performance Counter.
  • Group Number. Select No Group, and leave the second drop-down as Standard.
  • Trended Column. Enter Value. The query returns two columns: Variable_name, which contains the name of the variable (Key_read_requests) and Value, which contains the value of the variable. We are interested only in the value in the Value column. We want SL1 to graph the value from the Value column.
  • Enable Deviation Alerting. Do not select these checkboxes.
  • Description. Leave blank.
  • Formula. Leave blank.
  1. Click the Save button to save the new collection object.
  2. In our example, you will notice that the collection objects have the following object IDs:
  • Key_reads = o_5500
  • Key_read_requests = o_5501

NOTE: On your SL1 system, the collection objects will have different object IDs. Whether your have imported the Dynamic Application or are creating the Dynamic Application from the steps in this chapter, the collection objects will have different object IDs than on our example SL1 system.

Defining the Presentation Objects

Presentation objects allow you to define how SL1 should use the values collected by the Dynamic Application to create performance graphs.

NOTE: For more details on presentation objects, see the section on Presentation Objects.

The MySQL:DBPerformance Dynamic Application on the ScienceLogic Support Site includes 33 Presentation Objects. This section will walk you through the creation of only two presentation objects.

In this section, we will create the following presentation objects:

  • Key_reads. Displays the value of the Key_reads collection object, over time. The Key_reads collection object specifies the number of times MySQL had to access the file system (instead of the key cache) to fetch database indexes. If the value of the Key_reads collection object is large, then the key buffer is probably too small. The Key_reads presentation object will graph each collected value of the Key_reads collection object and its associated date and time.
  • Key_read_requests. Displays the value of the Key_read_requests collection object, over time. The Key_read_requests collection object specifies the total number of requests to read a key block from the cache. The Key_read_requests presentation object will graph each collected value of the Key_read_requests collection object and its associated date and time.

To create these two presentation objects, perform the following:

  1. Go to the Dynamic Applications Manager page (System > Manage > Applications).
  2. Click the wrench icon ( ) for the Dynamic Application named MySQL:DBPerformance.
  3. Click the Presentations tab. The Dynamic Applications Presentation Objects page appears.
  4. First, we will define the Key_reads presentation object. The Key_reads presentation object will graph each collected value of the Key_reads collection object and its associated date and time.
  5. Supply values in the following fields:
  • Report Name. Enter Key_reads. This name will appear in the NavBar of the Performance page for each device that subscribes to the Dynamic Application. This name will also appear as a title for the graph.
  • Active State. Select Enabled. SL1 will immediately create the graph at the next polling session.
  • Data Unit. Leave blank.
  • Abbreviation/Suffix. Leave blank.
  • Show as Percent. Select No.
  • Vitals Link. Select Disabled.
  • Formula Editor. Enter the following: (o_5500)
  • This formula tells SL1 to graph each value of the collection object o_5500. In our example system, this is the object ID for the Key_reads collection object. SL1 will graph each value of this collection object, along with its associated date and time.

NOTE: The object ID for the Key_reads collection object will be different on your SL1 system. If you are creating a new Dynamic Application using the instructions in this chapter, please enter the object ID for the Key_reads collection object, as it appears on your SL1 system.

  1. Click the Save button to save the new presentation object.
  2. Next, we will define the Key_read_requests presentation object. The Key_read_requests presentation object will graph each collected value of the Key_read_requests collection object and its associated date and time.
  3. Supply values in the following fields:
  • Report Name. Enter Key_read_requests. This name will appear in the NavBar of the Performance page for each device that subscribes to the Dynamic Application. This name will also appear as a title for the graph.
  • Active State. Select Enabled. SL1 will immediately create the graph at the next polling session.
  • Data Unit. Leave blank.
  • Abbreviation/Suffix. Leave blank.
  • Show as Percent. Select No.
  • Vitals Link. Select Disabled.
  • Formula Editor. Enter the following: (o_5501)
  • This formula tells SL1 to graph each value of the collection object o_5501. On our example SL1 system, this is the object ID for the Key_read_requests collection object. SL1 will graph each value of this collection object, along with its associated date and time.

NOTE: The object ID for the Key_read_requests collection object will be different on your SL1 system. If you are creating a new Dynamic Application using the instructions in this chapter, please enter the object ID for the Key_read_requests collection object, as it appears on your SL1 system.

  1. Click the Save button to save the new presentation object.

Defining the Threshold Objects

A threshold object is an object that you can use in the formula for an alert definition or a presentation object, just as you would use a collection object.

Threshold objects can also appear as thresholds in the Device Thresholds page (Devices > Classic Devices > wrench icon > Thresholds, or Registry > Devices > Device Manager > wrench icon > Thresholds in the classic SL1 user interface )for each device that subscribes to the Dynamic Application.

NOTE: For more details on threshold objects, see the section on Alerts and Thresholds.

The MySQL:DBPerformance Dynamic Application on the ScienceLogic Support Site includes seven threshold objects. This section will walk you through the creation of only one threshold object.

  • Keycache_hitrate. We will use this threshold in the formula for two alerts. The initial alert is triggered when MySQL fetches database indexes from the filesystem instead of from the key cache. This threshold defines the percentage of fetches that can be from the filesystem instead of from the key cache before SL1 generates an alert.

To create this threshold object, perform the following:

  1. Go to the System > Manage > Applications page (System > Manage > Applications).
  2.  Click the wrench icon ( ) for the Dynamic Application named MySQL:DBPerformance
  3. Click the Thresholds tab. The Dynamic Applications Threshold Objects page appears.
  4. Supply values in the following fields:
  • Threshold Name. Enter Keycache_hitrate.
  • Override Threshold Value. Select Enabled. This threshold will appear in the the Device Thresholds page (Devices > Classic Devices > wrench icon > Thresholds, or Registry > Devices > Device Manager > wrench icon > Thresholds in the classic SL1 user interfacefor devices that subscribe to the Dynamic Application.
  • Numeric Range: High. Enter 100. By default, the highest possible value for this threshold will be "100". This value will appear at the high end of the slider in the the Device Thresholds page (Devices > Classic Devices > wrench icon > Thresholds, or Registry > Devices > Device Manager > wrench icon > Thresholds in the classic SL1 user interface.
  • Numeric Range: Low. Enter 0. By default, the lowest possible value for this threshold will be "0". This value will appear at the low end of the slider in the the Device Thresholds page (Devices > Classic Devices > wrench icon > Thresholds, or Registry > Devices > Device Manager > wrench icon > Thresholds in the classic SL1 user interface.
  • Threshold Type. Select Percentage.
  • Threshold Value. Enter 99.
  1. Click the Save button to save the new threshold.
  1. If you imported the Dynamic Application from the ScienceLogic Support Site, you will notice that the threshold object has the following object ID:
  • Keycache_hitrate = t_130

NOTE: On your SL1 system, the threshold object will have different object IDs. Whether your have imported the Dynamic Application or are creating the Dynamic Application from the steps in this chapter, the collection objects will have different object IDs than on our example SL1 system.

Defining the Alerts

Alerts allow you to examine and manipulate values retrieved by a Dynamic Application. An alert defines the conditions during which you would like SL1 to insert a message in the device log. You can define events that are triggered when the alert message appears in a device log.

NOTE: For details on alerts, see the section on Alerts and Thresholds.

The MySQL:DBPerformance Dynamic Application on the ScienceLogic Support Site includes 14 alerts. This section will walk you through the creation of only two alerts.

In this section, we will create the following alerts:

  • MySQL:Keycache_hitrate_low. This alert compares the value of the Key_reads collection object to the value of the Key_read_requests collection object. Remember that the Key_reads collection object specifies the number of times the MySQL server has had to fetch a database index from the file system instead of from the cache. The Key_read_requests object specifies the number of times the MySQL server has fetched a database index from cache. The alert says "If the number of times MySQL has had to fetch a database index from the file system is 1% or more of the number of times MySQL has fetched a database index from cache, generate an alert of severity "minor".
  • MySQL:Keycache_hitrate_normal. This alert compares the value of the Key_reads collection object to the value of the Key_read_requests collection object. The alert says "If the MySQL:Keycache_hitrate_low alert is still active, and if the number of times MySQL has had to fetch a database index from the file system is less than 1% of the number of times MySQL has fetched a database index from cache, generate an alert of severity "healthy".

To create these two alerts, perform the following:

  1. Go to the Dynamic Applications Manager page (System > Manage > Applications.
  1. Click the wrench icon ( ) for the Dynamic Application named MySQL:DBPerformance.
  2. Click the Alerts tab. The Dynamic Applications Alert Objects page appears.
  3. First, we will define the MySQL:Keycache_hitrate_low alert.
  4. Supply values in the following fields:
  • Policy Name. Enter MySQL:Keycache_hitrate_low.
  • Active State. Select Enabled. SL1 will monitor this alert.
  • Log Message. If this alert evaluates to TRUE, the alert will insert the following message in the device log (on the device where the condition occurred). Enter the following:

MySQL Keycache hitrate: %V% is low. Threshold: %T.

  • The %V variable says "substitute the value returned by the result function".
  • The %T variable says "substitute the value returned by the threshold function".
  • Maintain State. Select Yes. This alert will maintain its state until it is explicitly cleared by an event.
  • Trigger Alert. Select None. This is a deprecated field.

  • Formula Editor. This is where you describe the conditions under which you want SL1 to make an entry in the device log. Enter the following:

result(100-((o_5500/o_5501)*100)) < threshold(t_191)

  • This formula says: Divide the number of Key_reads by the number of Key_read_requests and convert that value to percent. If the percentage of Key_Reads is 1% or more, the alert will evaluate to TRUE. When the alert evaluates to TRUE, it makes an entry of severity "minor" in the appropriate device log.
  • o_5500 is the object ID of the Key_reads collection object.

NOTE: On your SL1 system, the Key_reads collection object will have a different object ID. Substitute the object ID from your SL1 system.

  • o_5501 is the object ID of the Key_read_requests collection object. If you have created the MySQL:DBPerformance Dynamic Application manually (instead of importing the Dynamic Application from the ScienceLogic Support Site), the Key_read_requests collection object will have a different object ID on your SL1 system. Substitute the object ID from your SL1 system.

NOTE: On your SL1 system, the Keycache_hitrate threshold will have a different object ID. Substitute the object ID from your SL1 system.

  • t_191 is the object ID of the Keycache_hitrate threshold.

NOTE: On your SL1 system, the Keycache_hitrate threshold will have a different object ID. Substitute the object ID from your SL1 system.

  • Remember that we set the Keycache_hitrate threshold to "99".
  • The result function returns the value of the formula and stores the value of the formula in the %V variable.
  • The threshold function returns the value of the threshold variable and stores the value of the threshold variable in the %T variable.
  1. Click the Save button to save the alert.

  1. In our example SL1 system, you will notice that the alert object has the following object ID:
  • MySQL:Keycache_hitrate_low = a_920

NOTE: On your SL1 system, the alert object will have a different object ID.

  1. Next we will define the MySQL:Keycache_hitrate_normal alert.
  2. Supply values in the following fields:
  • Policy Name. Enter MySQL:Keycache_hitrate_normal. 
  • Active State. Select Enabled. SL1will monitor this alert.

  • Log Message. If this alert evaluates to TRUE, the alert will insert the following message in the device log (on the device where the condition occurred. )Enter the following:

MySQL Keycache hitrate: %V% is normal.

  • The %V variable says "substitute the value returned by the result function".

  • Maintain State. Select No. This alert will not maintain its state and does not need to be explicitly cleared by an event.
  • Trigger Alert. Select None. This is a deprecated field.

  • Formula Editor. This is where you describe the conditions under which you want SL1 to make an entry in the device log. Enter the following:

result(100-((o_5500/o_5501)*100)) >= threshold(t_191) and active(a_920)

  • This formula says: Divide the number of Key_reads by the number of Key_read_requests and convert that value to percent. If the alert MySQL:keycache_hitrate_low is still active, and if the percentage of Key_Reads is 1% or less, the alert will evaluate to TRUE. When the alert evaluates to TRUE, it makes an entry of severity "healthy" in the appropriate device log.
  • o_5500 is the object ID of the Key_reads collection object.

NOTE: On your SL1 system, the Key_reads collection object will have a different object ID. Substitute the object ID from your SL1 system.

  • o_5501 is the object ID of the Key_read_requests collection object.

NOTE: On your SL1 system, the Key_read_requests collection object will have a different object ID. Substitute the object ID from your SL1 system.

  • t_191 is the object ID of the Keycache_hitrate threshold.

NOTE: On your SL1 system, the Keycache_hitrate threshold will have a different object ID . Substitute the object ID from your SL1 system.

  • a_920 is the object ID of the alert MySQL:keycache_hitrate_low.

NOTE: On your SL1 system, the Keycache_hitrate_low alert will have a different object ID. Substitute the object ID from your SL1 system.

  • Remember that we set the Keycache_hitrate threshold to "99".
  • The result function returns the value of the formula and stores the value of the formula in the %V variable.
  • The threshold function returns the value of the threshold variable and stores the value of the threshold variable in the %T variable.
  • The active function checks the state of a specified alert. If the specified alert is still active, the active function returns the value TRUE.
  1. Click the Save button to save the alert.

  1. On our example SL1 system, notice that the alert object has the following object ID:
  • MySQL:Keycache_hitrate_normal = a_921

NOTE: On your SL1 system, the alert object will have a different object ID.

Creating a Credential for the MySQL:DBPerformance Dynamic Application

If you want to align the MySQL:DBPerformance Dynamic Application with SL1's MySQL database, you must create a database credential that allows access to SL1's MySQL database.

Before you define the credential, you must collect the information you will need. In this case, you will need the username and password for the MySQL database. This account was defined during setup and is different than the account for logging into SL1.

If you can log in to the phpMyAdmin tool from the Appliance Manager page (System > Settings > Appliances), you can use the username and password you used to access the phpMyAdmin tool as the username and password in the credential. For details on accessing the phpMyAdmin tool, see the section on System Administration. If you need help, ask your administrator.

For details on the database password, see the section on System Administration.

For details on credentials, see the section on Credentials.

To create the credential for this example:

  1. Go to the Credential Management page (System > Manage > Credentials).
  2. In the the Credential Management page, click the Create menu. Select Database Credential.
  3. The Credential Editor modal page appears. In this page, you can define the new database credential. To define the new credential, supply values in the following fields:
  • Profile Name. Enter EM7 DB.
  • DB Type. Select MySQL.
  • DB Name. Enter master.
  • DB User. Username associated with a valid account on the database.
  • Password. Password associated with a valid account on the database.
  • Hostname/IP. Hostname or IP address where the database resides. To use the localhost, in the Hostname/IP field, enter the IP address 127.0.0.1. The credential will not work if you enter the string localhost in the Hostname/IP field.
  • Port. Enter 7706.
  1. Click the Save button to save the new database credential.

Aligning the Dynamic Application with a Device

For our example, we aligned the MySQL:DBPerformance Dynamic Application with the Database Server.

There are three ways to align the MySQL:DBPerformance Dynamic Application with a device:

  • During initial discovery or nightly auto-discovery. Because the MySQL:DBPerformance Dynamic Application includes a discovery object, SL1 can automatically align this Dynamic Application with devices during discovery. For details on discovery, see the section on Discovery.

  • Manual discovery for the Dynamic Application. Because the MySQL:DBPerformance Dynamic Application includes a discovery object, SL1 can automatically align this Dynamic Application with devices. From the Dynamic Applications Manager page, you can manually execute discovery for all devices, but only for the MySQL:DBPerformance Dynamic Application. For details on how to perform this type of discovery, see the section Dynamic Applications and Discovery..
  • Manually associate the Dynamic Application with an existing device. For details on how to perform this type of discovery, see the section on Managing Dynamic Applications.

This section will walk you through the steps to manually align the MySQL:DBPerformance Dynamic Application with the Database Server or the All-In-One Appliance.

To manually align the Dynamic Application to the Database Server or the All-In-One Appliance:

  • Go to the Appliance Manager page (System > Settings > Appliances). Determine the device name of the Database Server or the All-In-One Appliance.
  • Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic SL1 user interface).
  • Find the device where the database resides (either the Database Server or the All-In-One Appliance). Click the device's wrench icon ().
  • The Device Properties page appears. Click the Collections tab.
  • In the Dynamic Application Collections page, click the Action menu and select Add Dynamic Application.
  • The Dynamic Application Alignment page appears. Select MySQL:DBPerformance in the Dynamic Applications pane, and select EM7 DB in the Credentials pane.
  • Click the Save button to add the Dynamic Application to the device.
  • At the next polling period, SL1 should start collecting the data specified in the MySQL:DBPerformance Dynamic Application from the device where SL1's database resides.

Viewing Reports for the Dynamic Application

For our example, we aligned the MySQL:DBPerformance Dynamic Application with the Database Server on our device em7_ao.

To view the graphs for the presentation objects key_reads and key_read_requests:

  1. Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic SL1 user interface).
  2. Find the device for which you want to edit thresholds. Click its bar-graph icon ().
  3. Click the Performance tab. The Device Performance page appears.
  4. In the NavBar, find the entry for the MySQL:DBPerformance Dynamic Application and expand it. Select the entry for Key_reads.
  5. The graph for Key_reads appears.
  6. The graph displays the value of the Key_reads collection object in the y-axis and the date and time in the x-axis.
  7. In the NavBar, find the entry for the MySQL:DBPerformance Dynamic Application and expand it. Select the entry for Key_read_requests.
  8. The graph for Key_read_requests appears.
  9. The graph displays the value of the Key_read_requests collection object in the y-axis and the date and time in the x-axis.

Viewing Alerts for the Dynamic Application

To view alerts for the Dynamic Application:

  1. Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic SL1 user interface).
  2. Find the subscriber device for which you want to edit thresholds. Click its wrench icon ().
  3. Click the Logs tab. The Device Logs & Messages page appears.
  4. Look for alert messages from the Dynamic Application. In our example, our MySQL database did not fetch any database indexes from the file system, so only the "normal" alert appears in our device log.

Changing the Threshold for a Subscriber Device

You can change one or more threshold values for a single device. When SL1 evaluates alerts for that device, it will use the threshold values set in the Device Threshold page instead of the threshold value set in the Dynamic Application Threshold Objects page.

To edit a threshold for a single device:

  1. Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic SL1 user interface).
  2. Find the device for which you want to edit thresholds. Click its wrench icon ().
  3. Click the Thresholds tab. The Device Thresholds page appears.
  4. In Device Thresholds page, move the sliders to edit one or more thresholds.
  5. To save your changes, click the Save button.