Skip to content

docs: clarify cleaning PROMETHEUS_MULTIPROC_DIR#1167

Open
ayushanand293 wants to merge 1 commit intoprometheus:masterfrom
ayushanand293:docs/931-multiproc-cleanup
Open

docs: clarify cleaning PROMETHEUS_MULTIPROC_DIR#1167
ayushanand293 wants to merge 1 commit intoprometheus:masterfrom
ayushanand293:docs/931-multiproc-cleanup

Conversation

@ayushanand293
Copy link
Copy Markdown

Summary

Document a recommended startup cleanup pattern for PROMETHEUS_MULTIPROC_DIR to avoid stale metrics across restarts.

Closes #931.

Checklist

  • I ran the test suite locally (python -m pytest -q).
  • Documentation updated.

Signed-off-by: Ayush Anand <ayushanand293@gmail.com>
@ayushanand293 ayushanand293 force-pushed the docs/931-multiproc-cleanup branch from dbaf533 to af766ef Compare April 23, 2026 11:07
Comment on lines +42 to +43
rm -rf "$PROMETHEUS_MULTIPROC_DIR"
mkdir -p "$PROMETHEUS_MULTIPROC_DIR"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
rm -rf "$PROMETHEUS_MULTIPROC_DIR"
mkdir -p "$PROMETHEUS_MULTIPROC_DIR"
rm "$PROMETHEUS_MULTIPROC_DIR/*.db"

This might be a bit safer, and one less thing to do. I also wonder if the example should be in python rather than asking people to run bash before starting python?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

How to clean PROMETHEUS_ MULTIPROC_

2 participants