Framework
Job details
Name: |
Framework |
Platform: |
Mysql |
Category: |
Maintenance |
Description: |
dbWatch engine framework job (for internal use only). Used for patching or upgrading of dbWatch engine framework. |
Long description: |
dbWatch engine framework job (for internal use only). Used for patching or upgrading of dbWatch engine framework. |
Version: |
1.32 |
Default schedule: |
50 5 1 * |
Requires engine install: |
Yes |
Compatibility tag: |
.[type=‘instance’ & is_mysql_branch=‘1′]/.[hasengine=‘YES’] |
Parameters
Name |
Default value |
Description |
Job Summary
- Purpose: The purpose of this job is to manage and maintain the dbWatch engine framework. This includes tasks like patching and upgrading, as well as some checks and registrations. This job is intended solely for internal use.
- Why: This job is crucial because it ensures that the dbWatch engine framework is up-to-date, operating effectively, and registering new tasks and parameters correctly. It maintains checks on various tasks like ‘Aborted clients’, ‘Aborted connections’, ‘Binlog cache check’, ‘InnoDB buffer pool check’, ‘MyISAM key cache check’, ‘NDB data memory usage check’, ‘NDB data node status’, ‘Query cache hitrate’, ‘SQL statistics’, ‘Threads statistics’, ‘Temporary table check’ – among others.
- Manual checking: Unfortunately, manual checking cannot be performed using simple SQL commands due to the complexity and intricacy of the job.
Report Summary
- Reporting: This job also provides a report titled ‘Framework’. The report indicates if the dbWatch framework has been successfully installed and points out that the task should not be removed as it is intended for internal use only.
Cleanup on Failure
- If the job fails for any reason, a cleanup procedure is run, which drops the procedure ‘dbw_framework_proc’.
Other Details
- Default schedule: The default schedule for this job is ‘50 5 1 *’.
- Version: The job has a version of ‘1.32′.
- Company: The job is designed by ‘dbwatch.com’.
- Dependency: The job has a dependency on the ‘dbw_framework_proc’ object which is the main procedure. On failure of this object, a cleanup is initiated.
- Reporting schedule: The default schedule for the report is ‘0 * * *’.
- Metadata: The job is categorised under ‘Maintenance’.
In summary, this job is crucial for the appropriate maintaining and functioning of the dbWatch engine framework.