Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Metrics GA documentation changes #304

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all 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
2 changes: 1 addition & 1 deletion src/docs/getting-started/adot-eks-add-on.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ import operatorImg2 from "assets/img/docs/gettingStarted/operator/img2.png"

## Introduction

Welcome to the getting started guide for AWS Distro for OpenTelemetry (ADOT) using Elastic Kubernetes Service (EKS) add-ons. This guide shows you how to leverage Amazon EKS add-ons to install and manage ADOT within your Amazon EKS cluster. [ADOT](https://aws-otel.github.io/) is generally available (GA) for tracing and can also be used for metrics. Amazon EKS add-ons support for ADOT enables a simplified experience through EKS APIs to install one component of ADOT, the [ADOT Operator](/docs/getting-started/adot-eks-add-on#the-adot-operator-and-adot-collector), in your Amazon EKS cluster for your metrics and/or trace collection pipeline. Amazon EKS add-ons support reduces the amount of configuration, setup, and deployment that would be required otherwise. For more information, see [Amazon EKS add-ons](https://docs.aws.amazon.com/eks/latest/userguide/eks-add-ons.html).
Welcome to the getting started guide for AWS Distro for OpenTelemetry (ADOT) using Elastic Kubernetes Service (EKS) add-ons. This guide shows you how to leverage Amazon EKS add-ons to install and manage ADOT within your Amazon EKS cluster. [ADOT](https://aws-otel.github.io/) is generally available (GA) for both tracing and metrics. Amazon EKS add-ons support for ADOT enables a simplified experience through EKS APIs to install one component of ADOT, the [ADOT Operator](/docs/getting-started/adot-eks-add-on#the-adot-operator-and-adot-collector), in your Amazon EKS cluster for your metrics and/or trace collection pipeline. Amazon EKS add-ons support reduces the amount of configuration, setup, and deployment that would be required otherwise. For more information, see [Amazon EKS add-ons](https://docs.aws.amazon.com/eks/latest/userguide/eks-add-ons.html).

This guide contains:

Expand Down
5 changes: 1 addition & 4 deletions src/docs/getting-started/cloudwatch-metrics.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ Collector as part of AWS OpenTelemetry that converts OpenTelemetry format metric
It enables customer applications integrating OpenTelemetry metrics with CloudWatch and has ability to send high-cardinality application
metrics which is well supported by EMF.

In this tutorial, we will walk through how to enable CloudWatch metrics in the ADOT Collector.
In this tutorial, we will walk through how to enable CloudWatch metrics in the ADOT Collector. Note that ADOT is generally available (GA) for metrics.

<SectionSeparator />

Expand Down Expand Up @@ -112,6 +112,3 @@ processors:

For new updates and configuration options on CloudWatch Metrics support, follow us on
[AWS EMF Repo](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/master/exporter/awsemfexporter).



3 changes: 1 addition & 2 deletions src/docs/getting-started/container-insights.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ CloudWatch Container Insights uses the [CloudWatch agent](https://github.com/aws
both [infrastructure metrics](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ContainerInsights.html)
and [Prometheus metrics](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus.html).
To migrate existing customers to use AWS Distro for OpenTelemetry,
we have enhanced the [ADOT Collector](https://github.com/aws-observability/aws-otel-collector) to support the same CloudWatch Container Insights experience.
we have enhanced the [ADOT Collector](https://github.com/aws-observability/aws-otel-collector) to support the same CloudWatch Container Insights experience. Also note that ADOT is generally available (GA) for metrics.

## Collecting infrastructure metrics

Expand Down Expand Up @@ -75,4 +75,3 @@ all clusters are saved in one metric namespace, with different dimension values
|-----------------------|-----------------------------------------------|------------------------------------|
| <Link to="/docs/getting-started/container-insights/eks-prometheus">EKS</Link> | `/aws/containerinsights/eks-1/prometheus` | `ContainerInsights/Prometheus` |
| <Link to="/docs/getting-started/container-insights/ecs-prometheus">ECS</Link> | `/aws/ecs/containerinsights/ecs-1/prometheus` | `ECS/ContainerInsights/Prometheus` |

2 changes: 2 additions & 0 deletions src/docs/getting-started/dotnet-sdk.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ OpenTelemetry provides different language SDKs to instrument customer applicatio

In this tutorial, we will introduce how to use OpenTelemetry .NET SDK for manual instrumentation.

Note: AWS Distro for OpenTelemetry is now generally available for .NET metrics.

<SectionSeparator />

## Getting Started
Expand Down
2 changes: 2 additions & 0 deletions src/docs/getting-started/java-sdk.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,8 @@ The AWS Distro for OpenTelemetry (ADOT) Java refers to some components developed
to guides that go over how to configure the relevant components of OpenTelemetry to send trace data to the AWS X-Ray
backend.

Note: ADOT is now generally available for Java metrics.

<SectionSeparator />

## Getting Started
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ In order to scrape and export metrics to your AWS Managed Service for Prometheus
the OpenTelemetry Collector (ADOT Collector) or a standard vanilla Prometheus server.

In this Getting Started guide, we’ll show you how to configure the ADOT Collector to scrape from a Prometheus-instrumented application,
and send metrics to the AWS Managed Service for Prometheus (AMP).
and send metrics to the AWS Managed Service for Prometheus (AMP). Note that ADOT is generally available (GA) for metrics.

<SectionSeparator />

Expand Down Expand Up @@ -132,4 +132,3 @@ For more advanced configurations with the ADOT Collector-AMP, please take a look

We would love to hear more common configuration scenarios or improvements to this documentation from you! Please submit an issue
on the [aws-otel community](https://github.com/aws-observability/aws-otel-community) to let us know.

2 changes: 2 additions & 0 deletions src/docs/getting-started/python-sdk.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ import SectionSeparator from "components/MdxSectionSeparator/sectionSeparator.js

The AWS Distro for OpenTelemetry (ADOT) Python refers to some components developed to complement the upstream [OpenTelemetry (OTel) Python SDK](https://github.com/open-telemetry/opentelemetry-python/tree/main/opentelemetry-sdk). Below are links to guides that go over how to configure the relevant components of the OpenTelemetry SDK to send trace data to the AWS X-Ray backend.

Note: ADOT is now generally available for Python metrics.

<SectionSeparator />

## Getting Started
Expand Down