Skip to content
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

[FEATURE] About #1364 and #1374 Gone From the Redis Agent #2252

Open
ededddy opened this issue Jan 12, 2024 · 6 comments
Open

[FEATURE] About #1364 and #1374 Gone From the Redis Agent #2252

ededddy opened this issue Jan 12, 2024 · 6 comments
Labels
Milestone

Comments

@ededddy
Copy link

ededddy commented Jan 12, 2024

While adding Redis Tracing for my company, I found out that the agent provided is not capturing the whole statement, but just the command was captured.

Then I looked up the issue on this GitHub. I found out that the feature was implemented in
#1374 Get Command and Key for StackExchange.Redis spans
which is intended for feature request
#1364 [FEATURE] Registering query parameters for 'StackExchange.Redis' spans

And from v1.11.0 to v1.22.0 the function still exists and can capture the whole statement.

However, starting from v1.23.0, which the instrument was moved to another folder, the method is gone.

Is it possible that we can add the feature back?
Or is there other concerns that need to remove this feature?

Tasks

Preview Give feedback
No tasks being tracked yet.
@ededddy ededddy added the enhancement New feature or request label Jan 12, 2024
@ededddy ededddy changed the title [FEATURE] About #1364 and #1374 Gone From the Agent [FEATURE] About #1364 and #1374 Gone From the Redis Agent Jan 12, 2024
@kuanpak
Copy link
Contributor

kuanpak commented Feb 24, 2024

I believe it's codebase synchronization issue. Is it possible to add back #1374 into the current release?

@grietine
Copy link

grietine commented Apr 3, 2024

Writing this as a regression, previously you've added this part in #1364 and now it's gone again. Why it was removed?

This is the place where it was removed:
#2104

@stevejgordon
Copy link
Contributor

Apologies for this. We will work on this to bring any lost features back.

@stevejgordon stevejgordon added this to the 8.14 milestone Apr 4, 2024
@stevejgordon stevejgordon modified the milestones: v1.27.0, v1.28.0 Apr 29, 2024
@grietine
Copy link

As well to the same issue: we noticed that the previous working version didn't show the statement for SCAN, EVAL, EXEC commands (the statement is visible for GET, SET, SETEX). Why is that?

@stevejgordon
Copy link
Contributor

@grietine If those are new feature requests, would you mind opening a separate issue to request them? Let's keep this issue to the regression.

@grietine
Copy link

grietine commented May 15, 2024

@grietine If those are new feature requests, would you mind opening a separate issue to request them? Let's keep this issue to the regression.

Sure, I've added a feature request: #2352

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants