Review policy trends
Use policy trends to find when rule behavior changed and inspect the sessions behind that change. The chart is a starting point for investigation, not a health score by itself.
Open Trends
Open Analytics and select Trends. The available view and summary follow your role and analytics permissions.
Set the scope
Choose the reporting period and, when available, an application or group. Keep the scope consistent across comparisons. Note differences in traffic volume or workload that could affect the result.
Find a meaningful change
Look for a sustained change in rule results, exceptions, or session volume. Do not use a fixed “healthy” score band; compare the result with the goals and expected traffic for the selected application.
Open the sessions
Select a chart point to open the sessions for that date or period. Review the matched rule, decision, risk, and recorded policy inputs.
Investigate the cause
Before editing policy, check recent application deployments, active rule changes, SDK Health field coverage, and changes in traffic mix. Record the evidence for the explanation. Keep an unconfirmed cause separate from a recorded fact.
Take the smallest useful action
Assign missing-field work to the application team, test a rule change, or route specific sessions for review. Check the affected records after the update. A lower exception count alone does not prove an improvement if fewer sessions were evaluated.
A trend chart does not prove why a result changed or that a compliance requirement is met. Use the linked sessions and current policy configuration as the evidence for your conclusion.