Skip to content

Commit fe15826

Browse files
authored
Merge branch 'main' into changepath
2 parents 579c2af + 05f7c04 commit fe15826

File tree

12 files changed

+178
-6
lines changed

12 files changed

+178
-6
lines changed

src/content/BlogPosts/blogPosts.yaml

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,21 @@ description:
66
path: /blog
77

88
blogs:
9+
- title: "AWS Distro for OpenTelemetry Lambda Layers are now available with ADOT Collector v0.35.0"
10+
author: "Pavan Sai Vasireddy"
11+
date: "03-November-2023"
12+
body:
13+
"ADOT Lambda Layers now distribute ADOT Collector v0.35.0 with new layers supporting AMD64 and ARM64 Lambda functions"
14+
link: "/docs/ReleaseBlogs/aws-distro-for-opentelemetry-lambda-layer-v0.35.0"
15+
16+
- title: "AWS Distro for OpenTelemetry v0.35.0 is now available"
17+
author: "Bryan Aguilar"
18+
date: "02-November-2023"
19+
body:
20+
"AWS Distro for OpenTelemetry v0.35.0 is now available. You can download the latest AWS Distro for OpenTelemetry Collector image
21+
from the Amazon Elastic Container Registry (Amazon ECR) Public Gallery."
22+
link: "/docs/ReleaseBlogs/aws-distro-for-opentelemetry-collector-v0.35.0"
23+
924
- title: "AWS Distro for OpenTelemetry Java Instrumentation v1.31.0 is now available"
1025
author: "Paurush Garg"
1126
date: "26-Oct-2023"
Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
---
2+
title: 'AWS Distro for OpenTelemetry v0.35.0'
3+
description:
4+
This blog post is the release announcement for ADOT Collector v0.35.0
5+
---
6+
7+
import SectionSeparator from "components/MdxSectionSeparator/sectionSeparator.jsx"
8+
9+
<SectionSeparator />
10+
11+
[AWS Distro for OpenTelemetry (ADOT)](https://aws-otel.github.io/) Collector v0.35.0 is now available.
12+
You can download the latest [ADOT Collector image](https://gallery.ecr.aws/aws-observability/aws-otel-collector) from the
13+
[Amazon Elastic Container Registry (Amazon ECR)](https://aws.amazon.com/ecr/) Public Gallery.
14+
15+
<SectionSeparator />
16+
17+
**Notice**
18+
19+
We are aware of a potential issue in the google.golang.org/grpc package (CVE-2023-44487), used by the AWS Distribution for Open Telemetry (ADOT) Collector up to and including v0.34.0.
20+
We have a new release of the ADOT Collector, v0.35.0 updating packages affected by this vulnerability. We recommend that users update their ADOT Collector
21+
to at least v0.35.0 at the earliest opportunity. See https://aws-otel.github.io/docs/getting-started/collector for information on deploying the ADOT Collector.
22+
23+
**Upstream changelog**
24+
25+
* [OpenTelemetry Collector v0.87.0](https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.87.0)
26+
* [OpenTelemetry Collector v0.88.0](https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.88.0)
27+
* [OpenTelemetry Collector Contrib v0.87.0](https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.87.0)
28+
* [OpenTelemetry Collector Contrib v0.88.0](https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.88.0)
29+
30+
**New Components**
31+
32+
The following feature gates are now enabled by default. The filelog receiver, filestorage extension, and AWS CloudwatchLogs exporter
33+
can be used with no command line changes. The feature gate can still be used to disable the usage of these components in an ADOT
34+
Collector configuration.
35+
36+
`adot.receiver.filelog`
37+
`adot.exporter.awscloudwatchlogs
38+
`adot.extension.file_storage`
39+
40+
** Important: ADOT Collector v0.35.0 Breaking Change **
41+
42+
Users of the `statsd` receiver, please refer to GitHub Issue - [Warning: StatsD Receiver → EMF Exporter
43+
Metric Pipeline Breaking Change](https://github.com/aws-observability/aws-otel-collector/issues/2249) for information on a breaking change.
44+
45+
** Important: ADOT Collector v0.35.0 Breaking Change
46+
47+
Users of the `awscontainerinsightreceiver`, please refer to the [GitHub Issue - Warning: Container Image Default User Change → Important
48+
consideration for AWSContainerInsightReceiver](https://github.com/aws-observability/aws-otel-collector/issues/2317) for more information on a breaking change.
49+
50+
-
51+
52+
Detailed release notes are available via - [GitHub](https://github.com/aws-observability/aws-otel-collector/releases).
53+
All code changes are upstream in the respective OpenTelemetry project components.
54+
55+
**Download**
56+
57+
Detailed technical documentation is available on the [ADOT developer site](https://aws-otel.github.io/),
58+
and you can [download the distribution](https://aws-otel.github.io/download) from
59+
[GitHub](https://github.com/aws-observability/aws-otel-collector/releases/tag/v0.35.0).
60+
You can also download the latest [ADOT Collector image](https://gallery.ecr.aws/aws-observability/aws-otel-collector)
61+
from the [Amazon Elastic Container Registry (Amazon ECR)](https://aws.amazon.com/ecr/) Public Gallery.
62+
63+
To learn more about how to use AWS Distro for OpenTelemetry (ADOT) to collect data for your observability solution,
64+
check out the hands-on [AWS Observability workshop](https://observability.workshop.aws/en/adot.html).
65+
Please file an [issue](https://github.com/aws-observability/aws-otel-community/issues) if you have any
66+
questions about the distribution, features, or its components.
67+
68+
We also welcome you to participate in the [OpenTelemetry project](https://github.com/open-telemetry).
69+
The project was [approved for incubation](https://www.cncf.io/blog/2021/08/26/opentelemetry-becomes-a-cncf-incubating-project/) status
70+
in August 2021 by the Cloud Native Computing Foundation Technical Oversight Committee (CNCF TOC). Learn more about
71+
[AWS Distro for OpenTelemetry](https://aws.amazon.com/blogs/opensource/category/management-tools/aws-distro-for-opentelemetry/) on the
72+
[AWS Open Source Blog](https://aws.amazon.com/blogs/opensource/category/management-tools/aws-distro-for-opentelemetry/), where we announced
73+
the distribution’s [general availability for tracing](https://aws.amazon.com/blogs/opensource/aws-distro-for-opentelemetry-is-now-ga-for-tracing/) in September 2021
74+
and the distribution's [general availability for metrics](https://aws.amazon.com/blogs/opensource/aws-distro-for-opentelemetry-is-now-generally-available-for-metrics/) in May 2022.
Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
---
2+
title: 'AWS Distro for OpenTelemetry Lambda Layers that contains ADOT Collector v0.35.0 are now available'
3+
description:
4+
Nov 2023 release announcement for ADOT Lambda layers
5+
---
6+
7+
import SectionSeparator from "components/MdxSectionSeparator/sectionSeparator.jsx"
8+
9+
<SectionSeparator />
10+
11+
AWS Distro for OpenTelemetry Lambda Layers now supports AMD64 and ARM64 in the following AWS regions:
12+
13+
|Region | AMD64 | ARM64 |
14+
|-------------------------|-------|-------|
15+
|Asia Pacific (Mumbai) |||
16+
|Asia Pacific (Singapore) |||
17+
|Asia Pacific (Sydney) |||
18+
|Asia Pacific (Tokyo) |||
19+
|Asia pacific (Seoul) |||
20+
|Canada (Central) |||
21+
|Europe (Frankfurt) |||
22+
|Europe (Ireland) |||
23+
|Europe (London) |||
24+
|Europe (Stockholm) |||
25+
|Europe(Paris) |||
26+
|South America (Sao Paulo)|||
27+
|US East (N. Virginia) |||
28+
|US East (Ohio) |||
29+
|US West (N California) |||
30+
|US West (Oregon) |||
31+
32+
<SectionSeparator />
33+
34+
### Release Highlights
35+
36+
- Python layer [**aws-otel-python-<amd64|arm64>-ver-1-20-0**](https://aws-otel.github.io/docs/getting-started/lambda/lambda-python) contains OpenTelemetry Python `v1.20.0` and ADOT Collector for Lambda `v0.35.0`
37+
- Nodejs layer [**aws-otel-nodejs-<amd64|arm64>-ver-1-17-1**](https://aws-otel.github.io/docs/getting-started/lambda/lambda-js) contains OpenTelemetry JavaScript Core `v1.17.1` with AWS Lambda Instrumentation `v0.37.1` and ADOT Collector for Lambda `v0.35.0`
38+
- Java-Wrapper layer [**aws-otel-java-wrapper-<amd64|arm64>-ver-1-31-0**](https://aws-otel.github.io/docs/getting-started/lambda/lambda-java) contains OpenTelemetry Java `v1.31.0` and ADOT Collector for Lambda `v0.35.0`
39+
- Java-Agent layer [**aws-otel-java-agent-<amd64|arm64>-ver-1-31-0**](https://aws-otel.github.io/docs/getting-started/lambda/lambda-java-auto-instr) contains AWS Distro for OpenTelemetry Java Instrumentation `v1.31.0` and ADOT Collector for Lambda `v0.35.0`
40+
- Collector layer **aws-otel-collector-<amd64|arm64>-ver-0-88-0** contains ADOT Collector for Lambda `v0.35.0`. Compatible with [.NET](https://aws-otel.github.io/docs/getting-started/lambda/lambda-dotnet) and [Go](https://aws-otel.github.io/docs/getting-started/lambda/lambda-go) runtimes.
41+
42+
### Download
43+
44+
Learn more about AWS Distro for Open Telemetry Lambda support [here](https://aws-otel.github.io/docs/getting-started/lambda). All code changes are made upstream in the respective OpenTelemetry project components. Please file an [issue](https://github.com/aws-observability/aws-otel-community/issues) if you have any questions about the features, or its components.
45+
46+
We also welcome you to participate in the [OpenTelemetry project](https://github.com/open-telemetry). The project was [approved for incubation](https://www.cncf.io/blog/2021/08/26/opentelemetry-becomes-a-cncf-incubating-project/) status in August 2021 by the Cloud Native Computing Foundation Technical Oversight Committee (CNCF TOC).
47+
48+
More blog posts about
49+
[AWS Distro for OpenTelemetry](https://aws.amazon.com/blogs/opensource/category/management-tools/aws-distro-for-opentelemetry/) can be found on the
50+
[AWS Open Source Blog](https://aws.amazon.com/blogs/opensource/category/management-tools/aws-distro-for-opentelemetry/).
51+
52+
53+
### Author
54+
55+
[Pavan Sai Vasireddy](https://github.com/vasireddy99) is as a Software Development Engineer on the AWS OpenSource Observability team. He is passionate about monitoring and observability, currently focussed on release engineering for ADOT, building monitoring tools and contributing to open source.

src/content/Downloads/downloads.yaml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,9 @@
1+
- version: 'AWS Distro for OpenTelemetry Collector Version 0.35.0'
2+
releaseDate: 'November-02-2023'
3+
license: 'Apache-2.0'
4+
releaseNotesLink: 'https://github.com/aws-observability/aws-otel-collector/releases/tag/v0.35.0'
5+
documentationLink: 'https://github.com/aws-observability/aws-otel-collector/blob/v0.35.0/README.md'
6+
downloadLink: 'https://gallery.ecr.aws/aws-observability/aws-otel-collector'
17
- version: 'AWS Distro for OpenTelemetry Collector Version 0.34.0'
28
releaseDate: 'October-17-2023'
39
license: 'Apache-2.0'

src/docs/getting-started/container-insights.mdx

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,26 @@ CloudWatch Container Insights collects metrics for many resources such as CPU, m
3232
It also provides diagnostic information such as container restart failures.
3333
The metrics are aggregated at the cluster, node, pod, task, and service level as CloudWatch metrics.
3434

35+
Note: Collecting infrastructure metrics through `awscontainerinsightreceiver` requires running ADOT Collector with privileged root access as it also collects container-related data from `cadvisor`.
36+
For EKS deployments, use the [Security Context](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#security-context-1) to specify the root user as owner of the Collector process:
37+
```
38+
containers:
39+
- name: aws-otel-collector
40+
image: public.ecr.aws/aws-observability/aws-otel-collector:latest
41+
securityContext:
42+
runAsUser: 0
43+
runAsGroup: 0
44+
```
45+
For ECS deployments, use the [Task Definition](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-taskdefinition-containerdefinition.html#cfn-ecs-taskdefinition-containerdefinition-user) to specify the user owner of the collector process:
46+
```
47+
{
48+
"name": "aoc-collector",
49+
"image": "public.ecr.aws/aws-observability/aws-otel-collector:latest",
50+
"user": "root",
51+
...
52+
}
53+
```
54+
3555
The following platforms are supported:
3656

3757
- <Link to="/docs/getting-started/container-insights/eks-infra">Amazon EKS and Kubernetes platforms on Amazon EC2</Link>

src/docs/getting-started/container-insights/ecs-prometheus.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -321,6 +321,7 @@ NOTE: You need to replace placeholder values with actual value
321321

322322
- The account id in the example is `123456` and is used in ARN for taskRole and executionRole, replace it with your own AWS account id.
323323
- `amazon/aws-otel-collector:v0.11.0` is using dockerhub (potential throttle) and you can use `latest` tag if you don't want to lock version.
324+
- Collecting infrastructure metrics requires running ADOT Collector with root access and this can be configured through `user` in the container definition.
324325
- `/aoc/ecs-prometheus` is the name of <Link to="/docs/setup/ecs/config-through-ssm">SSM parameter</Link>.
325326
- `networkMode` can be `bridge`, `host`, `awsvpc`. For fargate, it has to be `awsvpc`.
326327
- `logConfiguration` is for log from ADOT Collector itself. Log groups for metrics/log collected by collector is configured using `AOT_CONFIG_CONTENT`.
@@ -338,6 +339,7 @@ e.g. `cpu 255 memory 511` is invalid pair.
338339
{
339340
"name": "adot",
340341
"image": "amazon/aws-otel-collector:v0.11.0",
342+
"user": "root",
341343
"secrets": [
342344
{
343345
"name": "AOT_CONFIG_CONTENT",

src/docs/getting-started/lambda/lambda-dotnet.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ Find the supported regions and amd64(x86_64)/arm64 layer ARN in the table below
6969

7070
|Supported Regions |Lambda layer ARN format | Contents |
7171
|---------------------|-------------------------|----------|
72-
| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-collector-<architecture\>-ver-0-84-0:1 | Contains ADOT Collector v0.33.0 |
72+
| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-collector-<architecture\>-ver-0-88-0:1 | Contains ADOT Collector v0.35.0 |
7373

7474
### Enable Tracing
7575
Once you’ve instrumented the Lambda function code and deployed to Lambda service, you can follow the instructions below to apply Lambda layer.

src/docs/getting-started/lambda/lambda-go.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ Find the supported regions and amd64(x86_64)/arm64 layer ARN in the table below
8787

8888
|Supported Regions |Lambda layer ARN format | Contents |
8989
|---------------------|-------------------------|----------|
90-
| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-collector-<architecture\>-ver-0-84-0:1 | Contains ADOT Collector v0.33.0 |
90+
| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-collector-<architecture\>-ver-0-88-0:1 | Contains ADOT Collector v0.35.0 |
9191

9292
### Enable Tracing
9393
Once you’ve instrumented the Lambda function code and deployed to Lambda service, you can follow the instructions below to apply Lambda layer.

src/docs/getting-started/lambda/lambda-java-auto-instr.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Find the supported regions and amd64(x86_64)/arm64 layer ARN in the table below
2929

3030
|Supported Regions |Lambda layer ARN format | Contents |
3131
|---------------------|-------------------------|----------|
32-
| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-java-agent-<architecture\>-ver-1-30-1:1 | Contains [ADOT Java Auto-Instrumentation Agent v1.30.0](https://github.com/aws-observability/aws-otel-java-instrumentation/releases/tag/v1.30.0) <br/><br/> Contains ADOT Collector v0.33.0 |
32+
| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-java-agent-<architecture\>-ver-1-31-0:1 | Contains [ADOT Java Auto-Instrumentation Agent v1.31.0](https://github.com/aws-observability/aws-otel-java-instrumentation/releases/tag/v1.31.0) <br/><br/> Contains ADOT Collector v0.35.0 |
3333

3434
### Enable auto-instrumentation for your Lambda function
3535

src/docs/getting-started/lambda/lambda-java.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ Find the supported regions and amd64(x86_64)/arm64 layer ARN in the table below
3939

4040
|Supported Regions |Lambda layer ARN format | Contents |
4141
|---------------------|-------------------------|----------|
42-
| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-java-wrapper-<architecture\>-ver-1-30-0:1 | Contains [OpenTelemetry for Java v1.28.0](https://github.com/open-telemetry/opentelemetry-java/releases/tag/v1.30.0) with [Java Instrumentation v1.30.0](https://github.com/aws-observability/aws-otel-java-instrumentation/releases/tag/v1.30.0) <br/><br/> Contains ADOT Collector v0.33.0 |
42+
| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-java-wrapper-<architecture\>-ver-1-31-0:1 | Contains [OpenTelemetry for Java v1.31.0](https://github.com/open-telemetry/opentelemetry-java/releases/tag/v1.31.0) with [Java Instrumentation v1.31.0](https://github.com/aws-observability/aws-otel-java-instrumentation/releases/tag/v1.31.0) <br/><br/> Contains ADOT Collector v0.35.0 |
4343

4444
### Enable auto-instrumentation for your Lambda function
4545
To enable the AWS Distro for OpenTelemetry in your Lambda function, you need to add and configure the layer, and then enable tracing.

0 commit comments

Comments
 (0)