cockroachdb / cockroachdb/cockroach

Log backup & restore duration in telemetry

Open
#98,131 1 comment 0 reactions 0 assignees View on GitHub
A-disaster-recovery C-enhancement T-disaster-recovery
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

**Is your feature request related to a problem? Please describe.**
We don't have an understanding of how long backup & restore take to run on customer environments.

**Describe the solution you'd like**
I would like to see a new "duration" field captured in log-based telemetry, at the end of a backup & restore operation.

**Describe alternatives you've considered**
None

**Additional context**
N/A

Jira issue: CRDB-25094

Contributor guide

Open the contributing guide

Research direction

Start by locating the backup and restore operation entry points and the log-based telemetry emitted when each completes. Add a duration field to the telemetry at the end of both operations, and verify that backup and restore logs report how long they took.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
databases, observability
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.