Skip to content
Merged
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,81 @@
---
title: "AWS Metric Streams Integration Now Supports OpenTelemetry 1.0 Format"
summary: "Enhanced support for the OpenTelemetry 1.0 output format in our AWS CloudWatch Metric Streams integration, offering improved performance and richer metadata for all setup methods."
releaseDate: "2025-10-13"

Check warning on line 4 in src/content/whats-new/2025/10/whats-new-10-13-support-aws-otel10-format.md

View workflow job for this annotation

GitHub Actions / vale-linter

[vale] reported by reviewdog 🐶 [new-relic.RangeFormat] Use an en dash in a range of numbers. Raw Output: {"message": "[new-relic.RangeFormat] Use an en dash in a range of numbers.", "location": {"path": "src/content/whats-new/2025/10/whats-new-10-13-support-aws-otel10-format.md", "range": {"start": {"line": 4, "column": 15}}}, "severity": "WARNING"}
---

We are excited to announce a significant enhancement to our AWS infrastructure monitoring capabilities. Our **AWS CloudWatch Metric Streams** integration now supports the **OpenTelemetry (OTLP) 1.0** output format. This update allows you to leverage the latest industry standards for telemetry data, providing a more efficient and future-proof way to stream metrics from your AWS environment into New Relic.

Check warning on line 7 in src/content/whats-new/2025/10/whats-new-10-13-support-aws-otel10-format.md

View workflow job for this annotation

GitHub Actions / vale-linter

[vale] reported by reviewdog 🐶 [Microsoft.SentenceLength] Try to keep sentences short (< 30 words). Raw Output: {"message": "[Microsoft.SentenceLength] Try to keep sentences short (\u003c 30 words).", "location": {"path": "src/content/whats-new/2025/10/whats-new-10-13-support-aws-otel10-format.md", "range": {"start": {"line": 7, "column": 216}}}, "severity": "INFO"}

Check warning on line 7 in src/content/whats-new/2025/10/whats-new-10-13-support-aws-otel10-format.md

View workflow job for this annotation

GitHub Actions / vale-linter

[vale] reported by reviewdog 🐶 [Microsoft.Passive] 'are excited' looks like passive voice. Raw Output: {"message": "[Microsoft.Passive] 'are excited' looks like passive voice.", "location": {"path": "src/content/whats-new/2025/10/whats-new-10-13-support-aws-otel10-format.md", "range": {"start": {"line": 7, "column": 4}}}, "severity": "INFO"}

Check failure on line 7 in src/content/whats-new/2025/10/whats-new-10-13-support-aws-otel10-format.md

View workflow job for this annotation

GitHub Actions / vale-linter

[vale] reported by reviewdog 🐶 [Microsoft.Contractions] Use 'we're' instead of 'We are'. Raw Output: {"message": "[Microsoft.Contractions] Use 'we're' instead of 'We are'.", "location": {"path": "src/content/whats-new/2025/10/whats-new-10-13-support-aws-otel10-format.md", "range": {"start": {"line": 7, "column": 1}}}, "severity": "ERROR"}

## What's Changed

You can now configure your AWS Metric Stream to send data using the OTLP 1.0 format, which uses an efficient binary protobuf encoding. To ensure backward compatibility and a seamless transition for existing users, our updated CloudFormation and Terraform integrations will continue to **default to the OTLP 0.7 format**. You can easily opt-in to use the new 1.0 format.

Check warning on line 11 in src/content/whats-new/2025/10/whats-new-10-13-support-aws-otel10-format.md

View workflow job for this annotation

GitHub Actions / vale-linter

[vale] reported by reviewdog 🐶 [new-relic.Adverbs] Consider removing 'easily'. Raw Output: {"message": "[new-relic.Adverbs] Consider removing 'easily'.", "location": {"path": "src/content/whats-new/2025/10/whats-new-10-13-support-aws-otel10-format.md", "range": {"start": {"line": 11, "column": 330}}}, "severity": "INFO"}

This enhancement provides several key benefits:

1. **Improved Performance and Efficiency**
* Utilize the highly efficient binary protobuf format of OTLP 1.0, reducing data transfer volume and processing overhead compared to JSON-based formats.
2. **Richer Metadata and Future-Proofing**
* Align with the latest OpenTelemetry standards, ensuring compatibility with future enhancements and enabling richer, more detailed metric attributes.

