hiltvan.blogg.se - Adot quickmap

#Adot quickmap how to#
#Adot quickmap install#

You can pull any of the images from there, however, we will not support any issues and pull requests for these test images. This image is used for the integration tests. However, if you have AWS Enterprise Support you can create a ticket and we will provide direct support within the respective SLAs.įor each merged pull request, a corresponding image with the naming convention of - is pushed to /aws-otel-test/adot-collector-integration-test. Please note that as per policy, we're providing support via GitHub on a best effort basis. The performance test can be conducted by following the instructions here. The charts use the github-action-benchmark action and uses a modified layout to group the testcases. The latest performance report is here, while the trends by testcase can be found here.īoth are updated on each successful CI run.

Use the following instructions to build your own ADOT Collector artifacts:

#Adot quickmap how to#

Here are some examples on how to run the ADOT Collector to send telemetry data: The ADOT Collector supports all AWS computing platforms and Docker/Kubernetes. Please refer to the Try out ADOT Collector section on configuring ADOT Collector. So you can customize or port your OpenTelemetry Collector configuration files when running ADOT Collector. For more information regarding OpenTelemetry Collector configuration please refer to the upstream documentation. The ADOT Collector configuration uses the same configuration syntax/design from OpenTelemetry Collector. The ADOT Collector is built with a default configuration.

#Adot quickmap install#

You can download and install Golang here. To build the ADOT Collector locally, you will need to have Golang installed. More documentation for confmap providers can be found here. Receiverīesides the components that interact with telemetry signals directly from the previous table, there is also support to the following confmap providers: The rest of the components in the table are the essential default components that the ADOT Collector will support. The highlighted components below are developed by AWS in-house.

This table represents the supported components of the ADOT Collector. Users of the prometheus receiver, prometheus exporter or prometheusremotewrite exporter please reference GitHub Issue Warning: ADOT Collector v0.31.0 breaking changeįor information on an upcoming breaking change. Notice: ADOT Collector v0.31.0 Breaking Change

For contributing guidelines, refer to CONTRIBUTING.md.

If you think you may have found a bug, open a bug report.

Join our GitHub Community for AWS Distro for OpenTelemetry to ask your questions, file issues, or request enhancements.

Use GitHub issues to report bugs and request features.

Open a support ticket with AWS Support.

Use the community resources below for getting help with the ADOT Collector. Additionally, the ADOT Collector is now generally available for metrics. See the AWS Distro for OpenTelemetry documentation for more information. It enables users to send telemetry data to AWS CloudWatch Metrics, Traces, and Logs backends as well as the other supported backends. It is fully compatible with AWS computing platforms including EC2, ECS, and EKS. It supports the selected components from the OpenTelemetry community. AWS Distro for OpenTelemetry Collector (ADOT Collector) is an AWS supported version of the upstream OpenTelemetry Collector and is distributed by Amazon.