Self-hosted teams struggle to inspect and export monitoring history
Operators of self-hosted monitoring tools need to browse, query, and analyze historical metrics and uptime data, but the ways to do so can be awkward or incomplete. One user spent a week trying to configure Thanos before considering VictoriaMetrics, while other requests ask for a maintained collectd web UI, monitor-data exports, and more detailed outage timelines. The shared need is easier access to monitoring history, though the data sources and integrations vary.
For self-hosted monitoring administrators. Mentioned from May 2019 to Oct 2025 on GitHub and Stack Exchange.
4 different people described this problem in 4 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 5.5/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
If this can be done without the complexity of Thanos that would be amazing. I spent a full week trying to get the Thanos and sidecar pieces set up but had too many issues. That drove me to Victoria Metrics as a probable solution
On my servers I have collectd running, now I would like to access this data on a UI, best using a web application which allows to browse the current and historic data using a html based UI
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks