config: add a new measurement to watchlist job type

[p0lyn0mial]

WatchListLatencyPrometheus measurement gathers 50th, 90th and 99th duration quantiles for watch list requests broken down by group, resource, scope.

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR adds WatchListLatencyPrometheus measurement to watchlist job type. The new measurement gathers 50th, 90th and 99th duration quantiles for watch list requests broken down by group, resource, scope.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

The new measurement was added in https://github.com/kubernetes/perf-tests/pull/2315

xref: https://github.com/kubernetes/enhancements/issues/3157

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: p0lyn0mial Once this PR has been reviewed and has the lgtm label, please assign mborsz for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• perfdash/OWNERS

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

[p0lyn0mial]

/hold

we should merge https://github.com/kubernetes/perf-tests/pull/2315 first.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[p0lyn0mial]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[p0lyn0mial]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[p0lyn0mial]

I think we can close this PR because watch-list latency was added to APIResponsivenessPrometheus in https://github.com/kubernetes/perf-tests/pull/2764

/close

[k8s-ci-robot]

@p0lyn0mial: Closed this PR.

In response to this:

I think we can close this PR because watch-list latency was added to APIResponsivenessPrometheus in https://github.com/kubernetes/perf-tests/pull/2764

/close

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-sigs/prow repository.