issue-statusvsnetdata
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| issue-status | netdata | |
|---|---|---|
| Score | 47/100 | 87/100 |
| Rank in category | #31 of 51 in Monitoring & observability | #4 of 104 in Monitoring & observability |
| GitHub stars | 429 | 81 200 |
| Stars, last 30 days | — | +566 |
| Stable releases, 12 months | 0 | 16 |
| Latest release | — | v2.12.2 · 23 Oct 2026 |
| Setup | Easy | Easy |
| Official Docker image | No | Yes |
| License | MIT | GPL-3.0 |
| Main language | Typescript | Go |
Which one should you pick?
netdata scores 87/100 against 47/100 for issue-status, so it is the safer default.
netdata ships more often: 16 stable releases in the past year, against 0 for issue-status.
netdata is growing faster right now (+566 stars in 30 days).
issue-status details →netdata details →
Swap a project
Keep issue-status, compare it with
Keep netdata, compare it with