revamp cloudwatch

Author: HarshCasper

src/content/docs/aws/services/cloudwatch.md

@@ -1,32 +1,18 @@
 ---
 title: "CloudWatch"
-linkTitle: "CloudWatch"
 description: Get started with AWS CloudWatch on LocalStack
 persistence: supported
 tags: ["Free"]
 ---
 
+## Introduction
+
 CloudWatch is a comprehensive monitoring and observability service that Amazon Web Services (AWS) provides.
 It allows you to collect and track metrics, collect and monitor log files, and set alarms.
 CloudWatch provides valuable insights into your AWS resources, applications, and services, enabling you to troubleshoot issues, optimize performance, and make informed decisions.
 
 LocalStack allows you to use CloudWatch APIs on your local machine to create and manage CloudWatch resources, such as custom metrics, alarms, and log groups, for local development and testing purposes.
-The supported APIs are available on our [API coverage page]({{< ref "coverage_cloudwatch" >}}), which provides information on the extent of CloudWatch's integration with LocalStack.
-
-{{< callout >}}
-We have introduced an all-new LocalStack-native [CloudWatch provider]({{< ref "/user-guide/aws/cloudwatch" >}}) and recently made this one the default.
-
-With the new provider we have migrated from storing data in Python objects within the Moto backend to a more robust system.
-
-Now, metrics are efficiently stored in SQLite, and alarm resources are managed using LocalStack stores.
-
-- Various enhancements have been made to attain greater feature parity with AWS.
-- The provider is engineered to ensure thread safety, facilitating smooth concurrent operations.
-- There’s a significant improvement in the integrity and durability of data.
-- The new provider allows for more efficient data retrieval.
-
-Currently, it is still possible to switch back to the old provider using `PROVIDER_OVERRIDE_CLOUDWATCH=v1` in your LocalStack configuration.
-{{< /callout >}}
+The supported APIs are available on our [API coverage page](), which provides information on the extent of CloudWatch's integration with LocalStack.
 
 ## Getting started
 
