Configuring Monitoring Performance Properties

Configure auto-purge, flush threshold, and flush batch size settings to determine how long monitoring data is retained, optionally disable storing of logon information, and set a monitoring database to configure where data is stored.

1. In the left navigation pane of SAP Control Center, select Monitoring.
2. In the right administration pane, select the General tab.
3. Click Configuration.
4. Configure auto purge settings.
   Auto purge clears obsolete data from the monitoring database once it reaches the specified threshold.
   1. Select Enable auto purge configuration to activate auto purge functionality.
   2. Enter the length of time (in days) to retain monitoring data before it is purged.
5. Configure flush threshold settings.
   The flush threshold indicates how often data is flushed from memory to the database. This allows you to specify the size of the data saved in memory before it is cleared. Alternately, if you do not enable a flush threshold, data is automatically written to the monitoring database as it is captured.
   1. Select Enable flush threshold configuration to activate flush threshold functionality.
   2. Select one of:
      • Number of rows – monitoring data that surpasses the specified number of rows is flushed from memory. Enter the desired number of rows adjacent to Rows. The default is 100.
      • Time interval – monitoring data older than the specified time interval is flushed from memory. Enter the desired duration adjacent to Minutes. The default is 5.
      • Either rows or time interval – monitoring data is flushed from memory according to whichever value is reached first: either the specified number of rows or the specified time interval. Enter the desired rows and duration adjacent to Rows and Minutes, respectively.
6. If you enabled a flush threshold, enter a Flush batch row size by specifying the size of each batch of data sent to the monitoring database. The row size must be a positive integer.
   The batch size divides flushed data into smaller segments, rather than saving all data together according to the flush threshold parameters. For example, if you set the flush threshold to 100 rows and the flush batch row size to 50, once 100 rows are collected in the monitoring console, the save process executes twice; data is flushed into the database in two batches of 50 rows. If the flush threshold is not enabled, the flush batch row size is implicitly 1.
   Note By default, the monitoring database flushes data every 5 minutes. Alternatively, you can flush data immediately by removing or decreasing the default values, but doing so impacts performance and prevents you from using captured data.
7. Disable (unselect) Enable to save security access info, if you do not want to log security access (login) information in the database. This option is enabled by default:
   • Enabled records security log information whether the monitoring profile is disabled or enabled.
   • Disabled does not record security log information whether the monitoring profile is disabled or enabled.
8. Optional. To change the data source, select an available database from the Monitor database endpoint drop down list.
   Available databases are those with a JDBC server connection type created in the "default" domain. To create a new monitor database, a platform administrator must set up a database by running the appropriate configuration scripts and creating a server connection for the database in the default domain. The database server connection then appears as an option in the Monitor Database Endpoint drop down list.
9. Click OK.