Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Custom URI with OpenTelemetry SDK #99

Closed
orrn opened this issue Jul 11, 2024 · 3 comments
Closed

Support for Custom URI with OpenTelemetry SDK #99

orrn opened this issue Jul 11, 2024 · 3 comments

Comments

@orrn
Copy link

orrn commented Jul 11, 2024

Hello,

I am currently using APISIX version 3.9.1 and have integrated opentelemetry.lua for tracing purposes. My setup involves using Alibaba Cloud's collector, which does not utilize the default /v1/traces URI for trace collection.

I would like to request the ability to customize the URI used for sending traces in the OpenTelemetry plugin. This feature would greatly enhance the flexibility of APISIX's tracing capabilities, especially for those of us using different backends or cloud providers that may not adhere to the default URI paths.

Thank you for considering this enhancement.

@orrn
Copy link
Author

orrn commented Jul 11, 2024

#100

@yangxikun
Copy link
Owner

Does PR #101 fix this issue?
You can set a custom URI path in the address parameter, such as http://aaa.com/another/traces.

@orrn
Copy link
Author

orrn commented Jul 22, 2024

This is exactly what I wanted. Thank you very much.

@orrn orrn closed this as completed Jul 22, 2024
yangxikun added a commit that referenced this issue Jul 24, 2024
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

No branches or pull requests

2 participants