-
Notifications
You must be signed in to change notification settings - Fork 573
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
Add otel logs to rideshare #2476
Add otel logs to rideshare #2476
Conversation
420ae52
to
f241af5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Dont understand why updating otel in rideshare requires updates in separate modules? Cant different modules have different dependencies?
Maybe sometime later we should remove rideshare examples from the workspace
nit: may be it is worth considering cherry-pick dskit upgrade in a separate PR |
No idea why it is part of the workspace, maybe the go push library was part of this repo at some point. But the fact it is in the same workspace forces the same grpc version, that then requires dskit upgrades. Once I am back at the keyboard I will split it or just remove it from the workspace. |
Once I remove it from go.work, it seems to ignore the local go.mod file and can't build it anymore. This is very weird:
|
f241af5
to
e9535ae
Compare
maybe GOWORK=off can help building?
|
Yeah that works, unsure if we should keep it in the go.work file then? |
Ok I think an "empty" go work file in the examples also does the trick 🙂 |
e9535ae
to
23552c2
Compare
In order to show better how the data signals connect I am adding a otel log pusher to our rideshare demo.
Note: The upgrade of otel required an upgrade of dskit, which needed some refactoring in commit f241af5.
Unfortunately the rideshare-app does not log at present, so I had to add a bit of logging as well
Screen.Recording.2023-10-03.at.16.04.21.mov