The builder's path
For: Prometheus operators can't keep important metrics longer than unimportant ones.
“Some things are under our control, while others are not under our control.”
Routes to a solution
Each route is a different kind of journey, with real people and organisations to contact at each step, starting with those in every country.
Step 1
Build in the open
Publish the code and invite contributors from the community.
Let the people a free tool helps fund its maintainer directly.
Raise and spend money in the open for a community project.
Grants for open source that makes the internet better.
Network of civic tech groups in many countries; find the one near the problem.
Step 2
Fund the maintainers
Sponsors, collectives and open source grants.
Let the people a free tool helps fund its maintainer directly.
Raise and spend money in the open for a community project.
Grants for open source that makes the internet better.
Network of civic tech groups in many countries; find the one near the problem.
Step 3
Get it adopted
Civic tech groups and public bodies take it up.
Y Combinator's free course and co-founder matching.
Raise and spend money in the open for a community project.
Network of civic tech groups in many countries; find the one near the problem.
Volunteer data scientists working with social-sector organisations.
Ideas, sources and tools for this problem, from first interviews to funding.
how blocks, compaction and retention work today
need to agree the scope before a large change
Starter prompt
Built from this problem's brief. Paste it into Claude or any AI assistant.
Help me design and build a first working prototype for this problem in Anywhere. Problem: Prometheus operators can't keep important metrics longer than unimportant ones. Who it hurts: People who run Prometheus monitoring and manage its disk use. The moment it hurts: When storage fills up and the only choice is to shorten retention for everything. What people do today: One retention time applies to all metrics. Why it is still unsolved: It touches how the time-series database compacts its blocks, and the scope is still being discussed. What solved looks like: A prototype in Prometheus's storage compaction that drops series matching a configured selector once they pass their own retention, with a benchmark of disk saved on a sample dataset and written answers to the scope questions raised in the issue. Where: Anywhere First, list what you would need to learn from the people affected before building, as interview questions. Then propose the simplest version that would help, the screens or messages it needs, and the data it would use. Keep it cheap to run, accessible, and respectful of people's privacy. Flag anything you are unsure about instead of guessing.
Talk to the people who live it before you build.
“Truth is one; the wise speak of it in many ways.”
एकं सद्विप्रा बहुधा वदन्ति
ekaṃ sad viprā bahudhā vadanti
Get a working version in front of people fast.
Using AI is not cheating. Every tool carries the work of the people who made it, and using it well is how knowledge has always moved forward. The thinking, the care for the people who live the problem, and the judgement are still yours.
“The Analytical Engine weaves algebraical patterns just as the Jacquard-loom weaves flowers and leaves.”
Open data that fits this problem.
“Lead me from the unreal to the real, from darkness to light.”
असतो मा सद्गमय। तमसो मा ज्योतिर्गमय।
asato mā sad gamaya, tamaso mā jyotir gamaya
Tools matched to what this problem needs.
“If I have seen further it is by standing on the shoulders of Giants.”
Ship it responsibly, and find help and funding.
“As to diseases, make a habit of two things: to help, or at least to do no harm.”
ἀσκέειν περὶ τὰ νουσήματα δύο, ὠφελέειν ἢ μὴ βλάπτειν
Kit written for this problem from its brief; every link was checked. Links go to each provider's own site. Zetema is not paid for any listing.