If the interval for this service level objective is a calendar interval, this structure contains the interval specifications.

A dimension is a name/value pair that is part of the identity of a metric. Because dimensions are part of the unique identifier for a metric, whenever you add a unique name/value pair to one of your metrics, you are creating a new variation of that metric. For example, many Amazon EC2 metrics publish InstanceId as a dimension name, and the actual instance ID as the value for that dimension.

This structure contains the attributes that determine the goal of an SLO. This includes the time period for evaluation and the attainment threshold.

The time period used to evaluate the SLO. It can be either a calendar interval or rolling interval.

This structure defines the metric used for a service level indicator, including the metric name, namespace, and dimensions

Use this structure to define a metric or metric math expression that you want to use as for a service level objective.

This structure contains information about one CloudWatch metric associated with this entity discovered by Application Signals.

This structure defines the metric to be used as the service level indicator, along with the statistics, period, and unit.

This structure defines the metric that is used as the "good request" or "bad request" value for a request-based SLO. This value observed for the metric defined in TotalRequestCountMetric is divided by the number found for MonitoredRequestCountMetric to determine the percentage of successful requests that this SLO tracks.

This structure contains information about the performance metric that a request-based SLO monitors.

This structure specifies the information about the service and the performance metric that a request-based SLO is to monitor.

This structure contains the information about the metric that is used for a request-based SLO.

Use this structure to specify the information for the metric that a period-based SLO will monitor.

If the interval for this SLO is a rolling interval, this structure contains the interval specifications.

This structure contains information about one of your services that was discovered by Application Signals.

This structure contains information about one dependency of this service.

This structure contains information about a service dependent that was discovered by Application Signals. A dependent is an entity that invoked the specified service during the provided time range. Dependents include other services, CloudWatch Synthetics canaries, and clients that are instrumented with CloudWatch RUM app monitors.

This structure contains information about the performance metric that a period-based SLO monitors.

This structure specifies the information about the service and the performance metric that a period-based SLO is to monitor.

This structure contains the information about the metric that is used for a period-based SLO.

Use this structure to specify the information for the metric that a period-based SLO will monitor.

A structure containing information about one service level objective (SLO) that has been created in Application Signals. Creating SLOs can help you ensure your services are performing to the level that you expect. SLOs help you set and track a specific target level for the reliability and availability of your applications and services. Each SLO uses a service level indicator (SLI), which is a key performance metric, to calculate how much underperformance can be tolerated before the goal that you set for the SLO is not achieved.

A structure containing an SLO budget report that you have requested.

A structure containing information about one error that occurred during a BatchGetServiceLevelObjectiveBudgetReport operation.

A structure that contains information about one service level objective (SLO) created in Application Signals.

This structure contains information about an operation discovered by Application Signals. An operation is a specific function performed by a service that was discovered by Application Signals, and is often an API that is called by an upstream dependent.

This structure contains information about one of your services that was discovered by Application Signals

A key-value pair associated with a resource. Tags can help you organize and categorize your resources.