AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
Use this operation to suppress anomaly detection for a specified anomaly or pattern. If you suppress an anomaly, CloudWatch Logs won’t report new occurrences of that anomaly and won't update that anomaly with new data. If you suppress a pattern, CloudWatch Logs won’t report any anomalies related to that pattern.
You must specify either anomalyId or patternId, but you can't specify
both parameters in the same operation.
If you have previously used this operation to suppress detection of a pattern or anomaly,
you can use it again to cause CloudWatch Logs to end the suppression. To do this,
use this operation and specify the anomaly or pattern to stop suppressing, and omit
the suppressionType and suppressionPeriod parameters.
This is an asynchronous operation using the standard naming convention for .NET 4.5 or higher. For .NET 3.5 the operation is implemented as a pair of methods using the standard naming convention of BeginUpdateAnomaly and EndUpdateAnomaly.
Namespace: Amazon.CloudWatchLogs
Assembly: AWSSDK.CloudWatchLogs.dll
Version: 3.x.y.z
public virtual Task<UpdateAnomalyResponse> UpdateAnomalyAsync( UpdateAnomalyRequest request, CancellationToken cancellationToken )
Container for the necessary parameters to execute the UpdateAnomaly service method.
A cancellation token that can be used by other objects or threads to receive notice of cancellation.
| Exception | Condition |
|---|---|
| InvalidParameterException | A parameter is specified incorrectly. |
| OperationAbortedException | Multiple concurrent requests to update the same resource were in conflict. |
| ResourceNotFoundException | The specified resource does not exist. |
| ServiceUnavailableException | The service cannot complete the request. |
.NET Core App:
Supported in: 3.1
.NET Standard:
Supported in: 2.0
.NET Framework:
Supported in: 4.5