Skip to content

[FEATURE]: for redis cluster, don't report MOVED responses as errors #4296

Open
@mbyio

Description

@mbyio

Gem Name

No response

Gem Version(s)

No response

Describe the goal of the feature

Hi! I would love if we could have the option to record MOVED responses as non-errors when tracing a Redis Cluster client. MOVED responses are not really errors, they just mean the cluster client has to retry with a different node. They are more like an HTTP 301 redirect. So, recording them as MOVED messes with our error rate metrics.

Is your feature request related to a problem?

Redis MOVED responses are recorded as errors, which causes incorrect error rate metrics.

Describe alternatives you've considered

It may be possible to fix this with monkey patching, but it is pretty tricky. Also, I think it is behavior a lot of people would want. I noticed that some other integrations also provide ways to customize what is considered an error, and maybe that would be appropriate for redis too.

Additional context

No response

How does Datadog help you?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    communityWas opened by a community memberfeature-requestA request for a new feature or change to an existing one

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions