Instance Scan
Run health checks against your own instance: check types, suites, findings and how to fold them into a release process.
Run health checks against your own instance: check types, suites, findings and how to fold them into a release process.
- Instance Scan turns tribal standards into automated checks
- Suites group checks for a purpose, for example pre release
- Findings need triage, otherwise the list becomes noise
- Custom linter checks enforce your own coding conventions
What it checks
Instance Scan runs checks against configuration records and reports findings. Out of box checks cover coding standards, unused customisations, performance risks such as missing indexes, and security patterns like ACLs that are too broad.
Check types
Table checks evaluate every row of a table against a condition. Script only checks run arbitrary logic. Linter checks parse script fields for patterns, for example use of gs.log in scoped code. Column checks look at one field across records.
Making it useful
A scan that nobody reads is wasted.
- Create a suite for your own standards and run it weekly
- Triage findings into fix now, fix later and accepted
- Run the suite before a release and treat new critical findings as blockers
- Write custom linter checks for the standards your team argues about most