We derive eventing status from CAS Service (Cloud Account Service independent from Entity Data Service stack) and sync it to CloudHealth on a regular schedule. To determine eventing status, we use two attributes (Account status, EventStream Status). We discovered four statuses for eventing in CloudHealth from the CAS Service.
The default eventing status is In Progress. This means that if an account is onboarded in cloudhealth but has not yet been synced to CAS, it will be in the In Progress state.
If eventing status is off, there might be issues in the asset collection related to that subscription as well.
Azure
Account status(CAS)
|
Event Stream Status(CAS)
|
Eventing Status(CH)
|
---|---|---|
Active | Connected | ON |
Active | ""/Disconnected | OFF |
Validation-failed | ""/Connected/Disconnected | FAILED |