Skip to content

docs: automate release metrics generation#1151

Open
AR21SM wants to merge 1 commit into
etcd-io:mainfrom
AR21SM:docs/update-metrics-from-etcd
Open

docs: automate release metrics generation#1151
AR21SM wants to merge 1 commit into
etcd-io:mainfrom
AR21SM:docs/update-metrics-from-etcd

Conversation

@AR21SM
Copy link
Copy Markdown
Contributor

@AR21SM AR21SM commented Apr 29, 2026

What changed

This PR adds a script to update the generated metrics file from the etcd source.

It uses the existing tools/etcd-dump-metrics tool from etcd repo.

I also added make targets for updating and verifying the metrics docs, and updated the release version script so future release updates can also refresh the metrics file.

This PR regenerates the v3.6 metrics file from v3.6.0.

closes #1133

Note

I did not update v3.7 metrics in this PR because v3.7 is still draft and uses git_version_tag: main. I kept the script limited to released etcd tags to avoid committing metrics generated from a moving branch.

If maintainers want draft docs to track metrics from main, I can add that separately.
image

Signed-off-by: AR21SM <mahajanashishar21sm@gmail.com>
@k8s-ci-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: AR21SM
Once this PR has been reviewed and has the lgtm label, please assign ivanvc for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot
Copy link
Copy Markdown

Hi @AR21SM. Thanks for your PR.

I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@jberkus
Copy link
Copy Markdown
Contributor

jberkus commented May 7, 2026

/ok-to-test

Comment on lines +411 to +425
etcd_disk_wal_write_duration_seconds_bucket{le="0.001"}
etcd_disk_wal_write_duration_seconds_bucket{le="0.002"}
etcd_disk_wal_write_duration_seconds_bucket{le="0.004"}
etcd_disk_wal_write_duration_seconds_bucket{le="0.008"}
etcd_disk_wal_write_duration_seconds_bucket{le="0.016"}
etcd_disk_wal_write_duration_seconds_bucket{le="0.032"}
etcd_disk_wal_write_duration_seconds_bucket{le="0.064"}
etcd_disk_wal_write_duration_seconds_bucket{le="0.128"}
etcd_disk_wal_write_duration_seconds_bucket{le="0.256"}
etcd_disk_wal_write_duration_seconds_bucket{le="0.512"}
etcd_disk_wal_write_duration_seconds_bucket{le="1.024"}
etcd_disk_wal_write_duration_seconds_bucket{le="2.048"}
etcd_disk_wal_write_duration_seconds_bucket{le="4.096"}
etcd_disk_wal_write_duration_seconds_bucket{le="8.192"}
etcd_disk_wal_write_duration_seconds_bucket{le="+Inf"}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it actually help users to output all of these bucket thresholds in this format?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Ameliorate the generated list of metrics page to be updated

3 participants