## How to Enable OpenTelemetry 1.0

You can enable the OTLP 1.0 format based on your integration method.

### CloudFormation Template

#### For New Stacks

When setting up a new stack with our latest template, you will have the option to select `opentelemetry1.0` as the output format. The template continues to default to `opentelemetry0.7`.

#### For Existing Stacks

If you have an existing stack, you must perform a stack update.

1. Navigate to your stack in the AWS CloudFormation console.
2. Initiate an update and choose "Replace existing template".

Check failure on line 35 in src/content/whats-new/2025/10/whats-new-10-13-support-aws-otel10-format.md

View workflow job for this annotation

GitHub Actions / vale-linter

[vale] reported by reviewdog 🐶 [Microsoft.Quotes] Punctuation should be inside the quotes. Raw Output: {"message": "[Microsoft.Quotes] Punctuation should be inside the quotes.", "location": {"path": "src/content/whats-new/2025/10/whats-new-10-13-support-aws-otel10-format.md", "range": {"start": {"line": 35, "column": 35}}}, "severity": "ERROR"}

Check warning on line 35 in src/content/whats-new/2025/10/whats-new-10-13-support-aws-otel10-format.md

View workflow job for this annotation

GitHub Actions / vale-linter

[vale] reported by reviewdog 🐶 [new-relic.ComplexWords] Consider using 'start' or 'begin' instead of 'Initiate'. Raw Output: {"message": "[new-relic.ComplexWords] Consider using 'start' or 'begin' instead of 'Initiate'.", "location": {"path": "src/content/whats-new/2025/10/whats-new-10-13-support-aws-otel10-format.md", "range": {"start": {"line": 35, "column": 5}}}, "severity": "INFO"}
3. Provide the following updated template URL:

Check warning on line 36 in src/content/whats-new/2025/10/whats-new-10-13-support-aws-otel10-format.md

View workflow job for this annotation

GitHub Actions / vale-linter

[vale] reported by reviewdog 🐶 [new-relic.ComplexWords] Consider using 'give' or 'offer' instead of 'Provide'. Raw Output: {"message": "[new-relic.ComplexWords] Consider using 'give' or 'offer' instead of 'Provide'.", "location": {"path": "src/content/whats-new/2025/10/whats-new-10-13-support-aws-otel10-format.md", "range": {"start": {"line": 36, "column": 5}}}, "severity": "INFO"}
[https://nr-downloads-main.s3.amazonaws.com/cloud_integrations/aws/cloudformation/newrelic-cloudformation-mstreams.yml](https://nr-downloads-main.s3.amazonaws.com/cloud_integrations/aws/cloudformation/newrelic-cloudformation-mstreams.yml)
4. Proceed with the stack update, selecting `opentelemetry1.0` when prompted for the output format.

### Terraform

> **Note:** Support for the OTLP 1.0 format is available starting with version 3.70.6 of the New Relic Terraform Provider.

Our Terraform configuration uses the official `newrelic` provider to create the necessary AWS and New Relic resources. To enable OTLP 1.0, you define a variable for the output format and set its value to `opentelemetry1.0`.

First, define the variable in your `variables.tf` file, defaulting to `opentelemetry0.7` for backward compatibility:

```tf
variable "output_format" {
description = "The output format for the CloudWatch Metric Stream. Use 'opentelemetry0.7' for OTLP 0.7 or 'opentelemetry1.0' for OTLP 1.0."
type = string
default = "opentelemetry0.7"
}
```

Then, in your `main.tf`, reference this variable in the `aws_cloudwatch_metric_stream` resource:

```tf
resource "aws_cloudwatch_metric_stream" "newrelic_metric_stream" {
# ... other properties like name, role_arn, firehose_arn ...

output_format = var.output_format

# ... include/exclude filters ...
}
```

When you run your Terraform plan, you can set `output_format` to `"opentelemetry1.0"` to enable the new format.

### Manual Setup

If you configured your integration manually, you can update the format directly in the AWS console.

1. Navigate to **CloudWatch** -\> **Metrics** -\> **Streams**.
2. Select the metric stream that forwards data to New Relic's Kinesis Firehose.
3. Click **Edit**.
4. Under "Output format," change the selection to **OpenTelemetry 1.0**.
5. Save your changes.

<!-- end list -->

Loading