Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Parsing TCP traffic: redis, cassandra, ES, memcache, whatever's next #1779

@sokoow

Description

@sokoow

Feature Request

Now that your proxy is being able to oversee all TCP/HTTP traffic, it'd be nice to do some inspection of traffic for tracing purposes - so show queries and timings mostly for storage related products.

What problem are you trying to solve?

Trying to add to tracing portfoio, so our lovely developers have it even easier.

How should the problem be solved?

Well, not with the deep packet inspection I suppose.. maybe parse the request body, have a template for each product that you match, and then display it in clicky details of HTTP request ?

What do you want to happen? Add any considered drawbacks.

I'd like to see query details for mentioned products.

Any alternatives you've considered?

Nothing that other products propose unfortunately.

Is there another way to solve this problem that isn't as good a solution?

Well proxy has a first row of access to TCP/HTTP traffic, so I think it's the best way to resolve it.

How would users interact with this feature?

Linkerd UX ?

If you can, explain how users will be able to use this. Maybe some sample CLI
output?

No idea yet

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions