Setting Threshold Values
Threshold values for monitored objects can be set on specific servers. Setting specific threshold values at the command line for attributes of a monitored object overrides for that object any factory-configured threshold values concerning the attribute. Any entries in the monitoring.properties configuration file concerning the attribute are also overridden.
To Set Threshold Values
for a Server
Before You Begin
To enable the management agent IP and security credentials on a server named server, add the management features on the server as explained in Adding Base and OS Management Features.
Steps
-
Log in to the N1 System Manager.
See To Access the N1 System Manager Command Line for details.
-
Use the set server command with the threshold attribute.
The syntax requires the threshold keyword to be followed by the attribute for which you are setting a threshold. The attribute is an OS resource utilization attribute. OS resource utilization attributes are described in OS Resource Utilization Monitoring and listed in Table 5–2.
The threshold is either criticallow, warninglow, warninghigh, or criticalhigh. The value is a numeric figure and usually represents a percentage.
Example 5–2 Setting Multiple Threshold Values for CPU Usage on a Server
This example shows how to set the CPU usage warninghigh severity threshold on a provisionable server named serv1 to 53 percent. This example also shows how to set the criticalhigh severity threshold value to 75 percent.
N1-ok> set server serv1 threshold cpustats.pctusage warninghigh 53 criticalhigh 75 |
These values override the default values stored in the monitoring.properties configuration file on the management server for the server named serv1.
Example 5–3 Setting Multiple Threshold Values for File System Usage On a Server
This example sets the file system usage warninghigh threshold on a provisionable server named serv1 to 75 percent. This example also shows how to set the criticalhigh threshold value to 87 percent.
N1-ok> set server serv1 threshold fsusage.pctused warninghigh 75 criticalhigh 87 |
Example 5–4 Deleting a Threshold Value for File System Usage on a Server
This example shows how to delete a value that was set for the warninghigh threshold on a provisionable server named serv1.
N1-ok> set server serv1 threshold fsusage warninghigh none |
In this case, any previously set value for this threshold at this severity is deleted. The threshold severity value does not revert back to the default threshold value, which is stored in the monitoring.properties configuration file, or to the factory-configured default, if this default existed for the attribute. In effect, monitoring is disabled for the warninghigh threshold for file system usage for this server.
To Set Threshold Values
for a Server Group
Before You Begin
To enable the management agent IP and security credentials on a server named server, add the management features on the server as explained in Adding Base and OS Management Features.
Steps
-
Log in to the N1 System Manager.
See To Access the N1 System Manager Command Line for details.
-
Use the set group command with the threshold attribute.
The syntax requires the threshold keyword to be followed by the attribute for which you are setting a threshold. The attribute is an OS resource utilization attribute. OS resource utilization attributes are described in OS Resource Utilization Monitoring and listed in Table 5–2.
The threshold is either criticallow, warninglow, warninghigh, or criticalhigh. The value is a numeric figure, and usually represents a percentage.
Example 5–5 Setting Multiple Threshold Values for File System Usage on a Server Group
This example shows how to set the file system usage warninghigh threshold to 75 percent on a group of provisionable servers with a group name of grp3. This example also shows how to set the criticalhigh threshold severity value to 87 percent.
N1-ok> set group grp3 threshold fsusage.pctused warninghigh 75 criticalhigh 87 |
- © 2010, Oracle Corporation and/or its affiliates