You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When looking at rule failures, the only way we can figure this out is through the rule_uuid. It is not clear what this rule_uuid points to, and what specific rule in this uuid it points to.
There are mechanisms to figure this out by looking at the stack trace that tells you the exact call. However, it might be simpler to have a rule type in table so that it is easier to triage and fix issues.
Acceptance criteria
There is a new column on rule_failure_telemetry that shows the type of rule that failed
Values are populated on the rule_failure_telemetry table with the values (data migration for easier verification)
The value is added on avni_client when syncing rule_failure_telemetry
There is a way to temporarily update the value if not provided on avni_server
Old clients syncing should still be able to populate the value of rule_type on the table (we should not have to wait until everyone upgrades for the column to be populated)
The text was updated successfully, but these errors were encountered:
When looking at rule failures, the only way we can figure this out is through the rule_uuid. It is not clear what this rule_uuid points to, and what specific rule in this uuid it points to.
There are mechanisms to figure this out by looking at the stack trace that tells you the exact call. However, it might be simpler to have a rule type in table so that it is easier to triage and fix issues.
Acceptance criteria
The text was updated successfully, but these errors were encountered: