Check SDK health

Use SDK Health to answer two questions: is this application sending sessions, and are those sessions carrying the inputs its rules need?

Review an application

Open Applications and select the application.
Open SDK Health.
Check the latest activity and recent error rate.
Review field coverage. Prioritize fields used by active rules.
Send a test session after changing the integration and confirm the field is now declared.

SDK Health reports observed application data. It does not define one universal healthy latency or error-rate threshold. Use the goals set for your application and environment.

Recorded activity in SDK Health shows that data arrived and which fields were available. It does not prove that VeriProof controlled an action. Check Control coverage, then test an allowed action and an action denied before it takes effect.

Understand transport recovery

The SDK transport can pause repeated requests and retain a limited number of records during an ingest outage. This recovery behavior does not guarantee delivery. Check the reference for your installed package in Tools and SDKs before changing transport settings.

For TypeScript core SDK 1.0.0, the default circuit opens after three consecutive failures, retries after 30 seconds, and buffers up to 500 payloads. When the buffer is full, it drops the oldest payload. These defaults do not apply to every language or release. Monitor transport metrics for dropped records and assess any resulting evidence gaps.

Turn on diagnostic logging briefly

Python


import logging
 
logging.getLogger("veriproof_sdk").setLevel(logging.DEBUG)

TypeScript


import { diag, DiagConsoleLogger, DiagLogLevel } from '@opentelemetry/api';
 
diag.setLogger(new DiagConsoleLogger(), DiagLogLevel.DEBUG);

.NET


builder.Logging.AddFilter("Veriproof", LogLevel.Debug);

Turn verbose logging off after the investigation. Review logs before sharing them because session metadata can be sensitive.