Object Patrol Task

Performance patrol (database object patrol) applies the audit rules in a patrol template to the instance’s database objects (tables), identifying structural defects, naming violations, missing comments, and other risks. It is configured in the “Patrol config” step of the add-instance wizard, and can be triggered manually or on a schedule from the Database objects page after onboarding.

​

Goal

Check database objects for structural risks by applying the audit rules from a patrol template.

​

Prerequisites

Slow query config has passed and a patrol template matching the target database type is available.

​

Patrol config step

After slow query config passes, the wizard enters “Patrol config”. This step selects the patrol template (rule set) used for patrol. The patrol template determines the audit rules and severities applied during patrol. Templates are provided per database type (such as “MySQL database patrol template”) and share the same rule system as the Audit platform’s rule templates.

​

Manual patrol

After onboarding, click “Patrol” on the Database objects page to trigger a patrol immediately. Patrol runs server-side, and the summary and object list update when it finishes. After patrol, the summary shows the result (from a real sample):

​

Scheduled patrol

At the top of the Database objects page, turn on “Scheduled patrol”, set the interval (every N days) and time (at HH:MM), then click “Update”. The platform then patrols automatically on schedule.

​

Interpreting results

Patrol results are summarized by severity and rule — see Patrol Task Report.

​

Before you submit

• The patrol template matches the target database type;
• The rules enabled in the template match the governance goal;
• The summary updates after manual patrol;
• Scheduled patrol avoids business peak hours if needed.

​

FAQ

​

Related reading