Fixing compliance evaluation issues #192
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview/Summary
The compliance evaluation for the following alerts is not evaluated correctly despite the corresponding alerts were created correctly:
Reason why, is a wrong value for the minFailingPeriodsToAlert and numberOfEvaluationPeriods fields.
After correction, with a simple AMBA re-deployment and without running the remediation again if already executed, the resources appear compliant
Remediation tasks for alerts Deploy AGW BackendLastByteResponseTime and Deploy AGW ApplicationGatewayTotalTime are failing see GH Issue #194) because the value for timeAggregation is set to Total which is not allowed. Allowed values are Average and Maximum as per error message:
{"code":"BadRequest","message":"Time aggregation must be one of [Average, Maximum]. Activity ID: 2f08dc2e-10ce-470c-ae4a-5686252aaedc."}
Given the alerts being using dynamic thresholds, changing the value to Average, will make the remediation tasks successful:
![image](https://private-user-images.githubusercontent.com/26008435/322844175-84f6033c-bc98-46d3-8df9-44fbedfb59e9.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkwODQ5OTksIm5iZiI6MTczOTA4NDY5OSwicGF0aCI6Ii8yNjAwODQzNS8zMjI4NDQxNzUtODRmNjAzM2MtYmM5OC00NmQzLThkZjktNDRmYmVkZmI1OWU5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA5VDA3MDQ1OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTU5MTQ4NThiOWYyMDJlZWM0M2IzMjQ0ZGViZTllNGRlMTk2NzE4ZTFkYjhlZmE1MWZjMDYwZjViMmMwOGExMTkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.fMNUC5ZehNBEp2My4-T-jeWVTjMngtg_LfGV7oQnMQQ)
This PR fixes/adds/changes/removes
Breaking Changes
As part of this Pull Request I have
main
branch