linkerd2 icon indicating copy to clipboard operation
linkerd2 copied to clipboard

Can Linkerd2 tap support printing response body?

Open wanggithub08 opened this issue 2 years ago • 7 comments

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

wanggithub08 avatar Apr 28 '22 09:04 wanggithub08

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[bot] avatar Aug 08 '22 20:08 stale[bot]

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.

philomory avatar Aug 08 '22 21:08 philomory

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.

adleong avatar Aug 11 '22 21:08 adleong

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?

sovereignstack avatar Sep 28 '22 20:09 sovereignstack

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[bot] avatar Dec 27 '22 23:12 stale[bot]

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 avatar Jan 05 '23 22:01 kleimkuhler

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

pradychefling avatar Nov 09 '23 06:11 pradychefling