Skip to content

Commit 11f880f

Browse files
author
AWS
committed
Amazon CloudWatch Application Signals Update: CloudWatch Application Signals now supports application logs correlation with traces and operational health metrics of applications running on EC2 instances. Users can view the most relevant telemetry to troubleshoot application health anomalies such as spikes in latency, errors, and availability.
1 parent 8b29b1b commit 11f880f

File tree

2 files changed

+41
-22
lines changed

2 files changed

+41
-22
lines changed

‎.changes/next-release/feature-AmazonCloudWatchApplicationSignals-d6d0a53.json

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
{
2+
"type": "feature",
3+
"category": "Amazon CloudWatch Application Signals",
4+
"contributor": "",
5+
"description": "CloudWatch Application Signals now supports application logs correlation with traces and operational health metrics of applications running on EC2 instances. Users can view the most relevant telemetry to troubleshoot application health anomalies such as spikes in latency, errors, and availability."
6+
}

‎services/applicationsignals/src/main/resources/codegen-resources/service-2.json

Lines changed: 35 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
"version":"2.0",
33
"metadata":{
44
"apiVersion":"2024-04-15",
5+
"auth":["aws.auth#sigv4"],
56
"endpointPrefix":"application-signals",
67
"protocol":"rest-json",
78
"protocols":["rest-json"],
@@ -486,13 +487,13 @@
486487
"members":{
487488
"StartTime":{
488489
"shape":"Timestamp",
489-
"documentation":"<p>The start of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p>",
490+
"documentation":"<p>The start of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p> <p>Your requested start time will be rounded to the nearest hour.</p>",
490491
"location":"querystring",
491492
"locationName":"StartTime"
492493
},
493494
"EndTime":{
494495
"shape":"Timestamp",
495-
"documentation":"<p>The end of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p>",
496+
"documentation":"<p>The end of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p> <p>Your requested start time will be rounded to the nearest hour.</p>",
496497
"location":"querystring",
497498
"locationName":"EndTime"
498499
},
@@ -538,11 +539,15 @@
538539
},
539540
"StartTime":{
540541
"shape":"Timestamp",
541-
"documentation":"<p>The start time of the data included in the response. In a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code>.</p>"
542+
"documentation":"<p>The start time of the data included in the response. In a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code>.</p> <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because it was rounded to the nearest hour.</p>"
542543
},
543544
"EndTime":{
544545
"shape":"Timestamp",
545-
"documentation":"<p>The end time of the data included in the response. In a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code>.</p>"
546+
"documentation":"<p>The end time of the data included in the response. In a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code>.</p> <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because it was rounded to the nearest hour.</p>"
547+
},
548+
"LogGroupReferences":{
549+
"shape":"LogGroupReferences",
550+
"documentation":"<p>An array of string-to-string maps that each contain information about one log group associated with this service. Each string-to-string map includes the following fields:</p> <ul> <li> <p> <code>\"Type\": \"AWS::Resource\"</code> </p> </li> <li> <p> <code>\"ResourceType\": \"AWS::Logs::LogGroup\"</code> </p> </li> <li> <p> <code>\"Identifier\": \"<i>name-of-log-group</i>\"</code> </p> </li> </ul>"
546551
}
547552
}
548553
},
@@ -599,13 +604,13 @@
599604
"members":{
600605
"StartTime":{
601606
"shape":"Timestamp",
602-
"documentation":"<p>The start of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p>",
607+
"documentation":"<p>The start of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p> <p>Your requested start time will be rounded to the nearest hour.</p>",
603608
"location":"querystring",
604609
"locationName":"StartTime"
605610
},
606611
"EndTime":{
607612
"shape":"Timestamp",
608-
"documentation":"<p>The end of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p>",
613+
"documentation":"<p>The end of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p> <p>Your requested end time will be rounded to the nearest hour.</p>",
609614
"location":"querystring",
610615
"locationName":"EndTime"
611616
},
@@ -643,11 +648,11 @@
643648
"members":{
644649
"StartTime":{
645650
"shape":"Timestamp",
646-
"documentation":"<p>The start of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p>"
651+
"documentation":"<p>The start of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p> <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because it was rounded to the nearest hour.</p>"
647652
},
648653
"EndTime":{
649654
"shape":"Timestamp",
650-
"documentation":"<p>The end of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p>"
655+
"documentation":"<p>The end of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p> <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because it was rounded to the nearest hour.</p>"
651656
},
652657
"ServiceDependencies":{
653658
"shape":"ServiceDependencies",
@@ -669,13 +674,13 @@
669674
"members":{
670675
"StartTime":{
671676
"shape":"Timestamp",
672-
"documentation":"<p>The start of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p>",
677+
"documentation":"<p>The start of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p> <p>Your requested start time will be rounded to the nearest hour.</p>",
673678
"location":"querystring",
674679
"locationName":"StartTime"
675680
},
676681
"EndTime":{
677682
"shape":"Timestamp",
678-
"documentation":"<p>The end of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p>",
683+
"documentation":"<p>The end of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p> <p>Your requested start time will be rounded to the nearest hour.</p>",
679684
"location":"querystring",
680685
"locationName":"EndTime"
681686
},
@@ -713,11 +718,11 @@
713718
"members":{
714719
"StartTime":{
715720
"shape":"Timestamp",
716-
"documentation":"<p>The start of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p>"
721+
"documentation":"<p>The start of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p> <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because it was rounded to the nearest hour.</p>"
717722
},
718723
"EndTime":{
719724
"shape":"Timestamp",
720-
"documentation":"<p>The end of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p>"
725+
"documentation":"<p>The end of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p> <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because it was rounded to the nearest hour.</p>"
721726
},
722727
"ServiceDependents":{
723728
"shape":"ServiceDependents",
@@ -791,13 +796,13 @@
791796
"members":{
792797
"StartTime":{
793798
"shape":"Timestamp",
794-
"documentation":"<p>The start of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p>",
799+
"documentation":"<p>The start of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p> <p>Your requested start time will be rounded to the nearest hour.</p>",
795800
"location":"querystring",
796801
"locationName":"StartTime"
797802
},
798803
"EndTime":{
799804
"shape":"Timestamp",
800-
"documentation":"<p>The end of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p>",
805+
"documentation":"<p>The end of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p> <p>Your requested end time will be rounded to the nearest hour.</p>",
801806
"location":"querystring",
802807
"locationName":"EndTime"
803808
},
@@ -829,11 +834,11 @@
829834
"members":{
830835
"StartTime":{
831836
"shape":"Timestamp",
832-
"documentation":"<p>The start of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p>"
837+
"documentation":"<p>The start of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p> <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because it was rounded to the nearest hour.</p>"
833838
},
834839
"EndTime":{
835840
"shape":"Timestamp",
836-
"documentation":"<p>The end of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p>"
841+
"documentation":"<p>The end of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p> <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because it was rounded to the nearest hour.</p>"
837842
},
838843
"ServiceOperations":{
839844
"shape":"ServiceOperations",
@@ -854,13 +859,13 @@
854859
"members":{
855860
"StartTime":{
856861
"shape":"Timestamp",
857-
"documentation":"<p>The start of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p>",
862+
"documentation":"<p>The start of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p> <p>Your requested start time will be rounded to the nearest hour.</p>",
858863
"location":"querystring",
859864
"locationName":"StartTime"
860865
},
861866
"EndTime":{
862867
"shape":"Timestamp",
863-
"documentation":"<p>The end of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p>",
868+
"documentation":"<p>The end of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p> <p>Your requested start time will be rounded to the nearest hour.</p>",
864869
"location":"querystring",
865870
"locationName":"EndTime"
866871
},
@@ -894,11 +899,11 @@
894899
"members":{
895900
"StartTime":{
896901
"shape":"Timestamp",
897-
"documentation":"<p>The start of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p>"
902+
"documentation":"<p>The start of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p> <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because it was rounded to the nearest hour.</p>"
898903
},
899904
"EndTime":{
900905
"shape":"Timestamp",
901-
"documentation":"<p>The end of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p>"
906+
"documentation":"<p>The end of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as be epoch time in seconds. For example: <code>1698778057</code> </p> <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because it was rounded to the nearest hour.</p>"
902907
},
903908
"ServiceSummaries":{
904909
"shape":"ServiceSummaries",
@@ -931,6 +936,10 @@
931936
}
932937
}
933938
},
939+
"LogGroupReferences":{
940+
"type":"list",
941+
"member":{"shape":"Attributes"}
942+
},
934943
"Metric":{
935944
"type":"structure",
936945
"members":{
@@ -1098,7 +1107,7 @@
10981107
},
10991108
"ResourceId":{
11001109
"shape":"ResourceId",
1101-
"documentation":"<p>Cannot find the resource id.</p>"
1110+
"documentation":"<p>Can't find the resource id.</p>"
11021111
},
11031112
"Message":{"shape":"FaultDescription"}
11041113
},
@@ -1161,6 +1170,10 @@
11611170
"MetricReferences":{
11621171
"shape":"MetricReferences",
11631172
"documentation":"<p>An array of structures that each contain information about one metric associated with this service.</p>"
1173+
},
1174+
"LogGroupReferences":{
1175+
"shape":"LogGroupReferences",
1176+
"documentation":"<p>An array of string-to-string maps that each contain information about one log group associated with this service. Each string-to-string map includes the following fields:</p> <ul> <li> <p> <code>\"Type\": \"AWS::Resource\"</code> </p> </li> <li> <p> <code>\"ResourceType\": \"AWS::Logs::LogGroup\"</code> </p> </li> <li> <p> <code>\"Identifier\": \"<i>name-of-log-group</i>\"</code> </p> </li> </ul>"
11641177
}
11651178
},
11661179
"documentation":"<p>This structure contains information about one of your services that was discovered by Application Signals. </p>"
@@ -1807,5 +1820,5 @@
18071820
"box":true
18081821
}
18091822
},
1810-
"documentation":"<important> <p>This is a Preview release of the Application Signals API Reference. Operations and parameters are subject to change before the general availability release.</p> </important> <p>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.</p> <p>Application Signals provides the following benefits:</p> <ul> <li> <p>Automatically collect metrics and traces from your applications, and display key metrics such as call volume, availability, latency, faults, and errors. </p> </li> <li> <p>Create and monitor service level objectives (SLOs). </p> </li> <li> <p>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.</p> </li> </ul>"
1823+
"documentation":"<p>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.</p> <p>Application Signals provides the following benefits:</p> <ul> <li> <p>Automatically collect metrics and traces from your applications, and display key metrics such as call volume, availability, latency, faults, and errors. </p> </li> <li> <p>Create and monitor service level objectives (SLOs). </p> </li> <li> <p>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.</p> </li> </ul> <p>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.</p>"
18111824
}

0 commit comments

Comments
 (0)