cloudwatch metrics

connectors/aws.md

@@ -7,7 +7,7 @@ order: -1
 
 ---
 
-The AWS Connector allows you to send data from your AWS resources to Baselime. This includes logs, traces, and metrics. By connecting your AWS account to Baselime, you can get a unified view of your architecture, query your data, and set up alerts.
+The AWS Connector allows you to send data from your AWS resources to Baselime. This includes logs and traces. By connecting your AWS account to Baselime, you can get a unified view of your architecture, query your data, and set up alerts.
 
 ---
 
@@ -33,16 +33,14 @@ If you decide to remove Baselime from your AWS account, delete the CloudFormatio
 
 ## Does Baselime automatically recognise new functions and services?
 
-Yes, when you deploy new serverless functions and services to your cloud infrastructure, Baselime automatically detects them and starts ingesting logs, metrics and traces from those function. To add OpenTelemetry tracing, add the `baselime:tracing` tag to your new functions and set it to `true`. 
+Yes, when you deploy new serverless functions and services to your cloud infrastructure, Baselime automatically detects them and starts ingesting logs and traces from those function. To add OpenTelemetry tracing, add the `baselime:tracing` tag to your new functions and set it to `true`. 
 
 ---
 
 ## Does Baselime have an impact on my AWS bill?
 
 Baselime relies on a few AWS resources in your AWS account, most notably:
-- Amazon CloudWatch metrics stream: to enable CloudWatch metrics to be queried using the Baselime query engine
 - Amazon CloudTrail: to enable CloudTrail events, and also register new subscription filters as soon as new serverless functions or services are created
-- Amazon Kinesis Data Firehose: To store telemetry data in cold storage in your AWS account
 
 These services may add a minimal cost on your AWS monthly bill. Please refer to the [AWS princing calculator](https://calculator.aws/) for estimates based on your usage.
 
@@ -69,9 +67,8 @@ Once connected, Baselime will automatically ingest data from your AWS environmen
 * AWS Lambda Logs
 * Amazon API Gateway Logs
 * Amazon Cloudtrail Logs
-* Amazon Cloudwatch Metrics
 * Amazon ECS Logs (through fluentd)
-* Open Telemetry Metrics
+* OpenTelemetry Metrics
 
 Once ingested, the telemetry data is streamed through a Kinesis Firehose to an Amazon S3 bucket in your AWS account for cold storage. There you can access the raw data and use it for your own purposes.
 

faq.md

@@ -19,7 +19,7 @@ Check out our [pricing page](https://baselime.io/pricing) for more details.
 
 ## How does Baselime count events for billing?
 
-Baselime counts the number of events daily and updates your dashboard accordingly. Baselime does not count Amazon CloudWatch metrics or Amazon CloudTrail logs as part of the monthly event cap. All other events are counted, including the `START`, `END` and `REPORT` log lines from serverless functions.
+Baselime counts the number of events daily and updates your dashboard accordingly. Baselime does not count Amazon CloudTrail logs as part of the monthly event cap. All other events are counted, including the `START`, `END` and `REPORT` log lines from serverless functions.
 
 ---
 

sending-data/platforms/aws/apprunner-logs.md

@@ -29,7 +29,7 @@ Moreover, Baselime automatically creates new subscription filters for newly depl
 
 If you're having trouble sending data from your AWS App Runner logs to Baselime, here are a few things to check:
 
-- Verify that your AWS account is correctly connected to Baselime and you receive data in other datasets such as [CloudWatch Metrics](./cloudwatch-metrics.md) or [CloudTrail Events](./cloudtrail.md)
+- Verify that your AWS account is correctly connected to Baselime and you receive data in other datasets such as [CloudTrail Events](./cloudtrail.md)
 - Check that your App Runner services functions are not already using the maximum number of subscription filters allowed per log group. AWS limits each log group to 2 subscription filters at most. If you're already at the limit, you can remove subscription filters with the [cloudwatch-subscription-filters-remover](https://github.com/baselime/cloudwatch-subscription-filters-remover) to delete the ones you don't need anymore.
 - Make sure that your AWS App Runner services are being live and you can view the logs in the CloudWatch section of the AWS Console.
 

sending-data/platforms/aws/aws-lambda/logs.md

@@ -70,7 +70,7 @@ The Baselime AWS Lambda Extension is language agnostic and is compressed as a si
 
 ![Using the Baselime Lambda Extension](../../../../assets/images/illustrations/sending-data/lambda-extension.png)
 
-All the logs and metrics from your AWS Lambda function is collected asynchronously from your invocation, and sent to the Baselime backend in a separate process from your invocation, with no impact on the latency your users experience.
+All the logs from your AWS Lambda function is collected asynchronously from your invocation, and sent to the Baselime backend in a separate process from your invocation, with no impact on the latency your users experience.
 
 ### Configuration
 
@@ -320,6 +320,6 @@ If the message in `@message` is a valid JSON object, Baselime will parse it, oth
 
 If you're having trouble sending data from your AWS Lambda logs to Baselime, here are a few things to check:
 
-- Verify that your AWS account is correctly connected to Baselime and you receive data in other datasets such as [CloudWatch Metrics](../cloudwatch-metrics.md) or [CloudTrail Events](../cloudtrail.md)
+- Verify that your AWS account is correctly connected to Baselime and you receive data in other datasets such as [CloudTrail Events](../cloudtrail.md)
 - Check that your Lambda functions are not already using the maximum number of subscription filters allowed per log group. AWS limits each log group to 2 subscription filters at most. If you're already at the limit, you can remove subscription filters with the [cloudwatch-subscription-filters-remover](https://github.com/baselime/cloudwatch-subscription-filters-remover) to delete the ones you don't need anymore.
 - Make sure that your AWS Lambda functions are being invoked and you can view the logs in the CloudWatch section of the AWS Console

sending-data/platforms/aws/index.md

@@ -17,4 +17,3 @@ The following sections highlight how Baselime captures telemetry data for suppor
 [!ref icon="../../../assets/images/logos/apprunner_logo.png"](./apprunner-logs.md)
 [!ref icon="../../../assets/images/logos/logo_aws_apigateway.png"](./apigateway-logs.md)
 [!ref icon="../../../assets/images/logos/logo_cloudtrail.png"](./cloudtrail.md)
-[!ref icon="../../../assets/images/logos/logo_cloudwatch.png"](./cloudwatch-metrics.md)