Provide instrumentation support for lettuce-4.0-4.5.0 sync/async APIs#1398
Conversation
53d0832 to
94f56b4
Compare
tylerbenson
left a comment
There was a problem hiding this comment.
A few quick comments... I'll give it a further review next week.
149aeca to
925679c
Compare
925679c to
d158590
Compare
tylerbenson
left a comment
There was a problem hiding this comment.
Please update the PR title and description (what would a consumer of this integration find useful to know?)
Optional comments below...
|
|
||
| import static datadog.trace.instrumentation.lettuce.InstrumentationPoints.AGENT_CRASHING_COMMAND_PREFIX | ||
|
|
||
| class LettuceAsyncClientTest extends AgentTestRunner { |
There was a problem hiding this comment.
Is there any logic that can be shared between the sync/async tests?
| // Workaround to keep trace agent from crashing | ||
| // Currently the commands in AGENT_CRASHING_COMMANDS_WORDS will crash the trace agent and | ||
| // traces with these commands as the resource name will not be processed by the trace agent | ||
| // https://github.com/DataDog/datadog-trace-agent/blob/master/quantizer/redis.go#L18 has |
There was a problem hiding this comment.
This url is now out of date... maybe find the new one?
There was a problem hiding this comment.
I looked for it, but couldn't find it, there seems to have been major refactoring here.
There was a problem hiding this comment.
I have removed the link but will follow up to see if this logic can actually just be removed in another PR.
There was a problem hiding this comment.
No description provided.