Roadmap
What is shipped, in progress and planned is tracked on the public project board: DumbMonit Roadmap. Priorities and timing can change; the board is a living plan, not a promise.
- Shipped changes are in the changelog and in the notes of each GitHub release.
- Ideas and bugs live in the issue tracker. Open an issue before writing code for something large.
- Security fixes are announced in the release notes and as GitHub security advisories, with their CVE or GHSA identifier.
DumbMonit is before 1.0: expect the API and the data model to keep evolving until a stable line is announced. See the contributing guide and the governance to take part.
Direction for the next twelve months
Section titled “Direction for the next twelve months”These are intentions, not commitments, in rough order.
- Towards 1.0. Settle the HTTP API and the database schema so that a stable line can be announced; until then minor versions may still change them, with upgrade notes in the changelog.
- More people with access. A second administrator of the repository, registry, documentation hosting and domains (see the governance).
- Supply chain. Reproducible release builds (current state) and signed version tags.
- arm64 images. Server images are amd64 only for now; arm64 returns with native build runners.
- Integrations and packs. More device and service integrations and SNMP profiles, driven by contributions and requests.
- Documentation. Keep the nine languages of the interface and the documentation in step with the English source.
What DumbMonit does not intend to do
Section titled “What DumbMonit does not intend to do”- Become a log, trace or APM platform: it monitors devices and services.
- Offer a paid edition or a hosted service: it stays 100 % open source.
- Send telemetry about your instance anywhere.
- Target fleets of thousands of devices: it is built for homelabs and small teams, on one container.