← Directory

beszel

A lightweight server monitoring hub with historical data, docker stats, and alerts.

  • Monitoring & Logging
  • Network Services
  • Other
  • Tools & Utilities
A lightweight server monitoring hub with historical data, docker stats, and alerts.

Platform availability

Available on 4 of 6 install platforms

Also on Docker Hub and GitHub

Health score

34/100 Low

Maintained
0GitHub repository no longer exists
Popular
No data
Easy to install
553 install platforms, install notes, Docker image
Light to run
95512 MB minimum RAM, runs on ARM

Based on 3 of 4 factors.

How is this calculated?

A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). Factors without data are left out and the rest are rescaled.

Availability: platform listings confirmed today, links checked 10 days ago

No GitHub repository data collected yet.

Checked 10 days ago - source: GitHub (BigBearTechWorld/beszel)

Resources & Compatibility

Minimum requirements: 512 MB RAM, 1 CPU core(s), 5 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 10 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install the Hub first and open port 8090 Run the Hub installer so it sets up and starts the Beszel dashboard service; the dashboard is the central place that stores data and shows graphs. It normally listens on port 8090 (the number your browser connects to), so if you can't reach that port, the site won't load. source
  • Install the agent on every machine you monitor Install and start the Beszel agent on each machine you want to monitor; the agent is the little program that collects stats like CPU, memory, and disks. Without it, the Hub has no data from that machine and it won't show up in the dashboard. source
  • Give the agent its Hub URL, key, and token Before starting the agent, enter the Hub URL, the machine's public key (a code that says this agent is allowed to join), and its token (a secret access code). These let the agent connect securely; if they're wrong or missing, the machine can't register and will appear offline or unknown. source

Fetched 10 days ago - each note links to its source

Alternatives (12)

  • Better Stack - AI-driven monitoring platform providing incident management, real-time logs, uptime, traces, error tracking, infrastructure analytics, and…
  • Datadog - Main repository for Datadog Agent
  • Grafana - Grafana allows you to query, visualize, alert on and understand your metrics no matter where they are stored.
  • HetrixTools
  • Icinga - Icinga is a fork of Nagios and is backward compatible.
  • LibreNMS - LibreNMS is a fully featured network monitoring system that discovers and monitors network devices, interfaces, and services.
  • Munin - Munin is a networked resource monitoring tool that can help analyze resource trends and "what just happened to kill our performance?&q…
  • NIXStats
  • Nagios - Nagios is a powerful monitoring system licensed under Nagios Enterprises that helps organizations identify and resolve IT infrastructure is…
  • Netdata - Netdata collects metrics per second and presents them in beautiful low-latency dashboards.
  • Tianji - Tianji is a self-hosted website analytics and uptime monitoring platform that combines visitor traffic insights, service availability check…
  • Zabbix - Zabbix is an enterprise-class, open-source distributed monitoring solution designed to monitor the performance and availability of network…

Checked 7 days ago - source: AlternativeTo

Common questions

Which port does the Beszel dashboard need to be reachable on?

The Hub dashboard normally listens on port 8090, so that port must be open for the browser to load the dashboard. If the port is not reachable, the site will not load.

What does an agent need before it can connect to the Beszel Hub?

Install the agent on each machine you monitor and set its Hub URL, public key, and token before starting it. If those values are wrong or missing, the machine cannot register and will show as offline or unknown.

Why might agents fail after an update when using self-signed HTTPS certificates?

Beszel 0.19.0 made agents verify HTTPS certificates as a breaking change. Self-signed certificates may require setting CA_CERT_FILE so the agent can trust them.

Does Beszel require a separate database to be provisioned?

No, Beszel does not require a separate database to provision. It provides history and threshold alerts without a separate database setup.

Answers sourced from beszel.dev, beszel.dev, forum.cloudron.io, selfhostatlas.com

Community

Collected 5 days ago - public community threads