Package-level declarations
Types
You don't have sufficient permissions to perform this action.
Base class for all service related exceptions thrown by the ApplicationSignals client
A structure that defines a filter for narrowing down results based on specific attribute values. This can be used to filter services by platform, environment, or other service characteristics.
A structure that contains information about an audit finding, which represents an automated analysis result about service behavior, performance issues, or potential problems identified through heuristic algorithms.
A structure that contains the result of an automated audit analysis, including the auditor name, description of findings, additional data, and severity level.
A structure that specifies the target entity for audit analysis, such as a service, SLO, service_operation, or canary.
A union structure that contains the specific entity information for different types of audit targets.
Parameters for targeted delete by ARN list.
Union type for batch delete target selection. Exactly one of the two modes must be specified.
Represents an error that occurred when attempting to delete a configuration.
Error codes for batch delete item-level failures.
Scope parameters for bulk delete by scope.
Represents a successfully deleted instrumentation configuration.
An array of structures, where each structure includes an error indicating that one of the requests in the array was not valid.
This object defines the length of the look-back window used to calculate one burn rate metric for this SLO. The burn rate measures how fast the service is consuming the error budget, relative to the attainment goal of the SLO. A burn rate of exactly 1 indicates that the SLO goal will be met exactly.
If the interval for this service level objective is a calendar interval, this structure contains the interval specifications.
A structure that contains identifying information for a CloudWatch Synthetics canary entity used in audit targeting.
A union that defines what data to capture when the instrumentation point is hit. Specify CodeCapture for code-level capture settings.
Guardrails that prevent instrumentation from impacting application performance by limiting how much data is captured.
A structure that contains information about a change event that occurred for a service, such as a deployment or configuration change.
Defines what data to capture for code-level instrumentation, including arguments, return values, stack traces, local variables, and safety limits.
Identifies a code location to instrument, including the programming language, code unit, class, method, file path, and optional line number.
Identifies a single operation to include in a composite SLI for a service-level SLO. Used as an element of the Components list in CompositeSliConfig.
This structure contains the configuration for a composite service level indicator (SLI) that aggregates metrics across multiple operations of a service for service-level SLOs.
This operation attempted to create a resource that already exists.
Identifies the dependency using the DependencyKeyAttributes and DependencyOperationName.
A structure that represents the dependency relationships relevant to an audit finding, containing nodes and edges that show how services and resources are connected.
A dimension is a name/value pair that is part of the identity of a metric. Because dimensions are part of the unique identifier for a metric, whenever you add a unique name/value pair to one of your metrics, you are creating a new variation of that metric. For example, many Amazon EC2 metrics publish InstanceId as a dimension name, and the actual instance ID as the value for that dimension.
The status of a delete request for an instrumentation configuration. The value is DELETED after a successful deletion.
The telemetry signal type for instrumentation.
The core SLO time window exclusion object that includes Window, StartTime, RecurrenceRule, and Reason.
A structure that defines how services should be grouped based on specific attributes. This includes the friendly name for the grouping, the source keys to derive values from, and an optional default value.
A structure that contains the complete grouping configuration for an account, including all defined grouping attributes and metadata about when it was last updated.
The full instrumentation configuration, including the instrumentation type, service, environment, signal type, location details, stable location hash, capture settings, filters, expiration, creation time, and ARN.
The status of an instrumentation configuration on a host.
The status of a single instrumentation configuration reported by an SDK instance.
An instrumentation configuration that omits service and environment because they are provided at a higher level, such as in a list response.
The reason why applying an instrumentation configuration failed.
A status event for an instrumentation configuration returned by GetInstrumentationConfigurationStatus. Events include the timestamp and, for errors, an error cause.
Type of instrumentation configuration
Union type for identifying an instrumentation configuration by code location or locationHash. Used in Get/Delete/GetStatus operations to allow flexible identification.
Use this structure to define a metric or metric math expression that you want to use as for a service level objective.
A structure that contains metric data queries and time range information that provides context for audit findings through relevant performance metrics.
This structure contains information about one CloudWatch metric associated with this entity discovered by Application Signals.
Identifies the metric source for SLOs on resources other than Application Signals services.
This structure defines the metric to be used as the service level indicator, along with the statistics, period, and unit.
This structure defines the metric that is used as the "good request" or "bad request" value for a request-based SLO. This value observed for the metric defined in TotalRequestCountMetric is divided by the number found for MonitoredRequestCountMetric to determine the percentage of successful requests that this SLO tracks.
The programming language of the instrumentation point. Java, Python, and JavaScript are currently supported.
The recurrence rule for the SLO time window exclusion .
This structure contains information about the performance metric that a request-based SLO monitors.
This structure specifies the information about the service and the performance metric that a request-based SLO is to monitor.
This structure contains the information about the metric that is used for a request-based SLO.
Use this structure to specify the information for the metric that a period-based SLO will monitor.
Resource not found.
If the interval for this SLO is a rolling interval, this structure contains the interval specifications.
Defines how operations are selected for a service-level SLO.
The strategy for selecting operations to include in a service-level SLO.
This structure contains information about one dependency of this service.
This structure contains information about a service dependent that was discovered by Application Signals. A dependent is an entity that invoked the specified service during the provided time range. Dependents include other services, CloudWatch Synthetics canaries, and clients that are instrumented with CloudWatch RUM app monitors.
A structure that contains identifying information for a service entity.
A structure that represents a logical grouping of services based on shared attributes such as business unit, environment, or entry point.
This structure contains information about the performance metric that a period-based SLO monitors.
This structure specifies the information about the service and the performance metric that a period-based SLO is to monitor.
This structure contains the information about the metric that is used for a period-based SLO.
Use this structure to specify the information for the metric that a period-based SLO will monitor.
A structure containing information about one service level objective (SLO) that has been created in Application Signals. Creating SLOs can help you ensure your services are performing to the level that you expect. SLOs help you set and track a specific target level for the reliability and availability of your applications and services. Each SLO uses a service level indicator (SLI), which is a key performance metric, to calculate how much underperformance can be tolerated before the goal that you set for the SLO is not achieved.
A structure containing an SLO budget report that you have requested.
A structure containing information about one error that occurred during a BatchGetServiceLevelObjectiveBudgetReport operation.
A structure that contains identifying information for a service level objective entity.
A structure that contains information about one service level objective (SLO) created in Application Signals.
This structure contains information about an operation discovered by Application Signals. An operation is a specific function performed by a service that was discovered by Application Signals, and is often an API that is called by an upstream dependent.
A structure that contains identifying information for a service operation entity.
This request exceeds a service quota.
A structure that contains information about the current state of a service, including its latest change events such as deployments and other state-changing activities.
This structure contains information about one of your services that was discovered by Application Signals
The request was throttled because of quota limits.
A status event that could not be processed by the service.
The reason an instrumentation status event could not be processed.
The resource is not valid.