komari-monitor/komari

A simple server monitor tool.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 22 minutes ago
Added to GitGenius on September 10th, 2026
Created on April 19th, 2025
Open Issues & Pull Requests: 9 (+0)
GitHub issues: Enabled
Number of forks: 591
Total Stargazers: 6,168 (+0)
Total Subscribers: 9 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 7
New in 7 days: 5
Closed in 7 days: 1
Avg open age: 7 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 5
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 3

Top labels

  • enhancement (198)
  • bug (164)
  • from end user (8)
  • need more information (8)
  • pull request welcome (6)
  • wontfix (4)
  • ask contributor (3)
  • invalid (3)

Detailed Description

Komari is a lightweight, self-hosted server monitoring tool that collects performance metrics through an agent and displays them via a web interface.

The tool addresses the need for simple server performance tracking without relying on external monitoring services. It works by deploying a lightweight agent on servers to gather metrics, which are then visualized in real-time through a web dashboard updated at one-second intervals. The self-hosted architecture means monitoring data remains under your control rather than being sent to third-party services.

Komari suits operators who want minimal resource overhead on their servers and prefer to manage monitoring infrastructure themselves. It works well across servers of any size and provides an intuitive dashboard for tracking performance. The tool supports custom themes and plugins, allowing some degree of customization for different monitoring needs. Anyone deploying Komari should be aware that it includes remote control capabilities alongside monitoring, so it should only be deployed on systems you own or are authorized to manage.

The project shows active development with regular updates and maintains documentation and community channels including a Telegram group. Development appears focused on keeping the codebase maintainable and the tool lightweight, with attention to both core functionality and extensibility through plugins and themes.