Application Health
The Health tab shows the policy and operating signals that matter most for one application. Use it to spot drift, review recommendations, and understand whether the application is moving toward a stable operating state.
What you will find here:
- Health metrics for the selected period.
- Prioritized recommendations for the next improvement.
- A monitoring-status pipeline that shows the current operating stage.
- Business-facing policy and cost indicators when that view is enabled.
Tip: When health changes sharply, compare the same period in Sessions and Rules to find the rule, rollout, or traffic shift that changed the picture.
Application Health
The Health tab turns application activity into an operating picture that is easy to scan. It combines recent metrics, policy outcomes, and recommendations so teams can decide what to do next without stitching the story together by hand.
Business Owners and Auditors access portfolio-level and engagement-scoped health signals rather than per-application health. All other roles can view the Health tab.
Open Health when you want the current status of one application rather than a portfolio-wide view.
The Policy Health section shows rule coverage, threshold proximity, and any rules nearing their alert boundary. Check it daily to confirm that your active thresholds still match your organization’s risk tolerance.
The Integration Health indicator turns yellow when SDK coverage drops below the recommended threshold for this application. Click it to open Instrumentation Coverage and see exactly which fields need attention.
What good looks like
- Stable session volume.
- Healthy policy coverage.
- Clear recommendations with no critical blockers.
- A steady progression toward standard monitoring or steady state.
Activity Log
The Activity tab inside each application workspace records a chronological log of governance events and operational changes for that application. It is separate from session data — it captures what happened to the application itself, not what individual AI sessions did.
Events in the Activity Log include:
| Category | Example events |
|---|---|
| Governance | Rule activated, rule deactivated, governance threshold changed |
| Lifecycle | Application created, environment changed, operating stage transition |
| Configuration | AI context fields updated, enrichment settings changed |
| Access | API key created, rotated, or revoked |
| Data | Redaction policy changed, legal hold added or removed |
| Compliance | Audit engagement opened, evidence exported, framework mapping updated |
Each event entry includes: the actor (user identity and role), a timestamp, the event category, and a plain-language description of the change.
Developers and Business Owners do not see the Activity Log. Developers work with session traces and SDK diagnostics; Business Owners see governance stage transitions through the Governance Dashboard instead. The categories you see within the log are filtered server-side to match your role's authority.
You see every event category in the Activity Log. Use it to audit configuration changes made by other users — including key rotations, rule activations, and AI context edits. Every entry is tied to a user identity and timestamp for accountability.
Your Activity Log view shows governance and configuration events: rule activations, threshold changes, AI context updates, and prompt configuration edits. Use it to confirm your recent changes applied correctly and to review what changed before an unexpected policy shift.
Your Activity Log view shows compliance-relevant events: audit engagement updates, evidence exports, legal holds, and framework mapping changes. Use it to build a narrative of governance actions taken on this application ahead of an audit review.
Your Activity Log view is scoped to your active engagement date range. It shows compliance and governance events for the applications in scope. Use it to verify that governance actions (rule activations, evidence exports, engagement milestones) occurred within the required timeframes.