Skip to content
Reporters and collectors for use in Amazon's cloud
Java Shell Dockerfile
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
.mvn/wrapper version bumps Sep 29, 2019
aws-junit [maven-release-plugin] prepare for next development iteration Nov 6, 2019
brave-instrumentation
brave-propagation-aws
collector-kinesis [maven-release-plugin] prepare for next development iteration Nov 6, 2019
collector-sqs [maven-release-plugin] prepare for next development iteration Nov 6, 2019
docker Updates to zipkin 2.18 and fixes region config (#146) Oct 16, 2019
module
reporter-xray-udp [maven-release-plugin] prepare for next development iteration Nov 6, 2019
sender-awssdk-sqs [maven-release-plugin] prepare for next development iteration Nov 6, 2019
sender-kinesis [maven-release-plugin] prepare for next development iteration Nov 6, 2019
sender-sqs [maven-release-plugin] prepare for next development iteration Nov 6, 2019
src/etc
storage-xray-udp [maven-release-plugin] prepare for next development iteration Nov 6, 2019
travis Version updates Jul 5, 2019
.dockerignore Add a Dockerfile that can build master. Aug 30, 2019
.gitignore Updates versions and maven wrapper (#123) Mar 2, 2019
.settings.xml
.travis.yml
LICENSE
README.md Updates to zipkin 2.18 and fixes region config (#146) Oct 16, 2019
RELEASE.md
mvnw Updates to ASF Zipkin and decouples storage-elasticsearch-aws (#130) May 11, 2019
mvnw.cmd
pom.xml [maven-release-plugin] prepare for next development iteration Nov 6, 2019

README.md

Gitter chat Build Status Maven Central

zipkin-aws

Shared libraries that provide Zipkin integration with AWS Kinesis and SQS. Requires JRE 6 or later.

Usage

These components provide Zipkin Senders and Collectors which build off interfaces provided by the zipkin-reporters-java and zipkin projects.

Senders

The component in a traced application that sends timing data (spans) out of process is called a Sender. Senders are called on interval by an async reporter.

NOTE: Applications can be written in any language, while we currently only have senders in Java, senders in other languages are welcome.

Sender Description
SQS An alternative to Kafka.
Kinesis An alternative similar to Kafka.

Collectors

The component in a zipkin server that receives trace data is called a collector. This decodes spans reported by applications and persists them to a configured storage component.

Collector Description
SQS An alternative to Kafka.
Kinesis An alternative to Kafka.

Server integration

In order to integrate with zipkin-server, you need to use properties launcher to load your collector (or sender) alongside the zipkin-server process.

To integrate a module with a Zipkin server, you need to:

  • add a module jar to the loader.path
  • enable the profile associated with that module
  • launch Zipkin with PropertiesLauncher

Each module will also have different minimum variables that need to be set.

Ex.

$ java -Dloader.path=sqs.jar -Dspring.profiles.active=sqs -cp zipkin.jar org.springframework.boot.loader.PropertiesLauncher

Example integrating the SQS Collector

If you cannot use our Docker image, you can still integrate yourself by downloading a couple jars. Here's an example of integrating the SQS Collector.

Step 1: Download zipkin-server jar

Download the latest released server as zipkin.jar:

cd /tmp
curl -sSL https://zipkin.io/quickstart.sh | bash -s

Step 2: Download the latest sqs-module jar

Download the latest released SQS module as sqs.jar:

cd /tmp
curl -sSL https://zipkin.io/quickstart.sh | bash -s io.zipkin.aws:zipkin-module-collector-sqs:LATEST:module sqs.jar

Step 3: Run the server with the "sqs" profile active

When you enable the "sqs" profile, you can configure sqs with short environment variables similar to other Zipkin integrations.

cd /tmp
SQS_QUEUE_URL=<from aws sqs list-queues> \
    java \
    -Dloader.path='sqs.jar,sqs.jar!/lib' \
    -Dspring.profiles.active=sqs \
    -cp zipkin.jar \
    org.springframework.boot.loader.PropertiesLauncher

** NOTE: Make sure the parameters are defined in the same line or use environment variables **

Artifacts

All artifacts publish to the group ID "io.zipkin.aws". We use a common release version for all components.

Library Releases

Releases are uploaded to Bintray and synchronized to Maven Central

Library Snapshots

Snapshots are uploaded to JFrog after commits to master.

You can’t perform that action at this time.