Skip to content

Fix tracing startup: Jaeger via OTLP/gRPC + update tracing orbit deps#13708

Open
manodyaSenevirathne wants to merge 2 commits intowso2:masterfrom
manodyaSenevirathne:fix/jaeger-zipkin
Open

Fix tracing startup: Jaeger via OTLP/gRPC + update tracing orbit deps#13708
manodyaSenevirathne wants to merge 2 commits intowso2:masterfrom
manodyaSenevirathne:fix/jaeger-zipkin

Conversation

@manodyaSenevirathne
Copy link
Copy Markdown
Contributor

@manodyaSenevirathne manodyaSenevirathne commented Mar 30, 2026

Purpose

Resolves :

Changes

  • Switch “jaeger” telemetry implementation to OTLP/gRPC exporter.
  • Update default port for Jaeger telemetry to OTLP/gRPC 4317.
  • Bump orbit dependencies for Jaeger client + Zipkin reporter sender versions.

Orbit PR

Testing

Tested the setup mentioned in [1] , traces were visible in both jaeger and zipkin dashboards

[1] - https://apim.docs.wso2.com/en/latest/monitoring/observability/traces/monitoring-with-opentelemetry/

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Mar 30, 2026

Warning

Rate limit exceeded

@manodyaSenevirathne has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 16 minutes and 11 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 16 minutes and 11 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 6ddf80bf-ad3a-4af2-bc00-09a68b2792ee

📥 Commits

Reviewing files that changed from the base of the PR and between c9848da and 4c6abeb.

📒 Files selected for processing (3)
  • components/apimgt/org.wso2.carbon.apimgt.tracing/src/main/java/org/wso2/carbon/apimgt/tracing/telemetry/JaegerTelemetry.java
  • components/apimgt/org.wso2.carbon.apimgt.tracing/src/main/java/org/wso2/carbon/apimgt/tracing/telemetry/TelemetryConstants.java
  • pom.xml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates APIM tracing so the “jaeger” OpenTelemetry tracer exports spans via OTLP/gRPC (to address Jaeger startup/visibility issues) and refreshes related Jaeger/Zipkin orbit dependency versions.

Changes:

  • Switch Jaeger telemetry exporter from JaegerGrpcSpanExporter to OtlpGrpcSpanExporter.
  • Update the Jaeger telemetry default port to OTLP/gRPC default 4317.
  • Bump Jaeger client and Zipkin reporter/sender dependency versions in the root pom.xml.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File Description
pom.xml Bumps Jaeger/Zipkin versions (orbit + zipkin-reporter) to align with updated tracing stack.
.../telemetry/TelemetryConstants.java Changes Jaeger default port from 14250 to 4317 to match OTLP/gRPC defaults.
.../telemetry/JaegerTelemetry.java Replaces Jaeger gRPC exporter with OTLP/gRPC exporter for “jaeger” tracer.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants