You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
143927: split: add an access direction metric and log r=angles-n-daemons a=angles-n-daemons
split: add an access direction metric and log
Similar to how the split decider logs and increments a counter when a popular key is found, here we do the same for when the access direction is > 80% left or right (descending or ascending).
Fixes: #142208
Epic: CRDB-43150
Release note: Adds a new metric `kv.loadsplitter.cleardirection` which increments when replica samples are found to be moving in a uniform direction.
144567: eventpb: move hot range log events to the health channel r=angles-n-daemons a=angles-n-daemons
eventpb: move hot range log events to the health channel
As title states, currently hot range logs are emitted on the OPS channel. This is a change we made recently, and we've revised our targeted destination to be the HEALTH channel.
Fixes: #143512
Epic: CRDB-43150
Release note (ops change): Moves the hot range logs to the HEALTH channel.
144612: sql: update sql metric definition to support configurable labels r=aa-joshi a=aa-joshi
This patch updates sql metric declaration to support additional `database` and
`application_name` as labels. This is driven by cluster settings introduced as
part of #144610. The updated metrics will export additional labels based on
cluster settings `sql.metrics.application_name.enabled` and
`sql.metrics.database_name.enabled`. The SQLMetric will persist aggregate sum
of all its children, while children additionally exported to prometheus.
Epic: [CRDB-43153](https://cockroachlabs.atlassian.net/browse/CRDB-43153)
Part of: [CRDB-48251](https://cockroachlabs.atlassian.net/browse/CRDB-48251)
Release note: None
Updated metrics along with their `internal` counterpart (if exists):
- cr.node.sql.txns.open
- cr.node.sql.txn.latency
- cr.node.sql.txn.begin.count
- cr.node.sql.txn.commit.count
- cr.node.sql.txn.rollback.count
- cr.node.sql.statements.active
- cr.node.sql.update.count
- cr.node.sql.update.count
- cr.node.sql.insert.count
- cr.node.sql.delete.count
- cr.node.sql.crud.count
- cr.node.sql.service.latency
- cr.node.sql.distsql.contended_queries.count
- sql.distsql.cumulative_contention_nanos
- cr.node.sql.failure.count
- cr.node.sql.full.scan.count
Co-authored-by: Brian Dillmann <[email protected]>
Co-authored-by: Akshay Joshi <[email protected]>
Copy file name to clipboardExpand all lines: docs/generated/metrics/metrics.html
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -202,6 +202,7 @@
202
202
<tr><td>STORAGE</td><td>kv.concurrency.max_lock_hold_duration_nanos</td><td>Maximum length of time any lock in a lock table is held. Does not include replicated locks (intents) that are not held in memory</td><td>Nanoseconds</td><td>GAUGE</td><td>NANOSECONDS</td><td>AVG</td><td>NONE</td></tr>
203
203
<tr><td>STORAGE</td><td>kv.concurrency.max_lock_wait_duration_nanos</td><td>Maximum lock wait duration across requests currently waiting in lock wait-queues</td><td>Nanoseconds</td><td>GAUGE</td><td>NANOSECONDS</td><td>AVG</td><td>NONE</td></tr>
204
204
<tr><td>STORAGE</td><td>kv.concurrency.max_lock_wait_queue_waiters_for_lock</td><td>Maximum number of requests actively waiting in any single lock wait-queue</td><td>Lock-Queue Waiters</td><td>GAUGE</td><td>COUNT</td><td>AVG</td><td>NONE</td></tr>
205
+
<tr><td>STORAGE</td><td>kv.loadsplitter.cleardirection</td><td>Load-based splitter observed an access direction greater than 80% left or right in the samples.</td><td>Occurrences</td><td>COUNTER</td><td>COUNT</td><td>AVG</td><td>NON_NEGATIVE_DERIVATIVE</td></tr>
205
206
<tr><td>STORAGE</td><td>kv.loadsplitter.nosplitkey</td><td>Load-based splitter could not find a split key.</td><td>Occurrences</td><td>COUNTER</td><td>COUNT</td><td>AVG</td><td>NON_NEGATIVE_DERIVATIVE</td></tr>
206
207
<tr><td>STORAGE</td><td>kv.loadsplitter.popularkey</td><td>Load-based splitter could not find a split key and the most popular sampled split key occurs in >= 25% of the samples.</td><td>Occurrences</td><td>COUNTER</td><td>COUNT</td><td>AVG</td><td>NON_NEGATIVE_DERIVATIVE</td></tr>
207
208
<tr><td>STORAGE</td><td>kv.prober.planning_attempts</td><td>Number of attempts at planning out probes made; in order to probe KV we need to plan out which ranges to probe;</td><td>Runs</td><td>COUNTER</td><td>COUNT</td><td>AVG</td><td>NON_NEGATIVE_DERIVATIVE</td></tr>
0 commit comments