Interface ApplicationSignalsAsyncClient

All Superinterfaces:
AutoCloseable, AwsClient, SdkAutoCloseable, SdkClient
@Generated("software.amazon.awssdk:codegen") @ThreadSafe public interface ApplicationSignalsAsyncClient extends AwsClient
Service client for accessing Amazon CloudWatch Application Signals asynchronously. This can be created using the static builder() method.The asynchronous client performs non-blocking I/O when configured with any SdkAsyncHttpClient supported in the SDK. However, full non-blocking is not guaranteed as the async client may perform blocking calls in some cases such as credentials retrieval and endpoint discovery as part of the async API call.

Use CloudWatch Application Signals for comprehensive observability of your cloud-based applications. It enables real-time service health dashboards and helps you track long-term performance trends against your business goals. The application-centric view provides you with unified visibility across your applications, services, and dependencies, so you can proactively monitor and efficiently triage any issues that may arise, ensuring optimal customer experience.

Application Signals provides the following benefits:

  • Automatically collect metrics and traces from your applications, and display key metrics such as call volume, availability, latency, faults, and errors.

  • Create and monitor service level objectives (SLOs).

  • See a map of your application topology that Application Signals automatically discovers, that gives you a visual representation of your applications, dependencies, and their connectivity.

Application Signals works with CloudWatch RUM, CloudWatch Synthetics canaries, and Amazon Web Services Service Catalog AppRegistry, to display your client pages, Synthetics canaries, and application names within dashboards and maps.

  • Field Details

  • Method Details

    • batchGetServiceLevelObjectiveBudgetReport

      default CompletableFuture<BatchGetServiceLevelObjectiveBudgetReportResponse> batchGetServiceLevelObjectiveBudgetReport(BatchGetServiceLevelObjectiveBudgetReportRequest batchGetServiceLevelObjectiveBudgetReportRequest)

      Use this operation to retrieve one or more service level objective (SLO) budget reports.

      An error budget is the amount of time or requests in an unhealthy state that your service can accumulate during an interval before your overall SLO budget health is breached and the SLO is considered to be unmet. For example, an SLO with a threshold of 99.95% and a monthly interval translates to an error budget of 21.9 minutes of downtime in a 30-day month.

      Budget reports include a health indicator, the attainment value, and remaining budget.

      For more information about SLO error budgets, see SLO concepts.

      Parameters:
      batchGetServiceLevelObjectiveBudgetReportRequest -
      Returns:
      A Java Future containing the result of the BatchGetServiceLevelObjectiveBudgetReport operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • batchGetServiceLevelObjectiveBudgetReport

      default CompletableFuture<BatchGetServiceLevelObjectiveBudgetReportResponse> batchGetServiceLevelObjectiveBudgetReport(Consumer<BatchGetServiceLevelObjectiveBudgetReportRequest.Builder> batchGetServiceLevelObjectiveBudgetReportRequest)

      Use this operation to retrieve one or more service level objective (SLO) budget reports.

      An error budget is the amount of time or requests in an unhealthy state that your service can accumulate during an interval before your overall SLO budget health is breached and the SLO is considered to be unmet. For example, an SLO with a threshold of 99.95% and a monthly interval translates to an error budget of 21.9 minutes of downtime in a 30-day month.

      Budget reports include a health indicator, the attainment value, and remaining budget.

      For more information about SLO error budgets, see SLO concepts.


      This is a convenience which creates an instance of the BatchGetServiceLevelObjectiveBudgetReportRequest.Builder avoiding the need to create one manually via BatchGetServiceLevelObjectiveBudgetReportRequest.builder()

      Parameters:
      batchGetServiceLevelObjectiveBudgetReportRequest - A Consumer that will call methods on BatchGetServiceLevelObjectiveBudgetReportRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the BatchGetServiceLevelObjectiveBudgetReport operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • batchUpdateExclusionWindows

      default CompletableFuture<BatchUpdateExclusionWindowsResponse> batchUpdateExclusionWindows(BatchUpdateExclusionWindowsRequest batchUpdateExclusionWindowsRequest)

      Add or remove time window exclusions for one or more Service Level Objectives (SLOs).

      Parameters:
      batchUpdateExclusionWindowsRequest -
      Returns:
      A Java Future containing the result of the BatchUpdateExclusionWindows operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ResourceNotFoundException Resource not found.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • batchUpdateExclusionWindows

      default CompletableFuture<BatchUpdateExclusionWindowsResponse> batchUpdateExclusionWindows(Consumer<BatchUpdateExclusionWindowsRequest.Builder> batchUpdateExclusionWindowsRequest)

      Add or remove time window exclusions for one or more Service Level Objectives (SLOs).


      This is a convenience which creates an instance of the BatchUpdateExclusionWindowsRequest.Builder avoiding the need to create one manually via BatchUpdateExclusionWindowsRequest.builder()

      Parameters:
      batchUpdateExclusionWindowsRequest - A Consumer that will call methods on BatchUpdateExclusionWindowsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the BatchUpdateExclusionWindows operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ResourceNotFoundException Resource not found.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createServiceLevelObjective

      default CompletableFuture<CreateServiceLevelObjectiveResponse> createServiceLevelObjective(CreateServiceLevelObjectiveRequest createServiceLevelObjectiveRequest)

      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

      Parameters:
      createServiceLevelObjectiveRequest -
      Returns:
      A Java Future containing the result of the CreateServiceLevelObjective operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • AccessDeniedException You don't have sufficient permissions to perform this action.
      • ServiceQuotaExceededException This request exceeds a service quota.
      • ConflictException This operation attempted to create a resource that already exists.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createServiceLevelObjective

      default CompletableFuture<CreateServiceLevelObjectiveResponse> createServiceLevelObjective(Consumer<CreateServiceLevelObjectiveRequest.Builder> createServiceLevelObjectiveRequest)

      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


      This is a convenience which creates an instance of the CreateServiceLevelObjectiveRequest.Builder avoiding the need to create one manually via CreateServiceLevelObjectiveRequest.builder()

      Parameters:
      createServiceLevelObjectiveRequest - A Consumer that will call methods on CreateServiceLevelObjectiveRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateServiceLevelObjective operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • AccessDeniedException You don't have sufficient permissions to perform this action.
      • ServiceQuotaExceededException This request exceeds a service quota.
      • ConflictException This operation attempted to create a resource that already exists.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteServiceLevelObjective

      default CompletableFuture<DeleteServiceLevelObjectiveResponse> deleteServiceLevelObjective(DeleteServiceLevelObjectiveRequest deleteServiceLevelObjectiveRequest)

      Deletes the specified service level objective.

      Parameters:
      deleteServiceLevelObjectiveRequest -
      Returns:
      A Java Future containing the result of the DeleteServiceLevelObjective operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ResourceNotFoundException Resource not found.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteServiceLevelObjective

      default CompletableFuture<DeleteServiceLevelObjectiveResponse> deleteServiceLevelObjective(Consumer<DeleteServiceLevelObjectiveRequest.Builder> deleteServiceLevelObjectiveRequest)

      Deletes the specified service level objective.


      This is a convenience which creates an instance of the DeleteServiceLevelObjectiveRequest.Builder avoiding the need to create one manually via DeleteServiceLevelObjectiveRequest.builder()

      Parameters:
      deleteServiceLevelObjectiveRequest - A Consumer that will call methods on DeleteServiceLevelObjectiveRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteServiceLevelObjective operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ResourceNotFoundException Resource not found.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getService

      default CompletableFuture<GetServiceResponse> getService(GetServiceRequest getServiceRequest)

      Returns information about a service discovered by Application Signals.

      Parameters:
      getServiceRequest -
      Returns:
      A Java Future containing the result of the GetService operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getService

      default CompletableFuture<GetServiceResponse> getService(Consumer<GetServiceRequest.Builder> getServiceRequest)

      Returns information about a service discovered by Application Signals.


      This is a convenience which creates an instance of the GetServiceRequest.Builder avoiding the need to create one manually via GetServiceRequest.builder()

      Parameters:
      getServiceRequest - A Consumer that will call methods on GetServiceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetService operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getServiceLevelObjective

      default CompletableFuture<GetServiceLevelObjectiveResponse> getServiceLevelObjective(GetServiceLevelObjectiveRequest getServiceLevelObjectiveRequest)

      Returns information about one SLO created in the account.

      Parameters:
      getServiceLevelObjectiveRequest -
      Returns:
      A Java Future containing the result of the GetServiceLevelObjective operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ResourceNotFoundException Resource not found.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getServiceLevelObjective

      default CompletableFuture<GetServiceLevelObjectiveResponse> getServiceLevelObjective(Consumer<GetServiceLevelObjectiveRequest.Builder> getServiceLevelObjectiveRequest)

      Returns information about one SLO created in the account.


      This is a convenience which creates an instance of the GetServiceLevelObjectiveRequest.Builder avoiding the need to create one manually via GetServiceLevelObjectiveRequest.builder()

      Parameters:
      getServiceLevelObjectiveRequest - A Consumer that will call methods on GetServiceLevelObjectiveRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetServiceLevelObjective operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ResourceNotFoundException Resource not found.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceDependencies

      default CompletableFuture<ListServiceDependenciesResponse> listServiceDependencies(ListServiceDependenciesRequest listServiceDependenciesRequest)

      Returns a list of service dependencies of the service that you specify. A dependency is an infrastructure component that an operation of this service connects with. Dependencies can include Amazon Web Services services, Amazon Web Services resources, and third-party services.

      Parameters:
      listServiceDependenciesRequest -
      Returns:
      A Java Future containing the result of the ListServiceDependencies operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceDependencies

      default CompletableFuture<ListServiceDependenciesResponse> listServiceDependencies(Consumer<ListServiceDependenciesRequest.Builder> listServiceDependenciesRequest)

      Returns a list of service dependencies of the service that you specify. A dependency is an infrastructure component that an operation of this service connects with. Dependencies can include Amazon Web Services services, Amazon Web Services resources, and third-party services.


      This is a convenience which creates an instance of the ListServiceDependenciesRequest.Builder avoiding the need to create one manually via ListServiceDependenciesRequest.builder()

      Parameters:
      listServiceDependenciesRequest - A Consumer that will call methods on ListServiceDependenciesRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListServiceDependencies operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceDependenciesPaginator

      default ListServiceDependenciesPublisher listServiceDependenciesPaginator(ListServiceDependenciesRequest listServiceDependenciesRequest)

      This is a variant of listServiceDependencies(software.amazon.awssdk.services.applicationsignals.model.ListServiceDependenciesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceDependenciesPublisher publisher = client.listServiceDependenciesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceDependenciesPublisher publisher = client.listServiceDependenciesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.applicationsignals.model.ListServiceDependenciesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.applicationsignals.model.ListServiceDependenciesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of MaxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listServiceDependencies(software.amazon.awssdk.services.applicationsignals.model.ListServiceDependenciesRequest) operation.

      Parameters:
      listServiceDependenciesRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceDependenciesPaginator

      default ListServiceDependenciesPublisher listServiceDependenciesPaginator(Consumer<ListServiceDependenciesRequest.Builder> listServiceDependenciesRequest)

      This is a variant of listServiceDependencies(software.amazon.awssdk.services.applicationsignals.model.ListServiceDependenciesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceDependenciesPublisher publisher = client.listServiceDependenciesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceDependenciesPublisher publisher = client.listServiceDependenciesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.applicationsignals.model.ListServiceDependenciesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.applicationsignals.model.ListServiceDependenciesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of MaxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listServiceDependencies(software.amazon.awssdk.services.applicationsignals.model.ListServiceDependenciesRequest) operation.


      This is a convenience which creates an instance of the ListServiceDependenciesRequest.Builder avoiding the need to create one manually via ListServiceDependenciesRequest.builder()

      Parameters:
      listServiceDependenciesRequest - A Consumer that will call methods on ListServiceDependenciesRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceDependents

      default CompletableFuture<ListServiceDependentsResponse> listServiceDependents(ListServiceDependentsRequest listServiceDependentsRequest)

      Returns the list of dependents 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.

      Parameters:
      listServiceDependentsRequest -
      Returns:
      A Java Future containing the result of the ListServiceDependents operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceDependents

      default CompletableFuture<ListServiceDependentsResponse> listServiceDependents(Consumer<ListServiceDependentsRequest.Builder> listServiceDependentsRequest)

      Returns the list of dependents 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 is a convenience which creates an instance of the ListServiceDependentsRequest.Builder avoiding the need to create one manually via ListServiceDependentsRequest.builder()

      Parameters:
      listServiceDependentsRequest - A Consumer that will call methods on ListServiceDependentsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListServiceDependents operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceDependentsPaginator

      default ListServiceDependentsPublisher listServiceDependentsPaginator(ListServiceDependentsRequest listServiceDependentsRequest)

      This is a variant of listServiceDependents(software.amazon.awssdk.services.applicationsignals.model.ListServiceDependentsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceDependentsPublisher publisher = client.listServiceDependentsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceDependentsPublisher publisher = client.listServiceDependentsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.applicationsignals.model.ListServiceDependentsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.applicationsignals.model.ListServiceDependentsResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of MaxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listServiceDependents(software.amazon.awssdk.services.applicationsignals.model.ListServiceDependentsRequest) operation.

      Parameters:
      listServiceDependentsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceDependentsPaginator

      default ListServiceDependentsPublisher listServiceDependentsPaginator(Consumer<ListServiceDependentsRequest.Builder> listServiceDependentsRequest)

      This is a variant of listServiceDependents(software.amazon.awssdk.services.applicationsignals.model.ListServiceDependentsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceDependentsPublisher publisher = client.listServiceDependentsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceDependentsPublisher publisher = client.listServiceDependentsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.applicationsignals.model.ListServiceDependentsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.applicationsignals.model.ListServiceDependentsResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of MaxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listServiceDependents(software.amazon.awssdk.services.applicationsignals.model.ListServiceDependentsRequest) operation.


      This is a convenience which creates an instance of the ListServiceDependentsRequest.Builder avoiding the need to create one manually via ListServiceDependentsRequest.builder()

      Parameters:
      listServiceDependentsRequest - A Consumer that will call methods on ListServiceDependentsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceLevelObjectiveExclusionWindows

      default CompletableFuture<ListServiceLevelObjectiveExclusionWindowsResponse> listServiceLevelObjectiveExclusionWindows(ListServiceLevelObjectiveExclusionWindowsRequest listServiceLevelObjectiveExclusionWindowsRequest)

      Retrieves all exclusion windows configured for a specific SLO.

      Parameters:
      listServiceLevelObjectiveExclusionWindowsRequest -
      Returns:
      A Java Future containing the result of the ListServiceLevelObjectiveExclusionWindows operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ResourceNotFoundException Resource not found.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceLevelObjectiveExclusionWindows

      default CompletableFuture<ListServiceLevelObjectiveExclusionWindowsResponse> listServiceLevelObjectiveExclusionWindows(Consumer<ListServiceLevelObjectiveExclusionWindowsRequest.Builder> listServiceLevelObjectiveExclusionWindowsRequest)

      Retrieves all exclusion windows configured for a specific SLO.


      This is a convenience which creates an instance of the ListServiceLevelObjectiveExclusionWindowsRequest.Builder avoiding the need to create one manually via ListServiceLevelObjectiveExclusionWindowsRequest.builder()

      Parameters:
      listServiceLevelObjectiveExclusionWindowsRequest - A Consumer that will call methods on ListServiceLevelObjectiveExclusionWindowsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListServiceLevelObjectiveExclusionWindows operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ResourceNotFoundException Resource not found.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceLevelObjectiveExclusionWindowsPaginator

      default ListServiceLevelObjectiveExclusionWindowsPublisher listServiceLevelObjectiveExclusionWindowsPaginator(ListServiceLevelObjectiveExclusionWindowsRequest listServiceLevelObjectiveExclusionWindowsRequest)

      This is a variant of listServiceLevelObjectiveExclusionWindows(software.amazon.awssdk.services.applicationsignals.model.ListServiceLevelObjectiveExclusionWindowsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceLevelObjectiveExclusionWindowsPublisher publisher = client.listServiceLevelObjectiveExclusionWindowsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceLevelObjectiveExclusionWindowsPublisher publisher = client.listServiceLevelObjectiveExclusionWindowsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.applicationsignals.model.ListServiceLevelObjectiveExclusionWindowsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.applicationsignals.model.ListServiceLevelObjectiveExclusionWindowsResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of MaxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listServiceLevelObjectiveExclusionWindows(software.amazon.awssdk.services.applicationsignals.model.ListServiceLevelObjectiveExclusionWindowsRequest) operation.

      Parameters:
      listServiceLevelObjectiveExclusionWindowsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ResourceNotFoundException Resource not found.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceLevelObjectiveExclusionWindowsPaginator

      default ListServiceLevelObjectiveExclusionWindowsPublisher listServiceLevelObjectiveExclusionWindowsPaginator(Consumer<ListServiceLevelObjectiveExclusionWindowsRequest.Builder> listServiceLevelObjectiveExclusionWindowsRequest)

      This is a variant of listServiceLevelObjectiveExclusionWindows(software.amazon.awssdk.services.applicationsignals.model.ListServiceLevelObjectiveExclusionWindowsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceLevelObjectiveExclusionWindowsPublisher publisher = client.listServiceLevelObjectiveExclusionWindowsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceLevelObjectiveExclusionWindowsPublisher publisher = client.listServiceLevelObjectiveExclusionWindowsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.applicationsignals.model.ListServiceLevelObjectiveExclusionWindowsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.applicationsignals.model.ListServiceLevelObjectiveExclusionWindowsResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of MaxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listServiceLevelObjectiveExclusionWindows(software.amazon.awssdk.services.applicationsignals.model.ListServiceLevelObjectiveExclusionWindowsRequest) operation.


      This is a convenience which creates an instance of the ListServiceLevelObjectiveExclusionWindowsRequest.Builder avoiding the need to create one manually via ListServiceLevelObjectiveExclusionWindowsRequest.builder()

      Parameters:
      listServiceLevelObjectiveExclusionWindowsRequest - A Consumer that will call methods on ListServiceLevelObjectiveExclusionWindowsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ResourceNotFoundException Resource not found.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceLevelObjectives

      default CompletableFuture<ListServiceLevelObjectivesResponse> listServiceLevelObjectives(ListServiceLevelObjectivesRequest listServiceLevelObjectivesRequest)

      Returns a list of SLOs created in this account.

      Parameters:
      listServiceLevelObjectivesRequest -
      Returns:
      A Java Future containing the result of the ListServiceLevelObjectives operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceLevelObjectives

      default CompletableFuture<ListServiceLevelObjectivesResponse> listServiceLevelObjectives(Consumer<ListServiceLevelObjectivesRequest.Builder> listServiceLevelObjectivesRequest)

      Returns a list of SLOs created in this account.


      This is a convenience which creates an instance of the ListServiceLevelObjectivesRequest.Builder avoiding the need to create one manually via ListServiceLevelObjectivesRequest.builder()

      Parameters:
      listServiceLevelObjectivesRequest - A Consumer that will call methods on ListServiceLevelObjectivesRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListServiceLevelObjectives operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceLevelObjectivesPaginator

      default ListServiceLevelObjectivesPublisher listServiceLevelObjectivesPaginator(ListServiceLevelObjectivesRequest listServiceLevelObjectivesRequest)

      This is a variant of listServiceLevelObjectives(software.amazon.awssdk.services.applicationsignals.model.ListServiceLevelObjectivesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceLevelObjectivesPublisher publisher = client.listServiceLevelObjectivesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceLevelObjectivesPublisher publisher = client.listServiceLevelObjectivesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.applicationsignals.model.ListServiceLevelObjectivesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.applicationsignals.model.ListServiceLevelObjectivesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of MaxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listServiceLevelObjectives(software.amazon.awssdk.services.applicationsignals.model.ListServiceLevelObjectivesRequest) operation.

      Parameters:
      listServiceLevelObjectivesRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceLevelObjectivesPaginator

      default ListServiceLevelObjectivesPublisher listServiceLevelObjectivesPaginator(Consumer<ListServiceLevelObjectivesRequest.Builder> listServiceLevelObjectivesRequest)

      This is a variant of listServiceLevelObjectives(software.amazon.awssdk.services.applicationsignals.model.ListServiceLevelObjectivesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceLevelObjectivesPublisher publisher = client.listServiceLevelObjectivesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceLevelObjectivesPublisher publisher = client.listServiceLevelObjectivesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.applicationsignals.model.ListServiceLevelObjectivesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.applicationsignals.model.ListServiceLevelObjectivesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of MaxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listServiceLevelObjectives(software.amazon.awssdk.services.applicationsignals.model.ListServiceLevelObjectivesRequest) operation.


      This is a convenience which creates an instance of the ListServiceLevelObjectivesRequest.Builder avoiding the need to create one manually via ListServiceLevelObjectivesRequest.builder()

      Parameters:
      listServiceLevelObjectivesRequest - A Consumer that will call methods on ListServiceLevelObjectivesRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceOperations

      default CompletableFuture<ListServiceOperationsResponse> listServiceOperations(ListServiceOperationsRequest listServiceOperationsRequest)

      Returns a list of the operations of this service that have been discovered by Application Signals. Only the operations that were invoked during the specified time range are returned.

      Parameters:
      listServiceOperationsRequest -
      Returns:
      A Java Future containing the result of the ListServiceOperations operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceOperations

      default CompletableFuture<ListServiceOperationsResponse> listServiceOperations(Consumer<ListServiceOperationsRequest.Builder> listServiceOperationsRequest)

      Returns a list of the operations of this service that have been discovered by Application Signals. Only the operations that were invoked during the specified time range are returned.


      This is a convenience which creates an instance of the ListServiceOperationsRequest.Builder avoiding the need to create one manually via ListServiceOperationsRequest.builder()

      Parameters:
      listServiceOperationsRequest - A Consumer that will call methods on ListServiceOperationsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListServiceOperations operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceOperationsPaginator

      default ListServiceOperationsPublisher listServiceOperationsPaginator(ListServiceOperationsRequest listServiceOperationsRequest)

      This is a variant of listServiceOperations(software.amazon.awssdk.services.applicationsignals.model.ListServiceOperationsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceOperationsPublisher publisher = client.listServiceOperationsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceOperationsPublisher publisher = client.listServiceOperationsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.applicationsignals.model.ListServiceOperationsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.applicationsignals.model.ListServiceOperationsResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of MaxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listServiceOperations(software.amazon.awssdk.services.applicationsignals.model.ListServiceOperationsRequest) operation.

      Parameters:
      listServiceOperationsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServiceOperationsPaginator

      default ListServiceOperationsPublisher listServiceOperationsPaginator(Consumer<ListServiceOperationsRequest.Builder> listServiceOperationsRequest)

      This is a variant of listServiceOperations(software.amazon.awssdk.services.applicationsignals.model.ListServiceOperationsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceOperationsPublisher publisher = client.listServiceOperationsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServiceOperationsPublisher publisher = client.listServiceOperationsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.applicationsignals.model.ListServiceOperationsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.applicationsignals.model.ListServiceOperationsResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of MaxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listServiceOperations(software.amazon.awssdk.services.applicationsignals.model.ListServiceOperationsRequest) operation.


      This is a convenience which creates an instance of the ListServiceOperationsRequest.Builder avoiding the need to create one manually via ListServiceOperationsRequest.builder()

      Parameters:
      listServiceOperationsRequest - A Consumer that will call methods on ListServiceOperationsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServices

      default CompletableFuture<ListServicesResponse> listServices(ListServicesRequest listServicesRequest)

      Returns a list of services that have been discovered by Application Signals. A service represents a minimum logical and transactional unit that completes a business function. Services are discovered through Application Signals instrumentation.

      Parameters:
      listServicesRequest -
      Returns:
      A Java Future containing the result of the ListServices operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServices

      default CompletableFuture<ListServicesResponse> listServices(Consumer<ListServicesRequest.Builder> listServicesRequest)

      Returns a list of services that have been discovered by Application Signals. A service represents a minimum logical and transactional unit that completes a business function. Services are discovered through Application Signals instrumentation.


      This is a convenience which creates an instance of the ListServicesRequest.Builder avoiding the need to create one manually via ListServicesRequest.builder()

      Parameters:
      listServicesRequest - A Consumer that will call methods on ListServicesRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListServices operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServicesPaginator

      default ListServicesPublisher listServicesPaginator(ListServicesRequest listServicesRequest)

      This is a variant of listServices(software.amazon.awssdk.services.applicationsignals.model.ListServicesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServicesPublisher publisher = client.listServicesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServicesPublisher publisher = client.listServicesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.applicationsignals.model.ListServicesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.applicationsignals.model.ListServicesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of MaxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listServices(software.amazon.awssdk.services.applicationsignals.model.ListServicesRequest) operation.

      Parameters:
      listServicesRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listServicesPaginator

      default ListServicesPublisher listServicesPaginator(Consumer<ListServicesRequest.Builder> listServicesRequest)

      This is a variant of listServices(software.amazon.awssdk.services.applicationsignals.model.ListServicesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServicesPublisher publisher = client.listServicesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.applicationsignals.paginators.ListServicesPublisher publisher = client.listServicesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.applicationsignals.model.ListServicesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.applicationsignals.model.ListServicesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of MaxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listServices(software.amazon.awssdk.services.applicationsignals.model.ListServicesRequest) operation.


      This is a convenience which creates an instance of the ListServicesRequest.Builder avoiding the need to create one manually via ListServicesRequest.builder()

      Parameters:
      listServicesRequest - A Consumer that will call methods on ListServicesRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listTagsForResource

      default CompletableFuture<ListTagsForResourceResponse> listTagsForResource(ListTagsForResourceRequest listTagsForResourceRequest)

      Displays the tags associated with a CloudWatch resource. Tags can be assigned to service level objectives.

      Parameters:
      listTagsForResourceRequest -
      Returns:
      A Java Future containing the result of the ListTagsForResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ResourceNotFoundException Resource not found.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listTagsForResource

      default CompletableFuture<ListTagsForResourceResponse> listTagsForResource(Consumer<ListTagsForResourceRequest.Builder> listTagsForResourceRequest)

      Displays the tags associated with a CloudWatch resource. Tags can be assigned to service level objectives.


      This is a convenience which creates an instance of the ListTagsForResourceRequest.Builder avoiding the need to create one manually via ListTagsForResourceRequest.builder()

      Parameters:
      listTagsForResourceRequest - A Consumer that will call methods on ListTagsForResourceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListTagsForResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ResourceNotFoundException Resource not found.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • startDiscovery

      default CompletableFuture<StartDiscoveryResponse> startDiscovery(StartDiscoveryRequest startDiscoveryRequest)

      Enables this Amazon Web Services account to be able to use CloudWatch Application Signals by creating the AWSServiceRoleForCloudWatchApplicationSignals service-linked role. This service- linked role has the following permissions:

      • xray:GetServiceGraph

      • logs:StartQuery

      • logs:GetQueryResults

      • cloudwatch:GetMetricData

      • cloudwatch:ListMetrics

      • tag:GetResources

      • autoscaling:DescribeAutoScalingGroups

      After completing this step, you still need to instrument your Java and Python applications to send data to Application Signals. For more information, see Enabling Application Signals.

      Parameters:
      startDiscoveryRequest -
      Returns:
      A Java Future containing the result of the StartDiscovery operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • AccessDeniedException You don't have sufficient permissions to perform this action.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • startDiscovery

      default CompletableFuture<StartDiscoveryResponse> startDiscovery(Consumer<StartDiscoveryRequest.Builder> startDiscoveryRequest)

      Enables this Amazon Web Services account to be able to use CloudWatch Application Signals by creating the AWSServiceRoleForCloudWatchApplicationSignals service-linked role. This service- linked role has the following permissions:

      • xray:GetServiceGraph

      • logs:StartQuery

      • logs:GetQueryResults

      • cloudwatch:GetMetricData

      • cloudwatch:ListMetrics

      • tag:GetResources

      • autoscaling:DescribeAutoScalingGroups

      After completing this step, you still need to instrument your Java and Python applications to send data to Application Signals. For more information, see Enabling Application Signals.


      This is a convenience which creates an instance of the StartDiscoveryRequest.Builder avoiding the need to create one manually via StartDiscoveryRequest.builder()

      Parameters:
      startDiscoveryRequest - A Consumer that will call methods on StartDiscoveryRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the StartDiscovery operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ThrottlingException The request was throttled because of quota limits.
      • AccessDeniedException You don't have sufficient permissions to perform this action.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • tagResource

      default CompletableFuture<TagResourceResponse> tagResource(TagResourceRequest tagResourceRequest)

      Assigns one or more tags (key-value pairs) to the specified CloudWatch resource, such as a service level objective.

      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.

      Tags don't have any semantic meaning to Amazon Web Services and are interpreted strictly as strings of characters.

      You can use the TagResource action with an alarm that already has tags. If you specify a new tag key for the alarm, this tag is appended to the list of tags associated with the alarm. If you specify a tag key that is already associated with the alarm, the new tag value that you specify replaces the previous value for that tag.

      You can associate as many as 50 tags with a CloudWatch resource.

      Parameters:
      tagResourceRequest -
      Returns:
      A Java Future containing the result of the TagResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ResourceNotFoundException Resource not found.
      • ThrottlingException The request was throttled because of quota limits.
      • ServiceQuotaExceededException This request exceeds a service quota.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • tagResource

      default CompletableFuture<TagResourceResponse> tagResource(Consumer<TagResourceRequest.Builder> tagResourceRequest)

      Assigns one or more tags (key-value pairs) to the specified CloudWatch resource, such as a service level objective.

      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.

      Tags don't have any semantic meaning to Amazon Web Services and are interpreted strictly as strings of characters.

      You can use the TagResource action with an alarm that already has tags. If you specify a new tag key for the alarm, this tag is appended to the list of tags associated with the alarm. If you specify a tag key that is already associated with the alarm, the new tag value that you specify replaces the previous value for that tag.

      You can associate as many as 50 tags with a CloudWatch resource.


      This is a convenience which creates an instance of the TagResourceRequest.Builder avoiding the need to create one manually via TagResourceRequest.builder()

      Parameters:
      tagResourceRequest - A Consumer that will call methods on TagResourceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the TagResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ResourceNotFoundException Resource not found.
      • ThrottlingException The request was throttled because of quota limits.
      • ServiceQuotaExceededException This request exceeds a service quota.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • untagResource

      default CompletableFuture<UntagResourceResponse> untagResource(UntagResourceRequest untagResourceRequest)

      Removes one or more tags from the specified resource.

      Parameters:
      untagResourceRequest -
      Returns:
      A Java Future containing the result of the UntagResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ResourceNotFoundException Resource not found.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • untagResource

      default CompletableFuture<UntagResourceResponse> untagResource(Consumer<UntagResourceRequest.Builder> untagResourceRequest)

      Removes one or more tags from the specified resource.


      This is a convenience which creates an instance of the UntagResourceRequest.Builder avoiding the need to create one manually via UntagResourceRequest.builder()

      Parameters:
      untagResourceRequest - A Consumer that will call methods on UntagResourceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UntagResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ResourceNotFoundException Resource not found.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateServiceLevelObjective

      default CompletableFuture<UpdateServiceLevelObjectiveResponse> updateServiceLevelObjective(UpdateServiceLevelObjectiveRequest updateServiceLevelObjectiveRequest)

      Updates an existing service level objective (SLO). If you omit parameters, the previous values of those parameters are retained.

      You cannot change from a period-based SLO to a request-based SLO, or change from a request-based SLO to a period-based SLO.

      Parameters:
      updateServiceLevelObjectiveRequest -
      Returns:
      A Java Future containing the result of the UpdateServiceLevelObjective operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ResourceNotFoundException Resource not found.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateServiceLevelObjective

      default CompletableFuture<UpdateServiceLevelObjectiveResponse> updateServiceLevelObjective(Consumer<UpdateServiceLevelObjectiveRequest.Builder> updateServiceLevelObjectiveRequest)

      Updates an existing service level objective (SLO). If you omit parameters, the previous values of those parameters are retained.

      You cannot change from a period-based SLO to a request-based SLO, or change from a request-based SLO to a period-based SLO.


      This is a convenience which creates an instance of the UpdateServiceLevelObjectiveRequest.Builder avoiding the need to create one manually via UpdateServiceLevelObjectiveRequest.builder()

      Parameters:
      updateServiceLevelObjectiveRequest - A Consumer that will call methods on UpdateServiceLevelObjectiveRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UpdateServiceLevelObjective operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ValidationException The resource is not valid.
      • ResourceNotFoundException Resource not found.
      • ThrottlingException The request was throttled because of quota limits.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • ApplicationSignalsException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • serviceClientConfiguration

      default ApplicationSignalsServiceClientConfiguration serviceClientConfiguration()
      Description copied from interface: SdkClient
      The SDK service client configuration exposes client settings to the user, e.g., ClientOverrideConfiguration
      Specified by:
      serviceClientConfiguration in interface AwsClient
      Specified by:
      serviceClientConfiguration in interface SdkClient
      Returns:
      SdkServiceClientConfiguration

    • create

      static ApplicationSignalsAsyncClient create()
      Create a ApplicationSignalsAsyncClient with the region loaded from the DefaultAwsRegionProviderChain and credentials loaded from the DefaultCredentialsProvider.

    • builder

      static ApplicationSignalsAsyncClientBuilder builder()
      Create a builder that can be used to configure and create a ApplicationSignalsAsyncClient.