new documentation for anomaly detection #9498
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
joeyouss
requested review from
navaneeth,
Rohit-Kaliki,
nikunj-badjatya,
raviyadalam,
iamanmolm,
sdsingh07,
sandyydk and
abhinavsingh-ccm
as code owners
Rohit-Kaliki
approved these changes
Feb 26, 2025
|
|
||
| - Resolved: An anomaly that has been resolved is marked as “Resolved”. | ||
|
|
||
| - Archived/Ignored: An anomaly that has been marked as ignored, appears in the Archived/Ignored list. Once an anomaly is more than 90 days, it is marked as archived. The Archived/Ignored page shows details about the anomalies marked as ignored as well as the estimated cost impact (total) from the anomalies, number of anomalies ignored and archived, etc. |
There was a problem hiding this comment.
Can we fix language on these, we can maintain the Archived ad Ignored as 2 separate states on the docs.
|
|
||
| While setting up a new alert, following can be selected: | ||
| - Scope: Scope for which the anomaly needs to be alerted for. This can be either for all account data that the user has access to or the user can specify perspectives for which anomaly alerts will be sent. | ||
| - Configuring the anomaly alert: Alert conditions follow your set preferences. You may override these thresholds, but only to increase them. Currently, the user can set thresholds for “Alert when cost difference is over ($)” and “Alert when cost difference is over (%)” depending on whether they want to define a specific cost amount or a cost percentage. |
There was a problem hiding this comment.
Can we clarify if these conditions are logical OR or if they are logical AND for the alert to be triggered.
|
|
||
| Similar to the above, this setting enables you to define a threshold based on the percentage of cost increase. Anomalies will only be flagged if the cost increase exceeds the specified percentage of the baseline cost. For example, if you set it to 5%, anomalies that cause a cost increase greater than 5% of the usual baseline cost will be reported. | ||
|
|
||
| 3. Anomaly Persistence |
There was a problem hiding this comment.
I think we call it Duration?
| ## Anomaly Drilldown | ||
| Once an anomaly is detected, for each of the anomaly detected, CCM provides insights into what are the resources which might be causing the anomaly. CCM queries the cloud provider's cost data, and identifies resources that have experienced significant cost increases compared to previous periods. CCM aggregates the total costs for each resource, computes the cost increase (or decrease) compared to the previous day, and orders the results by the highest increase in cost, helping to detect resources that have experienced significant cost spikes. | ||
|
|
||
| Detected anomalies are stored in a time series database and are available for review and analysis. |
| - Cost Trend and Anomalies: Graph showing Anomalies Spend and Spend within Range for historical data over a time period of either 30 or 90 days. | ||
| - Anomalies Spend: | ||
| - Spend within range: | ||
| - Top resource changes: Top resources with major cost impact due to the anomaly |
There was a problem hiding this comment.
Corresponding cloud labels on the resources for additional metadata
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description
PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged: