Purging Orchestration Monitoring Logs
You can purge and archive orchestration monitoring logs.
About this task
When the Integration Appliance purges orchestration monitoring data, it can take a few minutes for the Dashboard to display the updated job counts.
By default, an Integration Appliance purges orchestration monitoring logs older than 30 days when any of the following conditions occurs on the Integration Appliance:
- The amount of available disk space falls below 50%.
- One day has passed since the last purge.
- More than 5,000 orchestration jobs have completed.
- More than 1,000 orchestration jobs have contained an error.
Using the WMC, you can configure the job log purging parameters on the Integration Appliance that determine:
- Trigger Conditions - What conditions trigger the Integration Appliance to purge orchestration monitoring data.
- Frequency - How often to purge orchestration monitoring data.
- Job Scope - What type of orchestration monitoring data to purge.
Procedure
- From the Navigation pane, select . The Results page is displayed.
- Click Settings. The Job Log Settings dialog box is displayed. By default the Purge page is displayed.
- Specify the parameters as described in the following section.
- Click Save.
Job Log Purging Parameters
Trigger Conditions
The amount of free disk space on the Integration Appliance, the time lapse since the last orchestration monitoring logs were purged, the number of completed jobs, and the number of jobs containing errors are all triggers that can initiate the purging or archiving of orchestration monitoring logs. The Integration Appliance uses "OR" logic and purges orchestration monitoring data when any one of the trigger conditions occurs.
Parameter | Description | Default |
---|---|---|
Available disk space | This trigger fires when the percentage of free disk space is less than the specified value. When this trigger fires, the Integration Appliance purges the orchestration monitoring data as you specify in the Job Scope parameters. If the percentage of free disk space is still short of the percentage you specified, the Integration Appliance purges 50% of the remaining orchestration monitoring data until the value is reached. For example, you specify the following values for purging parameters:
If only 10% of the Integration Appliance disk is free, the Available disk space trigger fires and the Integration Appliance purges all completed jobs that are older than 30 days. However, purging this data only frees 10% of the disk space. Since the minimum amount of free disk space is still not satisfied, the Integration Appliance purges an additional 50% of the remaining orchestration monitoring data. The Integration Appliance continues to purge the remaining orchestration monitoring data by 50%, until the minimum available disk space is greater than or equal to the specified value. You can specify a value between 1-100 percent, any value outside a 40-75 percent range results in the Integration Appliance using the default value of 50%. Note: This
is a required parameter.
|
50% |
Schedule | This trigger fires when the period since the last purge is greater than the specified day, hours, minutes value. You can more precisely schedule a purge by selecting the Fixed option. When you select the Schedule Fixed option, the schedule you specify overrides the day, hours, minutes value specified since last purge. To schedule a purge:
|
1 day |
Completed job count | This trigger fires when the number of completed jobs is greater than the specified value. This parameter must be a positive integer value. Note: After the Integration Appliance purges
the jobs, the job count is no longer visible from the WMC.
|
5,000 jobs |
Errored job count | This trigger fires when the number of jobs containing errors is greater than the specified value. Errored job count includes any orchestration job in the following states: unknown, cancelled, terminated, or errored. This parameter must be a positive integer value. Note: After the Integration Appliance purges the jobs, the
job count is no longer visible from the WMC.
|
1,000 jobs |
Frequency
The frequency determines the interval at which the Integration Appliance checks the set of defined triggers for an actionable condition. You can specify the frequency interval in increments of hours, minutes, and seconds.
By default, this parameter is set to 10 seconds.
Job Scope
Along with specifying trigger conditions and frequency, you must also specify the type of orchestration job data you want to purge. The Integration Appliance uses the values you specify for the Job Status AND the Jobs Older Than parameters OR the values you specify for Job Status AND Jobs Older Than the Most Recent parameters to determine when the Integration Appliance purges data.
Parameter | Description | Default |
---|---|---|
Job status | This parameter specifies the type of orchestration jobs that the Integration Appliance purges. By default, this parameter is set to ANY, which purges completed and jobs containing errors. You can choose to purge only the completed jobs by specifying COMPLETED. | Any |
Jobs older than | This parameter specifies the minimum age of orchestration jobs to purge. The Integration Appliance purges anything older than the amount of time you specify. You can specify the age of an orchestration job in months, days, hours, and minutes. | 7 days |
Jobs older than the most recent | This parameter specifies the number of most recent jobs that the orchestration job must be older than before the Integration Appliance purges data. | 1,000 jobs |