@aws-sdk/client-application-signals 3.936.0 → 3.937.0

package/dist-types/commands/ListGroupingAttributeDefinitionsCommand.d.ts

@@ -27,7 +27,7 @@ declare const ListGroupingAttributeDefinitionsCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Retrieves the available grouping attribute definitions that can be used to create grouping configurations. These definitions specify the attributes and rules available for organizing services.</p> <p>Use this operation to discover what grouping options are available before creating or updating grouping configurations.</p>
+ * <p>Returns the current grouping configuration for this account, including all custom grouping attribute definitions that have been configured. These definitions determine how services are logically grouped based on telemetry attributes, Amazon Web Services tags, or predefined mappings.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -38,6 +38,8 @@ declare const ListGroupingAttributeDefinitionsCommand_base: {
  * const client = new ApplicationSignalsClient(config);
  * const input = { // ListGroupingAttributeDefinitionsInput
  *   NextToken: "STRING_VALUE",
+ *   AwsAccountId: "STRING_VALUE",
+ *   IncludeLinkedAccounts: true || false,
  * };
  * const command = new ListGroupingAttributeDefinitionsCommand(input);
  * const response = await client.send(command);

package/dist-types/commands/ListServiceStatesCommand.d.ts

@@ -27,7 +27,7 @@ declare const ListServiceStatesCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Retrieves the current state information for services monitored by Application Signals. Service states include health status, recent change events, and other operational metadata.</p> <p>You can filter results by time range, AWS account, and service attributes to focus on specific services or time periods. This operation supports pagination and can include data from linked accounts.</p>
+ * <p>Returns information about the last deployment and other change states of services. This API provides visibility into recent changes that may have affected service performance, helping with troubleshooting and change correlation.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -78,7 +78,7 @@ declare const ListServiceStatesCommand_base: {
  * //           Entity: { // required
  * //             "<keys>": "STRING_VALUE",
  * //           },
- * //           ChangeEventType: "DEPLOYMENT", // required
+ * //           ChangeEventType: "DEPLOYMENT" || "CONFIGURATION", // required
  * //           EventId: "STRING_VALUE", // required
  * //           UserName: "STRING_VALUE",
  * //           EventName: "STRING_VALUE",

package/dist-types/commands/PutGroupingConfigurationCommand.d.ts

@@ -27,7 +27,7 @@ declare const PutGroupingConfigurationCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates or updates a grouping configuration that defines how services are organized and grouped in Application Signals dashboards and service maps.</p> <p>Grouping configurations allow you to logically organize services based on attributes such as environment, team ownership, or business function, making it easier to monitor and manage related services together.</p>
+ * <p>Creates or updates the grouping configuration for this account. This operation allows you to define custom grouping attributes that determine how services are logically grouped based on telemetry attributes, Amazon Web Services tags, or predefined mappings. These grouping attributes can then be used to organize and filter services in the Application Signals console and APIs.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/StartDiscoveryCommand.d.ts

@@ -27,7 +27,7 @@ declare const StartDiscoveryCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Enables this Amazon Web Services account to be able to use CloudWatch Application Signals by creating the <i>AWSServiceRoleForCloudWatchApplicationSignals</i> service-linked role. This service- linked role has the following permissions:</p> <ul> <li> <p> <code>xray:GetServiceGraph</code> </p> </li> <li> <p> <code>logs:StartQuery</code> </p> </li> <li> <p> <code>logs:GetQueryResults</code> </p> </li> <li> <p> <code>cloudwatch:GetMetricData</code> </p> </li> <li> <p> <code>cloudwatch:ListMetrics</code> </p> </li> <li> <p> <code>tag:GetResources</code> </p> </li> <li> <p> <code>autoscaling:DescribeAutoScalingGroups</code> </p> </li> </ul> <p>After completing this step, you still need to instrument your Java and Python applications to send data to Application Signals. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Application-Signals-Enable.html"> Enabling Application Signals</a>.</p>
+ * <p>Enables this Amazon Web Services account to be able to use CloudWatch Application Signals by creating the <i>AWSServiceRoleForCloudWatchApplicationSignals</i> service-linked role. This service- linked role has the following permissions:</p> <ul> <li> <p> <code>xray:GetServiceGraph</code> </p> </li> <li> <p> <code>logs:StartQuery</code> </p> </li> <li> <p> <code>logs:GetQueryResults</code> </p> </li> <li> <p> <code>cloudwatch:GetMetricData</code> </p> </li> <li> <p> <code>cloudwatch:ListMetrics</code> </p> </li> <li> <p> <code>tag:GetResources</code> </p> </li> <li> <p> <code>autoscaling:DescribeAutoScalingGroups</code> </p> </li> </ul> <p>A service-linked CloudTrail event channel is created to process CloudTrail events and return change event information. This includes last deployment time, userName, eventName, and other event metadata.</p> <p>After completing this step, you still need to instrument your Java and Python applications to send data to Application Signals. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Application-Signals-Enable.html"> Enabling Application Signals</a>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/index.d.ts

@@ -6,6 +6,7 @@ export * from "./DeleteServiceLevelObjectiveCommand";
 export * from "./GetServiceCommand";
 export * from "./GetServiceLevelObjectiveCommand";
 export * from "./ListAuditFindingsCommand";
+export * from "./ListEntityEventsCommand";
 export * from "./ListGroupingAttributeDefinitionsCommand";
 export * from "./ListServiceDependenciesCommand";
 export * from "./ListServiceDependentsCommand";

package/dist-types/models/enums.d.ts

@@ -101,6 +101,18 @@ export declare const StandardUnit: {
  * @public
  */
 export type StandardUnit = (typeof StandardUnit)[keyof typeof StandardUnit];
+/**
+ * @public
+ * @enum
+ */
+export declare const DetailLevel: {
+    readonly BRIEF: "BRIEF";
+    readonly DETAILED: "DETAILED";
+};
+/**
+ * @public
+ */
+export type DetailLevel = (typeof DetailLevel)[keyof typeof DetailLevel];
 /**
  * @public
  * @enum
@@ -133,6 +145,7 @@ export type ConnectionType = (typeof ConnectionType)[keyof typeof ConnectionType
  * @enum
  */
 export declare const ChangeEventType: {
+    readonly CONFIGURATION: "CONFIGURATION";
     readonly DEPLOYMENT: "DEPLOYMENT";
 };
 /**