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.

Sign up for GitHub

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

Jump to bottom

inboundNode should be split according to resource type #299

Open
ansiz opened this issue Oct 22, 2020 · 2 comments
Open

inboundNode should be split according to resource type #299

ansiz opened this issue Oct 22, 2020 · 2 comments
Assignees
@luckyxiaoqiang
Labels
kind/enhancement Category issues or PRs related to enhancement

Comments

@ansiz
Copy link
Contributor

ansiz commented Oct 22, 2020

Issue Description

Type: feature request

希望能够将inboundNode更细粒度的拆分

Describe what feature you want

目前sentinel中所有的流量类型的数据都会计入inboundNode中，但实际上业务上可能需要更为详细的区分，以Concurrency为例，rpc、消息、网关api和http请求混合在一起时，该指标失去了原本的意义。如果能够拆分成totalRPCInbound、totalHTTPInbound、totalMQInbound，业务才能根据更加具体的统计信息决策后续的限流逻辑
@luckyxiaoqiang
Copy link
Collaborator

Please assign this to me. @louyuting

@louyuting louyuting added the kind/enhancement Category issues or PRs related to enhancement label Nov 3, 2020
@louyuting
Copy link
Collaborator

Nice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@luckyxiaoqiang luckyxiaoqiang

Labels
kind/enhancement Category issues or PRs related to enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ansiz @louyuting @luckyxiaoqiang