Improve req handling dashboard

[naseemkullah]

What this PR does / why we need it:

Display per method/path combos for various metrics, adjust titles, and sort tooltip by decreasing

Types of changes

• New feature (non-breaking change which adds functionality)

Which issue/s this PR fixes

How Has This Been Tested?

Actively using this dashboard, worth noting original committer of it

[k8s-ci-robot]

@naseemkullah: This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

Hi @naseemkullah. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[longwuyuan]

• Create an issue and put all the details of the problem you are trying to solve in that issue
• Link that issue to this PR
• Show screenshot of current problem here
• Show screenshot of improvement using your fork's modified content also here

[naseemkullah]

• Create an issue and put all the details of the problem you are trying to solve in that issue
• Link that issue to this PR
• Show screenshot of current problem here
• Show screenshot of improvement using your fork's modified content also here

Can we skip issue creation?

we get method cardinality for the various latency metrics, also polished the titles (casing, improved names)

tooltip: values are sorted form high to low

If this does not suffice please feel free to close

[longwuyuan]

@naseemkullah , thanks you very much for your contribution. It helps .

• The intention is not a "close" but the intention is to populate enough information here, so that revisits and maintenance does not become a challenge.
• I see at at least 10-15 edits in the commit but there is no issue created to track what those edits are for and there is no information on those edits here except these 2 screenshots you have added. Would you be interested in adding more information as to what you found as problem(s) and what the several edits amount to.
• At least the 2 screenshots are an improvement that is clearly visible so definitely suggesting we merge. Just wish for more info/documentation of the changes

/ok-to-test

[naseemkullah]

Most changed lines are the updated Grafana version exporting with new schema, maybe I should run a 6.x Grafana to do the export of this if preferred I can look into this, alternatively if you use nginx ingress and Grafana yourself import this dashboard and have a look

[longwuyuan]

I was hoping it to be documented here so anyone can maintain it. I can impor dashboard on my cluster, but I will be a dependency then. I have already labeled ok-to-test. Let's wait for comments and labels from others. Thanks, ; Long

…

On Fri, 11 Mar, 2022, 8:57 AM naseemkullah, ***@***.***> wrote: Most changed lines are the updated Grafana version exporting with new schema, maybe I should run a 6.x Grafana to do the export of this if preferred I can look into this, alternatively if you use nginx ingress and Grafana yourself import this dashboard and have a look — Reply to this email directly, view it on GitHub <#8322 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGZVWWVXPTLO5522FYAJN3U7K4RPANCNFSM5QNEWYRA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[rikatz]

/lgtm
/approve
Thanks :)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: naseemkullah, rikatz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [rikatz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment