[go: nahoru, domu]

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

Can Linkerd2 tap support printing response body? #8359

Open
wanggithub08 opened this issue Apr 28, 2022 · 7 comments
Open

Can Linkerd2 tap support printing response body? #8359

wanggithub08 opened this issue Apr 28, 2022 · 7 comments

Comments

@wanggithub08
Copy link

What problem are you trying to solve?

I want to send the body content (decoded) lets say to elastic-search or write in to a file.

How should the problem be solved?

I execute the command: linkerd viz tap -n booksapp deploy/webapp -o wide ,and can see the response code and response length.Can it add body print options?

Any alternatives you've considered?

I haven't thought of it yet.

How would users interact with this feature?

No response

Would you like to work on this feature?

maybe

@stale
Copy link
Stale bot commented Aug 8, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

@stale Stale bot added the wontfix label Aug 8, 2022
@philomory
Copy link
philomory commented Aug 8, 2022

I'd like to see this as well, although want I'd it more as a live debugging aid, rather than actually logging the response body to something like elasticsearch.

@stale Stale bot removed wontfix labels Aug 8, 2022
@adleong
Copy link
Member
adleong commented Aug 11, 2022

Linkerd does not support printing the message bodies in tap, but this is something that's certainly on the long-term roadmap. The work to add this feature has not yet been prioritized.

@sovereignstack
Copy link

This is the number one feature (wrongly assumed) I installed Linkerd for while trying to debug an issue. With micro services there is no good tool to look at messages being exchanged between micro services. This functionality is often needed for debugging. The alternative is to make the micro services log their requests but that's code change and we don't control code in all containers. Plus this is an operational requirement which is ideally solved in the service mesh than application code. Can you please consider implementing this?

@stale
Copy link
Stale bot commented Dec 27, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

@stale Stale bot added the wontfix label Dec 27, 2022
@kleimkuhler
Copy link
Contributor

We don't currently have a meta issue for this, so we're going to keep this open so that it serves as something future users can reference for any updates. However, it's currently not prioritized in any way so there is no timeframe for when this would be supported.

@kleimkuhler kleimkuhler added pinned and removed wontfix labels Jan 5, 2023
@pradychefling
Copy link

Is there any updates on this? Even This was one of the main reasons we went for linkerd

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

No branches or pull requests

6 participants