Struct CreateServiceLevelObjectiveFluentBuilder 

pub struct CreateServiceLevelObjectiveFluentBuilder { /* private fields */ }

Fluent builder constructing a request to CreateServiceLevelObjective.

Creates a service level objective (SLO), which can help you ensure that your critical business operations are meeting customer expectations. Use SLOs to set and track specific target levels for the reliability and availability of your applications and services. SLOs use service level indicators (SLIs) to calculate whether the application is performing at the level that you want.

Create an SLO to set a target for a service or operation’s availability or latency. CloudWatch measures this target frequently you can find whether it has been breached.

The target performance quality that is defined for an SLO is the attainment goal.

You can set SLO targets for your applications that are discovered by Application Signals, using critical metrics such as latency and availability. You can also set SLOs against any CloudWatch metric or math expression that produces a time series.

You can't create an SLO for a service operation that was discovered by Application Signals until after that operation has reported standard metrics to Application Signals.

When you create an SLO, you specify whether it is a period-based SLO or a request-based SLO. Each type of SLO has a different way of evaluating your application's performance against its attainment goal.

• A period-based SLO uses defined periods of time within a specified total time interval. For each period of time, Application Signals determines whether the application met its goal. The attainment rate is calculated as the number of good periods/number of total periods.

  For example, for a period-based SLO, meeting an attainment goal of 99.9% means that within your interval, your application must meet its performance goal during at least 99.9% of the time periods.

• A request-based SLO doesn't use pre-defined periods of time. Instead, the SLO measures number of good requests/number of total requests during the interval. At any time, you can find the ratio of good requests to total requests for the interval up to the time stamp that you specify, and measure that ratio against the goal set in your SLO.

After you have created an SLO, you can retrieve error budget reports for it. An error budget is the amount of time or amount of requests that your application can be non-compliant with the SLO's goal, and still have your application meet the goal.

• For a period-based SLO, the error budget starts at a number defined by the highest number of periods that can fail to meet the threshold, while still meeting the overall goal. The remaining error budget decreases with every failed period that is recorded. The error budget within one interval can never increase.

  For example, an SLO with a threshold that 99.95% of requests must be completed under 2000ms every month translates to an error budget of 21.9 minutes of downtime per month.

• For a request-based SLO, the remaining error budget is dynamic and can increase or decrease, depending on the ratio of good requests to total requests.

For more information about SLOs, see Service level objectives (SLOs).

When you perform a CreateServiceLevelObjective operation, Application Signals creates the AWSServiceRoleForCloudWatchApplicationSignals service-linked role, if it doesn't already exist in your account. This service- linked role has the following permissions:

• xray:GetServiceGraph

• logs:StartQuery

• logs:GetQueryResults

• cloudwatch:GetMetricData

• cloudwatch:ListMetrics

• tag:GetResources

• autoscaling:DescribeAutoScalingGroups

Implementations

impl CreateServiceLevelObjectiveFluentBuilder

pub fn as_input(&self) -> &CreateServiceLevelObjectiveInputBuilder

Access the CreateServiceLevelObjective as a reference.

pub async fn send( self, ) -> Result<CreateServiceLevelObjectiveOutput, SdkError<CreateServiceLevelObjectiveError, HttpResponse>>

Sends the request and returns the response.

If an error occurs, an SdkError will be returned with additional details that can be matched against.

By default, any retryable failures will be retried twice. Retry behavior is configurable with the RetryConfig, which can be set when configuring the client.

pub fn customize( self, ) -> CustomizableOperation<CreateServiceLevelObjectiveOutput, CreateServiceLevelObjectiveError, Self>

Consumes this builder, creating a customizable operation that can be modified before being sent.

pub fn name(self, input: impl Into<String>) -> Self

A name for this SLO.

pub fn set_name(self, input: Option<String>) -> Self

A name for this SLO.

pub fn get_name(&self) -> &Option<String>

A name for this SLO.

pub fn description(self, input: impl Into<String>) -> Self

An optional description for this SLO.

pub fn set_description(self, input: Option<String>) -> Self

An optional description for this SLO.

pub fn get_description(&self) -> &Option<String>

An optional description for this SLO.

pub fn sli_config(self, input: ServiceLevelIndicatorConfig) -> Self

If this SLO is a period-based SLO, this structure defines the information about what performance metric this SLO will monitor.

You can't specify both RequestBasedSliConfig and SliConfig in the same operation.

pub fn set_sli_config(self, input: Option<ServiceLevelIndicatorConfig>) -> Self

If this SLO is a period-based SLO, this structure defines the information about what performance metric this SLO will monitor.

You can't specify both RequestBasedSliConfig and SliConfig in the same operation.

pub fn get_sli_config(&self) -> &Option<ServiceLevelIndicatorConfig>

If this SLO is a period-based SLO, this structure defines the information about what performance metric this SLO will monitor.

You can't specify both RequestBasedSliConfig and SliConfig in the same operation.

pub fn request_based_sli_config( self, input: RequestBasedServiceLevelIndicatorConfig, ) -> Self

If this SLO is a request-based SLO, this structure defines the information about what performance metric this SLO will monitor.

You can't specify both RequestBasedSliConfig and SliConfig in the same operation.

pub fn set_request_based_sli_config( self, input: Option<RequestBasedServiceLevelIndicatorConfig>, ) -> Self

If this SLO is a request-based SLO, this structure defines the information about what performance metric this SLO will monitor.

You can't specify both RequestBasedSliConfig and SliConfig in the same operation.

pub fn get_request_based_sli_config( &self, ) -> &Option<RequestBasedServiceLevelIndicatorConfig>

If this SLO is a request-based SLO, this structure defines the information about what performance metric this SLO will monitor.

You can't specify both RequestBasedSliConfig and SliConfig in the same operation.

pub fn goal(self, input: Goal) -> Self

This structure contains the attributes that determine the goal of the SLO.

pub fn set_goal(self, input: Option<Goal>) -> Self

This structure contains the attributes that determine the goal of the SLO.

pub fn get_goal(&self) -> &Option<Goal>

This structure contains the attributes that determine the goal of the SLO.

pub fn tags(self, input: Tag) -> Self

Appends an item to Tags.

To override the contents of this collection use set_tags.

A list of key-value pairs to associate with the SLO. You can associate as many as 50 tags with an SLO. To be able to associate tags with the SLO when you create the SLO, you must have the cloudwatch:TagResource permission.

Tags can help you organize and categorize your resources. You can also use them to scope user permissions by granting a user permission to access or change only resources with certain tag values.

pub fn set_tags(self, input: Option<Vec<Tag>>) -> Self

A list of key-value pairs to associate with the SLO. You can associate as many as 50 tags with an SLO. To be able to associate tags with the SLO when you create the SLO, you must have the cloudwatch:TagResource permission.

Tags can help you organize and categorize your resources. You can also use them to scope user permissions by granting a user permission to access or change only resources with certain tag values.

pub fn get_tags(&self) -> &Option<Vec<Tag>>

A list of key-value pairs to associate with the SLO. You can associate as many as 50 tags with an SLO. To be able to associate tags with the SLO when you create the SLO, you must have the cloudwatch:TagResource permission.

Tags can help you organize and categorize your resources. You can also use them to scope user permissions by granting a user permission to access or change only resources with certain tag values.

pub fn burn_rate_configurations(self, input: BurnRateConfiguration) -> Self

Appends an item to BurnRateConfigurations.

To override the contents of this collection use set_burn_rate_configurations.

Use this array to create burn rates 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.

pub fn set_burn_rate_configurations( self, input: Option<Vec<BurnRateConfiguration>>, ) -> Self

Use this array to create burn rates 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.

pub fn get_burn_rate_configurations( &self, ) -> &Option<Vec<BurnRateConfiguration>>

Use this array to create burn rates 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.

Trait Implementations

impl Clone for CreateServiceLevelObjectiveFluentBuilder

fn clone(&self) -> CreateServiceLevelObjectiveFluentBuilder

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for CreateServiceLevelObjectiveFluentBuilder

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.