-
Notifications
You must be signed in to change notification settings - Fork 0
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
[SERF-3255] Add Redis client configuration and instrumentation #104
Conversation
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.
I did a really quick pass – will remove the documentation next week.
Overall it looks great – left 2 small comments.
Thank you @Neurostep! 🌮
11a229c
to
40f3beb
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 🚀
40f3beb
to
82666f5
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
We have cache now 🎉
82666f5
to
07f0a59
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
Description
In this PR we introduce a new configuration and instrumentation package: Redis.
We use official go-redis client and the dd-trace-go wrapper for instrumentation.
PLEASE NOTE: in this PR we have to upgrade a few widely used libraries, such as
dd-trace-go
andaws-sdk-go
. This is the case because thego-redis
wrapper in thedd-trace-go
library is supported in the later versions only. Upgrade of thedd-trace-go
transitively upgraded theaws-sdk-go
. All upstream services will be carefully tested with this change.Testing considerations
go-chassis
and check tracesChecklist
development
and/orstaging
README.md
as necessaryRelated links