-
Notifications
You must be signed in to change notification settings - Fork 187
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
[Jaeger] Add X-Request-ID to the metadata #1022
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions. |
still needed. will become hot when the first real use of ocis is approaching. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions. |
@butonic the API test suite is sending |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions. |
The X-Request-ID was added to the first span and to all possible log output. |
All ownCloud (desktop-/mobile-/web-)clients already send
X-Request-ID
HTTP header with every request. They're shown in the client logfiles, and in the beginning of every line of theowncloud.log
. They can also be easily added to the Apache log and to the logs from various middleware.As far as I know, they're not really used from oCIS yet. (maybe in the logs?)
A beginning could be, to add the
X-Request-ID
HTTP header to the Jaeger metadata…In the future, clients could also support opentelemetry.io:
@C0rby @micbar @dragotin
The text was updated successfully, but these errors were encountered: