Admission Control: Essential Metrics Classification & Cloud Integration Updates

[kevin-v-ngo]

Context

This issue tracks updates to Admission Control (AC) metrics based on review of which metrics meet the bar for Essential status:

• Clear monitoring / troubleshooting valuex
• Stability
• Production guarantees

Playbook to add metrics.

Promote to Essential + Add to Cloud Integrations for Advanced cluster

Core resource indicators

• sys.cpu.combined.percent-normalized (already Essential, need to add to Cloud integration)
• sys.runnable.goroutines.per.cpu (already Essential, need to add to Cloud integration)

Admission Control

• admission.wait_durations.sql-kv-response-p99

• admission.wait_durations.sql-sql-response-p99

• admission.wait_durations.elastic-stores-p99

• admission.wait_durations.elastic-cpu-p99

• admission.granter.slots_exhausted_duration.kv

• admission.granter.io_tokens_exhausted_duration.kv

• admission.granter.elastic_io_tokens_exhausted_duration.kv

• admission.elastic_cpu.nanos_exhausted_duration

• kvflowcontrol.eval_wait.regular.duration-p99

• kvflowcontrol.eval_wait.elastic.duration-p99

• kvflowcontrol.send_queue.bytes

Epic: CRDB-35697

Jira issue: CRDB-59506

[blathers-crl]

Hi @kevin-v-ngo, please add a branch-* label to identify the earliest affected branch for this C-bug

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

[blathers-crl]

This issue has multiple T-eam labels. Please make sure it only has one, or else issue synchronization will not work correctly.

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

[blathers-crl]

This issue has multiple T-eam labels. Please make sure it only has one, or else issue synchronization will not work correctly.

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