@@ -38,13 +24,13 @@ You can get the name for your Lambda Functions using the [`ListFunctions`](https
 Fetch the Log Groups using the [`DescribeLogGroups`](https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_DescribeLogGroups.html) API.
 Run the following command to get the Log Group name:
 
-{{< command >}}
-$ awslocal logs describe-log-groups
-{{< / command >}}
+```bash
+awslocal logs describe-log-groups
+```
 
 The output should look similar to the following:
 
-```sh
+```bash
 {
     "logGroups": [
         {
@@ -68,14 +54,14 @@ The output should look similar to the following:
 Get the log streams for the Log Group using the [`DescribeLogStreams`](https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_DescribeLogStreams.html) API.
 Run the following command to get the Log Stream name:
 
-{{< command >}}
-$ awslocal logs describe-log-streams \
+```bash
+awslocal logs describe-log-streams \
     --log-group-name /aws/lambda/serverless-local-hello
-{{< / command >}}
+```
 
 The output should look similar to the following:
 
-```sh
+```bash
 {
     "logStreams": [
         {
@@ -95,14 +81,14 @@ The output should look similar to the following:
 You can now fetch the log events using the [`GetLogEvents`](https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_GetLogEvents.html) API.
 Run the following command to get the logs:
 
-{{< command >}}
-$ awslocal logs get-log-events \
+```bash
+awslocal logs get-log-events \
     --log-group-name '/aws/lambda/serverless-local-hello' --log-stream-name '2023/05/02/[$LATEST]853a59d0767cfaf10d6b29a6790d8b03'
-{{< / command >}}
+```
 
 The output should look similar to the following:
 
-```sh
+```bash
 {
     "events": [
         {
@@ -126,9 +112,9 @@ The output should look similar to the following:
 }
 ```
 
-{{< callout "tip" >}}
+:::note
 You can use [filters](https://docs.aws.amazon.com/cli/latest/reference/logs/filter-log-events.html) or [queries](https://docs.aws.amazon.com/cli/latest/reference/logs/get-query-results.html) with a licensed LocalStack edition to refine your results.
-{{< /callout >}}
+:::
 
 ## Metric Alarms
 
@@ -145,8 +131,8 @@ With metric alarms, you can create customized thresholds and define actions base
 
 To get started with creating an alarm in LocalStack using the `awslocal` integration, use the following command:
 
-{{< command >}}
-$ awslocal cloudwatch put-metric-alarm \
+```bash
+awslocal cloudwatch put-metric-alarm \
   --alarm-name my-alarm \
   --metric-name Orders \
   --namespace test \
@@ -156,21 +142,21 @@ $ awslocal cloudwatch put-metric-alarm \
   --period 30 \
   --statistic Minimum \
   --treat-missing notBreaching
-{{< / command >}}
+```
 
 To monitor the status of the alarm, open a separate terminal and execute the following command:
 
-{{< command >}}
-$ watch "awslocal cloudwatch describe-alarms --alarm-names my-alarm | jq '.MetricAlarms[0].StateValue'"
-{{< / command >}}
+```bash
+watch "awslocal cloudwatch describe-alarms --alarm-names my-alarm | jq '.MetricAlarms[0].StateValue'"
+```
 
 Afterward, you can add some data that will cause a breach and set the `metric-alarm` state to **ALARM** using the following command:
 
-{{< command >}}
-$ awslocal cloudwatch put-metric-data \
+```bash
+awslocal cloudwatch put-metric-data \
     --namespace test \
     --metric-data '[{"MetricName": "Orders", "Value": -1}]'
-{{< / command >}}
+```
 
 Within a few seconds, the alarm state should change to **ALARM**, and eventually, it will go back to **OK** as we configured it to treat missing data points as `not breaching`.
 This allows you to observe how the alarm behaves in response to the provided data.
@@ -184,8 +170,8 @@ Currently, only SNS Topics are supported as the target for these actions, and it
 Here's an example demonstrating how to set up an alarm that sends a message to the specified topic when entering the **ALARM** state.
 Make sure to replace `<topic-arn>` with the valid ARN of an existing SNS topic.
 
-{{< command >}}
-$ awslocal cloudwatch put-metric-alarm \
+```bash
+awslocal cloudwatch put-metric-alarm \
   --alarm-name my-alarm \
   --metric-name Orders \
   --namespace test \
@@ -196,20 +182,30 @@ $ awslocal cloudwatch put-metric-alarm \
   --statistic Maximum \
   --treat-missing notBreaching \
   --alarm-actions <topic-arn>
-{{< / command >}}
+```
 
 By executing this command, you'll create an alarm named `my-alarm` that monitors the `Orders` metric in the `test` namespace.
 If the metric value exceeds the threshold of 50 (using the `GreaterThanThreshold` operator) during a single evaluation period of 300 seconds, the alarm will trigger the specified action on the provided SNS topic.
 
-{{< callout "warning" >}}
+:::danger
 Please be aware of the following known limitations in LocalStack:
 - Anomaly detection and extended statistics are not supported.
 - The `unit` values specified in the alarm are ignored.
 - Composite alarms are not evaluated.
 - Metric streams are not supported.
-{{< /callout >}}
+:::
+
+## Current Limitations
+
+The following CloudWatch Metrics are not supported:
+
+- Anomaly detection
+- Metric streams
+- Extended statistics
+
+In addition, the `unit` values specified in the alarm are ignored, and Composite alarms are not evaluated.
 
-## Supported Service Integrations with CloudWatch Metrics
+## Supported Service Integrations
 
 LocalStack supports the following AWS services for integration with CloudWatch metrics:
 
@@ -223,9 +219,9 @@ You can access the Resource Browser by opening the LocalStack Web Application in
 
 The Resource Browser allows you to perform the following actions:
 
-<img src="cloudwatch-log-groups-resource-browser.png" alt="CloudWatch Logs Resource Browser" title="CloudWatch Logs Resource Browser" width="900" />
+![CloudWatch Logs Resource Browser](/images/aws/cloudwatch-log-groups-resource-browser.png)
 
-<img src="cloudwatch-metrics-resource-browser.png" alt="CloudWatch Metrics Resource Browser" title="CloudWatch Metrics Resource Browser" width="900" />
+![CloudWatch Metrics Resource Browser](/images/aws/cloudwatch-metrics-resource-browser.png)
 
 - **Create Log Group**: Create a new log group by specifying the `Log Group Name`, `KMS Key ID`, and `Tags`.
 - **Put metric**: Create a new metric by specifying the `Namespace` and `Metric Data`.