release-24.1: kvcoord: add a metric for number of partial batches in progress

[blathers-crl[bot]]

Backport 1/1 commits from #134092 on behalf of @yuzefovich.

/cc @cockroachdb/release

---

It has been shown that adjusting kv.dist_sender.concurrency_limit cluster setting can improve the performance significantly. We currently already have two relevant counters:

• distsender.batches.async.sent tracks the total number of partial KV batches that have been executed in parallel since the node restart
• distsender.batches.async.throttled is the total number of times we tried to send a partial KV batch but couldn’t because we exhausted the kv.dist_sender.concurrency_limit.

This commit additionally introduces distsender.batches.async.in_progress gauge to indicate how many partial batch are being executed asynchronously at any point in time.

Fixes: #131125.

Release note: None

---

Release justification: low-risk observability improvement.

[blathers-crl[bot]]

Thanks for opening a backport.

Please check the backport criteria before merging:

• [ ] Backports should only be created for serious issues or test-only changes.
• [ ] Backports should not break backwards-compatibility.
• [ ] Backports should change as little code as possible.
• [ ] Backports should not change on-disk formats or node communication protocols.
• [ ] Backports should not add new functionality (except as defined here).
• [ ] Backports must not add, edit, or otherwise modify cluster versions; or add version gates.
• [ ] All backports must be reviewed by the owning areas TL. For more information as to how that review should be conducted, please consult the backport policy.

If your backport adds new functionality, please ensure that the following additional criteria are satisfied:

- [ ] There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way. - [ ] The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting). - [ ] New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters. State changes must be further protected such that nodes running old binaries will not be negatively impacted by the new state (with a mixed version test added). - [ ] The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules. - [ ] Your backport must be accompanied by a post to the appropriate Slack channel (#db-backports-point-releases or #db-backports-XX-X-release) for awareness and discussion.

Also, please add a brief release justification to the body of your PR to justify this backport.

[blathers-crl[bot]]

It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR?

_{:owl: Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[cockroach-teamcity]

This change is