咨询Zipkin是否支持ActiveMQ作为收集器及所需配置

Absolutely, Zipkin does support ActiveMQ as a collector—nice to hear you're making this transition from RabbitMQ! The integration relies on JMS (Java Message Service), which is an officially supported collector type in Zipkin. Let's walk through everything you need to know to set this up smoothly.

Does Zipkin Support ActiveMQ as a Collector? #

Yes, this is a fully supported integration. Zipkin's collector component can consume trace spans sent to an ActiveMQ queue, just like it does with RabbitMQ. The main differences lie in configuration parameters and dependency setup (if you're running a custom Zipkin build).

Step-by-Step Configuration #

1. Enable ActiveMQ Collector in Zipkin #

How you set this up depends on how you're running Zipkin:

Option A: Running Zipkin via Docker (Most Common)

Use the official Zipkin Docker image and set environment variables to activate ActiveMQ support:

docker run -d -p 9411:9411 \
  -e ZIPKIN_COLLECTOR_ACTIVEMQ_ENABLED=true \
  -e ZIPKIN_COLLECTOR_ACTIVEMQ_BROKER_URL=tcp://your-activemq-server:61616 \
  # Add these lines if your ActiveMQ instance uses authentication
  -e ZIPKIN_COLLECTOR_ACTIVEMQ_USER=your-username \
  -e ZIPKIN_COLLECTOR_ACTIVEMQ_PASSWORD=your-password \
  openzipkin/zipkin

By default, Zipkin listens for spans on the zipkin queue. To use a custom queue name, add:
-e ZIPKIN_COLLECTOR_ACTIVEMQ_QUEUE=your-custom-queue-name

Option B: Running Zipkin as a Standalone JAR

If you're building Zipkin from source or running the JAR directly, first include the ActiveMQ collector dependency. For Maven, add this to your pom.xml:

<dependency>
  <groupId>io.zipkin.collector</groupId>
  <artifactId>zipkin-collector-activemq</artifactId>
  <version>${zipkin.version}</version>
</dependency>

Then start the JAR with the same environment variables as the Docker example, or pass them as system properties (e.g., -Dzipkin.collector.activemq.enabled=true).

2. Configure Tracing Clients to Send Spans to ActiveMQ #

If you're using a client like Spring Cloud Sleuth (common in Java ecosystems), update your client config to send spans via ActiveMQ instead of RabbitMQ/HTTP.

Example Spring Boot application.yml

spring:
  sleuth:
    sampler:
      probability: 1.0 # Adjust sampling rate based on your needs
  zipkin:
    sender:
      type: activemq # Tell the client to use ActiveMQ for span delivery
    activemq:
      queue: zipkin # Match this to the queue name in your Zipkin config
      broker-url: tcp://your-activemq-server:61616
      # Add these if your ActiveMQ requires authentication
      user: your-username
      password: your-password

Don't forget to add the ActiveMQ client dependency to your client project. For Spring Boot, use:

<dependency>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-starter-activemq</artifactId>
</dependency>

Key Notes to Avoid Issues #

• Queue Name Consistency: The queue name configured in Zipkin must match the one your clients are sending to—mismatched names will result in spans not being collected.
• Broker Accessibility: Ensure your Zipkin instance can reach the ActiveMQ broker (check firewalls, network rules, and that the broker is listening on the correct protocol/port).
• Payload Format: Zipkin expects spans in its native JSON format—official clients handle this automatically, but double-check payload structure if building a custom client.

内容的提问来源于stack exchange，提问作者shaks