Why are CloudHealth policy violations sometimes delayed?

Products

• CloudHealth

Issue/Introduction

This is likely due to the policy posting the last known timeframe a violation took place which would not necessarily align with the most recent evaluation.

CloudHealth Policies and Notification Center may sometimes appear to have delays or latency in reporting violations due to this.

When the CloudHealth Policy Engine detects a violation (conditions in the rule of a policy block are met), a new Violation is added for that policy block, along with the corresponding timestamp.

However, if no violations are found during the scheduled policy evaluation period, then no violation is added, and nothing is added to the Notifications page.

For example, if a policy evaluates hourly but the last time a violation was found was 3 days prior, the policy violation API and the Notifications page would show the timestamp and violation from 3 days prior, not the current timestamp.

This results in a timeline of policy violations, which can be queried as described in our API Documentation.