storage_capacity metric and related DBConsole graphs should not start from 0

Open

#94,846 opened on Jan 6, 2023 3 comments 0 reactions 1 assignee Claimed by @dhartunian View on GitHub

A-observability-inf C-bug O-community T-storage X-blathers-triaged

Dominant language: Go
Stars: 32.5k
Forks: 4.1k
PR merge metrics: PR metrics pending

Description

**Describe the problem**

The behavior of the metrics `storage_capacity` has changed in version 22.1/22.2 and appears to be a regression bug.

In v21.2 when a node is started the graph for `storage_capacity` start from the correct value, but in v22.1 and v22.2 the graph start from 0 when the node is restarted showing something that is not actually correct until the real value is displayed. This behavior is seen in DB Console and custom TS charts, see attached screenshots.

**Expected behavior**

Restore the original behavior seen in 21.2

**Additional data / screenshots**

DB Console
![image](https://user-images.githubusercontent.com/8233381/211074518-34c44924-129e-42b1-afba-125d2c830531.png)

Custom TS Chart
![image](https://user-images.githubusercontent.com/8233381/211074833-56b741b3-6189-47e4-9fa8-c07361baf0ef.png)

Grafana/Prometheus
![image](https://user-images.githubusercontent.com/8233381/211074951-05ad64e0-1e87-40fc-b311-42118a6b6ccc.png)

v21.2 DB Console
![image](https://user-images.githubusercontent.com/8233381/211075268-34c7b263-247a-4663-ad37-1b6ed60dad41.png)

Jira issue: CRDB-23183

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

storage_capacity metric and related DBConsole graphs should not start from 0

Description

Contributor guide

Assessment

Get new issues in your inbox