|
883 | 883 | "BurnRateConfigurations":{ |
884 | 884 | "shape":"BurnRateConfigurations", |
885 | 885 | "documentation":"<p>Use this array to create <i>burn rates</i> for this SLO. Each burn rate is a metric that indicates how fast the service is consuming the error budget, relative to the attainment goal of the SLO.</p>" |
| 886 | + }, |
| 887 | + "CreateRecommendedSlo":{ |
| 888 | + "shape":"Boolean", |
| 889 | + "documentation":"<p>Set this to <code>true</code> to create a recommended SLO out of the box. When set to <code>true</code>, you don't need to specify the <code>MetricThreshold</code> or <code>ComparisonOperator</code> in the <code>SliConfig</code> or <code>RequestBasedSliConfig</code>. The default value is <code>false</code>.</p> <p>This is supported for SLOs on a service, service operation, or a dependency.</p>" |
886 | 890 | } |
887 | 891 | } |
888 | 892 | }, |
|
1309 | 1313 | }, |
1310 | 1314 | "Auditors":{ |
1311 | 1315 | "shape":"Auditors", |
1312 | | - "documentation":"<p>A list of auditor names to filter the findings by. Only findings generated by the specified auditors will be returned.</p> <p>The following auditors are available for configuration:</p> <ul> <li> <p> <code>slo</code> - SloAuditor: Identifies SLO violations and detects breached thresholds during the Assessment phase.</p> </li> <li> <p> <code>operation_metric</code> - OperationMetricAuditor: Detects anomalies in service operation metrics from Application Signals RED metrics during the Assessment phase</p> <note> <p>Anomaly detection is not supported for sparse metrics (those missing more than 80% of datapoints within the given time period).</p> </note> </li> <li> <p> <code>service_quota</code> - ServiceQuotaAuditor: Monitors resource utilization against service quotas during the Assessment phase</p> </li> <li> <p> <code>trace</code> - TraceAuditor: Performs deep-dive analysis of distributed traces, correlating traces with breached SLOs or abnormal RED metrics during the Analysis phase</p> </li> <li> <p> <code>dependency_metric</code> - CriticalPathAuditor: Analyzes service dependency impacts and maps dependency relationships from Application Signals RED metrics during the Analysis phase</p> </li> <li> <p> <code>top_contributor</code> - TopContributorAuditor: Identifies infrastructure-level contributors to issues by analyzing EMF logs of Application Signals RED metrics during the Analysis phase</p> </li> <li> <p> <code>log</code> - LogAuditor: Extracts insights from application logs, categorizing error types and ranking severity by frequency during the Analysis phase</p> </li> </ul> <note> <p> <code>InitAuditor</code> and <code>Summarizer</code> auditors are not configurable as they are automatically triggered during the audit process.</p> </note>" |
| 1316 | + "documentation":"<p>A list of auditor names to filter the findings by. Only findings generated by the specified auditors will be returned.</p> <p>The following auditors are available for configuration:</p> <ul> <li> <p> <code>slo</code> - SloAuditor: Identifies SLO violations and detects breached thresholds during the Assessment phase.</p> </li> <li> <p> <code>operation_metric</code> - OperationMetricAuditor: Detects anomalies in service operation metrics from Application Signals RED metrics during the Assessment phase</p> <note> <p>Anomaly detection is not supported for sparse metrics (those missing more than 80% of datapoints within the given time period).</p> </note> </li> <li> <p> <code>service_quota</code> - ServiceQuotaAuditor: Monitors resource utilization against service quotas during the Assessment phase</p> </li> <li> <p> <code>trace</code> - TraceAuditor: Performs deep-dive analysis of distributed traces, correlating traces with breached SLOs or abnormal RED metrics during the Analysis phase</p> </li> <li> <p> <code>dependency_metric</code> - CriticalPathAuditor: Analyzes service dependency impacts and maps dependency relationships from Application Signals RED metrics during the Analysis phase</p> </li> <li> <p> <code>top_contributor</code> - TopContributorAuditor: Identifies infrastructure-level contributors to issues by analyzing EMF logs of Application Signals RED metrics during the Analysis phase</p> </li> <li> <p> <code>log</code> - LogAuditor: Extracts insights from application logs, categorizing error types and ranking severity by frequency during the Analysis phase</p> </li> <li> <p> <code>change_indicator</code> - ChangeIndicatorAuditor: Detects change events (deployments, configuration changes) that occurred within 10 minutes before and during a detected anomaly, and surfaces them as findings with deployment timestamps in the Analysis phase. When changes are detected, the <code>top_contributor</code> auditor skips its analysis to avoid redundancy.</p> </li> </ul> <note> <p> <code>InitAuditor</code> and <code>Summarizer</code> auditors are not configurable as they are automatically triggered during the audit process.</p> </note>" |
1313 | 1317 | }, |
1314 | 1318 | "AuditTargets":{ |
1315 | 1319 | "shape":"AuditTargets", |
|
2608 | 2612 | }, |
2609 | 2613 | "ServiceLevelIndicatorConfig":{ |
2610 | 2614 | "type":"structure", |
2611 | | - "required":[ |
2612 | | - "SliMetricConfig", |
2613 | | - "MetricThreshold", |
2614 | | - "ComparisonOperator" |
2615 | | - ], |
| 2615 | + "required":["SliMetricConfig"], |
2616 | 2616 | "members":{ |
2617 | 2617 | "SliMetricConfig":{ |
2618 | 2618 | "shape":"ServiceLevelIndicatorMetricConfig", |
2619 | 2619 | "documentation":"<p>Use this structure to specify the metric to be used for the SLO.</p>" |
2620 | 2620 | }, |
2621 | 2621 | "MetricThreshold":{ |
2622 | 2622 | "shape":"ServiceLevelIndicatorMetricThreshold", |
2623 | | - "documentation":"<p>This parameter is used only when a request-based SLO tracks the <code>Latency</code> metric. Specify the threshold value that the observed <code>Latency</code> metric values are to be compared to.</p>" |
| 2623 | + "documentation":"<p>This parameter is used only when a request-based SLO tracks the <code>Latency</code> metric. Specify the threshold value that the observed <code>Latency</code> metric values are to be compared to.</p> <p>This is not required if <code>CreateRecommendedSlo</code> is set to <code>true</code>.</p>", |
| 2624 | + "box":true |
2624 | 2625 | }, |
2625 | 2626 | "ComparisonOperator":{ |
2626 | 2627 | "shape":"ServiceLevelIndicatorComparisonOperator", |
2627 | | - "documentation":"<p>The arithmetic operation to use when comparing the specified metric to the threshold.</p>" |
| 2628 | + "documentation":"<p>The arithmetic operation to use when comparing the specified metric to the threshold.</p> <p>This is not required if <code>CreateRecommendedSlo</code> is set to <code>true</code>.</p>" |
2628 | 2629 | } |
2629 | 2630 | }, |
2630 | 2631 | "documentation":"<p>This structure specifies the information about the service and the performance metric that a period-based SLO is to monitor.</p>" |
|
0 commit comments