Instrumentation Coverage
Instrumentation Coverage shows how completely your SDK populates the inputs that policies depend on. Use it to find missing fields before they turn into blind spots.
What you can review here:
- Overall coverage for the selected window.
- Coverage by field, including declared, inferred, and missing values.
- The exact SDK fields your application is sending today.
- Exportable reports for audits and implementation reviews.
Tip: Fix the lowest-coverage fields first. They usually create the largest improvement in policy reliability.
Instrumentation Coverage
This page helps teams answer a practical question: does the SDK send enough data for policies to evaluate sessions reliably? The view is especially useful after onboarding a new application or changing instrumentation.
Instrumentation Coverage is a technical diagnostics view. Only Administrators and Developers can access it. Governance Engineers review policy coverage in the Rules workspace — not here.
Declared values come directly from your SDK. Inferred values are reconstructed by VeriProof and are useful, but they are not a substitute for explicit input coverage.
This is your primary signal for whether your SDK integration is sending complete governance data. Start with the fields that score below 60% declared coverage — those are the most likely to cause policy blind spots. The Debug panel on each field shows which specific spans are missing the attribute.
The Export coverage report button downloads a CSV of coverage by field and application. Use it in onboarding reviews and go-live checklists to confirm that every application meets your minimum coverage bar before production traffic starts.
Focus areas
- Raise declared coverage on high-value fields.
- Review missing fields before widening rule scope.
- Export reports for implementation reviews.