Start_Baselining: Start the baselining process
The monitoring agent can run a baselining process for every application. During this process, which runs for a preset period, the data collector collects statistical data on metric values for a given period. Based on this statistical data, the monitoring agent can automatically set the fair and bad thresholds, as well as the typical breakdown of response times for nested requests. Use the Start_Baselining Take Action to start the baselining process.
When Cloud Pak System Software begins monitoring an application for the first time, it automatically starts this process for the application. However, with time, average response times can change because of configuration, load pattern, database size, and other issues. You can manually start the baselining process again to take these changes into account. You can also use IBM® Tivoli® Monitoring policies and workflow management to run the baselining process every few months.
As soon as you take the Start Baselining action, the baselining process begins. The thresholds are updated when either the Period or the Update Interval passes.
While the baselining process is running, you can trigger a baseline update to immediately set the thresholds based on the information collected so far.
Command syntax
YN:Start_Baselining App_Id Period Update_Interval Run_Clean
Parameters:
- App_Id
- The application ID, automatically assigned in the portal from the selection context when Take Action was invoked.
- Period
- The time for which the baselining process runs. The data collector
collects the necessary statistical information for this entire period.
When Cloud Pak System Software starts
the baselining process automatically, it sets the period to seven
days. The format is
ddd/hh:mm:ss. - Update_Interval
- If you set this parameter to a time interval, Cloud Pak System Software updates
the thresholds according to the information already collected every
time this interval passes. For example, when Cloud Pak System Software starts
the baselining process automatically, it sets the update interval
to 1 hour. During the seven days that the initial baselining runs,
every hour the thresholds are updated according to the statistical
data collected so far (for all request types where at least one request
was received during the baselining process). The format is
ddd/hh:mm:ss. - Run_Clean
- Set to either 0 or 1. If set to 0, statistical data collected in any previous baselining for the same requests are kept and "amalgamated" with the new data. If set to 1, only the new data are used for setting the thresholds. Normally, you set this to 1.