Remove orphaned tag-alias-check job left by the merge (#295)
PR #294 was scoped down to just the S3 download+signature monitor before merge, which deleted check-tag-aliases.sh. The squash-merge kept the file deletion but not the corresponding removal of the tag-alias-check job from continuous-monitoring.yml, so master has a job that runs .github/scripts/check-tag-aliases.sh – a file that no longer exists. That job fails on every scheduled run.
Remove the orphaned job block; the referenced script is already gone.
Co-authored-by: Syed Ahsan Ishtiaque syed-ahsan-ishtiaque@users.noreply.github.com
版权所有:中国计算机学会技术支持:开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802047560号
AWS X-Ray Daemon
The AWS X-Ray daemon is a software application that listens for traffic on UDP port 2000, gathers raw segment data, and relays it to the AWS X-Ray API.
The daemon works in conjunction with the AWS X-Ray SDKs and must be running so that data sent by the SDKs can reach the X-Ray service. For more information, see AWS X-Ray Daemon.
The AWS X-Ray Daemon will enter maintenance mode on
February 25, 2026. During maintenance mode, the X-Ray SDKs and Daemon will only receive critical bug fixes and security updates, and will not be updated to support new features.We recommend that you migrate to AWS Distro for OpenTelemetry (ADOT) or OpenTelemetry Instrumentation to generate traces (through manual or zero-code instrumentation) from your application and send them to AWS X-Ray. OpenTelemetry is the industry-wide standard for tracing instrumentation and observability. It has a large open-source community for support and provides more instrumentations and updates. By adopting an OpenTelemetry solution, developers can leverage the latest services and innovations from AWS CloudWatch.
To gather traces from OpenTelemetry instrumentation and relay them to AWS X-Ray, you can use OpenTelemetry-compatible solutions such as the CloudWatch Agent, or the OpenTelemetry Collector. Read more about migrating to OpenTelemetry-compatible solutions to replace the X-Ray Daemon in the migration guide.
Getting Help
Use the following community resources for getting help with the AWS X-Ray Daemon. We use the GitHub issues for tracking bugs and feature requests.
Sending Segment Documents
The X-Ray SDK sends segment documents to the daemon to avoid making calls to AWS directly. You can send the segment/subsegment in JSON over UDP port 2000 to the X-Ray daemon, prepended by the daemon header :
{"format": "json", "version": 1}\nFor more details refer : Link
Installing
The AWS X-Ray Daemon is compatible with Go 1.8 and later.
Install the daemon using the following command:
Credential Configuration
The AWS X-Ray Daemon follows default credential resolution for the aws-sdk-go.
Follow the guidelines for the credential configuration.
Daemon Usage (command line args)
Usage: xray [options]
Build
make buildwould build binaries and .zip files in/buildfolder for Linux, MacOS, and Windows platforms.Linux
make build-linuxwould build binaries and .zip files in/buildfolder for the Linux platform.MAC
make build-macwould build binaries and .zip files in/buildfolder for the MacOS platform.Windows
make build-windowswould build binaries and .zip files in/buildfolder for the Windows platform.Build for ARM achitecture
Currently, the
make buildscript builds artifacts for AMD architecture. You can build the X-Ray Daemon for ARM by using thego buildcommand and setting theGOARCHtoarm64. To build the daemon binary on a linux ARM machine, you can use the following command:As of Aug 31, 2020, windows and darwin builds for ARM64 are not supported by
go build.Pulling X-Ray Daemon image from ECR Public Gallery
Before pulling an image you should authenticate your docker client to the Amazon ECR public registry. For registry authentication options follow this link
Run below command to authenticate to public ECR registry using
get-login-password(AWS CLI)aws ecr-public get-login-password --region us-east-1 | docker login --username AWS --password-stdin public.ecr.awsPull alpha tag from Public ECR Gallery
docker pull public.ecr.aws/xray/aws-xray-daemon:alphaPull released version tag from Public ECR Gallery
docker pull public.ecr.aws/xray/aws-xray-daemon:3.2.0NOTE: We are not recommending to use daemon image with alpha tag in production environment. For production environment customer should pull in an image with released tag.
X-Ray Daemon Performance Report
EC2 Instance Type: T2.Micro [1 vCPU, 1 GB Memory]
Collection time: 10 minutes per TPS (TPS = Number of segments sent to daemon in 1 second)
Daemon version tested: 3.3.6
Testing
make testwill run unit tests for the X-Ray daemon.License
This library is licensed under the Apache 2.0 License.