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
{{ message }}
This repository was archived by the owner on Sep 12, 2024. It is now read-only.
The bug occurs when a KPI is edited and all existing sub-dimensions are completely removed so no sub-dimension is being ran for anomaly detection for a KPI.
Explain the environment
Chaos Genius version: 0.6.1
OS Version / Instance: macOS Big Sur 11.6.3
Deployment type: setup from scratch
Current behavior
If a KPI is set up without sub-dimensions in the first place this error does not come up. However, after editing an existing KPI by removing all sub-dimensions, this task failure appears saying ValueError: No group keys passed! .
Expected behavior
When a KPI is edited to remove all sub-dimensions (in the case we do not want anomaly detection for sub-dimensions), it should allow us to give no keys for sub-dimensions without producing an error, or there should be an option to not run anomaly detection on sub-dimensions.
Screenshots
The task failure csv returned for one of the KPIs with this issue.
Additional context
We recreated the KPI from scratch without including any sub-dimensions and there were no task failures raised.
Logs
Provided in Expected Behavior section.
The text was updated successfully, but these errors were encountered:
Describe the bug
The bug occurs when a KPI is edited and all existing sub-dimensions are completely removed so no sub-dimension is being ran for anomaly detection for a KPI.
Explain the environment
Current behavior
If a KPI is set up without sub-dimensions in the first place this error does not come up. However, after editing an existing KPI by removing all sub-dimensions, this task failure appears saying
ValueError: No group keys passed!
.Expected behavior
When a KPI is edited to remove all sub-dimensions (in the case we do not want anomaly detection for sub-dimensions), it should allow us to give no keys for sub-dimensions without producing an error, or there should be an option to not run anomaly detection on sub-dimensions.
Screenshots
The task failure csv returned for one of the KPIs with this issue.
Additional context
We recreated the KPI from scratch without including any sub-dimensions and there were no task failures raised.
Logs
Provided in Expected Behavior section.
The text was updated successfully, but these errors were encountered: