此內容尚未提供您所選取的語言。我們持續努力為您提供選取的語言內容。感謝您的耐心等待！
We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.
If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”
Essential cookies are necessary to provide our site and services and cannot be deactivated. They are usually set in response to your actions on the site, such as setting your privacy preferences, signing in, or filling in forms.
Performance cookies provide anonymous statistics about how customers navigate our site so we can improve site experience and performance. Approved third parties may perform analytics on our behalf, but they cannot use the data for their own purposes.
Functional cookies help us provide useful site features, remember your preferences, and display relevant content. Approved third parties may set these cookies to provide certain site features. If you do not allow these cookies, then some or all of these services may not function properly.
Advertising cookies may be set through our site by us or our advertising partners and help us deliver relevant marketing content. If you do not allow these cookies, you will experience less relevant advertising.
Blocking some types of cookies may impact your experience of our sites. You may review and change your choices at any time by selecting Cookie preferences in the footer of this site. We and selected third-parties use cookies or similar technologies as specified in the AWS Cookie Notice.
We display ads relevant to your interests on AWS sites and on other properties, including cross-context behavioral advertising. Cross-context behavioral advertising uses data from one site or app to advertise to you on a different company’s site or app.
To not allow AWS cross-context behavioral advertising based on cookies or similar technologies, select “Don't allow” and “Save privacy choices” below, or visit an AWS site with a legally-recognized decline signal enabled, such as the Global Privacy Control. If you delete your cookies or visit this site from a different browser or device, you will need to make your selection again. For more information about cookies and how we use them, please read our AWS Cookie Notice.
To not allow all other AWS cross-context behavioral advertising, complete this form by email.
For more information about how AWS handles your information, please read the AWS Privacy Notice.
We will only store essential cookies at this time, because we were unable to save your cookie preferences.
If you want to change your cookie preferences, try again later using the link in the AWS console footer, or contact support if the problem persists.
The Cloud Native Computing Foundation (CNCF) OpenTelemetry project provides a single set of open source APIs, libraries, and agents to collect and correlate distributed traces and metrics. AWS contributes to OpenTelemetry in an upstream-first model: our enhancements to the project are first contributed to the upstream project, then we build the AWS Distro for OpenTelemetry from upstream OpenTelemetry components. These components include SDKs, auto-instrumentation agents, and collectors that are tested, optimized, secured, and supported by AWS. AWS Distro for OpenTelemetry supports Java, .NET, JavaScript, Go, and Python. Additional language support will be provided in upcoming releases.
AWS Distro for OpenTelemetry consists of SDKs, auto-instrumentation agents, collectors and exporters to send data to back-end services. AWS has contributed code to the upstream project for OpenTelemetry components including:
These components have all been contributed back to the upstream project, as future work will also be.
No, there is no cost for using AWS Distro for OpenTelemetry. You pay for traces, logs, and metrics sent to AWS. Refer to individual services for their pricing details.
To gain end-to-end visibility, OpenTelemetry agents are commonly deployed on every host or container and OpenTelemetry SDKs are integrated into every application binary. An unexpected performance degradation in an OpenTelemetry component such as a memory leak or excessive CPU usage can significantly hurt the performance and stability of monitored systems. AWS applies a comprehensive testing framework before each AWS Distro for OpenTelemetry release to ensure that the overhead of OpenTelemetry components shipped as part of AWS Distro for OpenTelemetry are quantifiable and predictable.
You can use AWS CloudFormation templates when using Amazon ECS, and KubeCtl commands when using Amazon EKS to deploy the Collector as a sidecar. To gain additional data from your applications, you can instrument using language-specific OpenTelemetry SDKs, and also use the Java auto-instrumentation agent.
You can include the OpenTelemetry Lambda Layer as part of your function using the AWS console or AWS CloudFormation templates. The layer is available in multiple languages and can be configured to send trace data to AWS X-Ray and destinations that support OpenTelemetry Protocol (OTLP). Refer to the Getting started guide when using AWS Distro for OpenTelemetry with AWS Lambda.
No, you should continue to use the CloudWatch agent. AWS Distro for OpenTelemetry works side-by-side with the CloudWatch agent to collect data needed for application monitoring. The CloudWatch agent can be used to collect logs and infrastructure metrics. AWS Distro for OpenTelemetry can be used to collect traces and application metrics.
You can deploy and configure the AWS Distro for OpenTelemetry Collector in Amazon EC2 using the getting started guide. You can then instrument your applications using language-specific OpenTelemetry SDKs to gather additional data. You can also collect the trace data using the OpenTelemetry Java and Python auto-instrumentation agents.
No, you don’t need to change anything. FireLens can be used for logs for any workloads on container services. FireLens works in conjunction with AWS Distro for OpenTelemetry. You can deploy the AWS Distro for OpenTelemetry Collector to run along with FireLens. To learn more about FireLens, see the documentation on Custom log routing.
No, you can continue using the AWS X-Ray SDK and daemon/agent for applications already instrumented. We recommend using AWS Distro for OpenTelemetry if you aim to standardize with open source APIs from upstream OpenTelemetry, or want to send traces to multiple monitoring solutions simultaneously. In order to migrate to AWS Distro for OpenTelemetry, you can use the auto-instrumentation agent for Java or instrument your application using OpenTelemetry APIs and SDKs.
Yes. All you need to do is enable the metrics exporters in AWS Distro for OpenTelemetry’s Collector configuration file.
Sampling is used to control the percentage of traces you will be collecting. Sampling is the primary mechanism used to control cost and amount of data sent across the network. In AWS Distro for OpenTelemetry, you can use a sampling rate to set a percentage of requests to be traced. The sampling rate can be set at the SDK level.
Yes. You can compile the upstream OpenTelemetry collector source code with all the necessary exporters from AWS and other third-party solutions.
No, we not creating a fork of the OpenTelemetry project. We are creating an “upstream first” distribution of the upstream code. All enhancements we make to AWS Distro for OpenTelemetry are contributed upstream to the OpenTelemetry project, and we consume and redistribute only changes that have been made upstream.
We plan to stay current with the upstream OpenTelemetry version, packaging new functionality from upstream regularly into this AWS distribution. New releases of AWS Distro for OpenTelemetry will use the latest versions of OpenTelemetry components.
Our roadmap is public. Please create a feature request and vote for features you want to see in AWS Distro for OpenTelemetry on the public roadmap.
Yes, AWS Distro for OpenTelemetry is open source with an Apache 2.0 License. You can contribute to all components of the AWS Distro for OpenTelemetry distribution. If the component is upstream, please contribute to the OpenTelemetry project. If the component is AWS specific, please contribute through our GitHub repositories.
For critical issues affecting your production environment, you can use AWS Support to open issues related to AWS Distro for OpenTelemetry. For feature requests and minor bug fixes, you can open an issue in the GitHub repositories for any specific component of AWS Distro for OpenTelemetry.