Stamon
Lightweight self-managed status monitoring tool-a high-performance server monitoring solution built with Rust. Supports real-time monitoring of service status and resource usage, and provides a simple and intuitive Web interface. Very low resource usage and suitable for server environments of all sizes.
Stamon is a lightweight, high-performance self-managed status monitoring tool. This document details how to use Stamon to monitor your services, create public status pages, and configure alarm notifications. ## 1. Overview of core functions Stamon mainly includes the following core modules: - **Dashboard **: Real-time overview of the running status of all services. - **Services **: Add and manage specific monitoring items (such as HTTP, TCP, DNS, etc.). - **Status Pages **: Create a public system status page and present it to your users. - **Notification Providers **: Configure alarm sending methods (such as Telegram, Slack, etc.). - **Team **: Manage users and team members. ## 2. Add Monitoring Services This is Stamon's core function. Click **Services** -> **New Service** in the sidebar to enter the add page. ### 2.1 Detailed explanation of monitoring types Stamon supports multiple monitoring types and is suitable for different scenarios: | type| described| applicable scenarios| | :--- | :--- | :--- | | **HTTP(s)** |Monitor web pages or API interfaces| Home page, backend API, REST/GraphQL services| | **TCP Port** |Monitor TCP port connectivity| Database (MySQL/Redis), SSH, mail services| | **ICMP Ping** |Monitor host survival status| Servers, network devices, routers| | **DNS** |Monitor domain name resolution records| Check whether the domain name is resolved correctly to prevent hijacking| ### 2.2 Detailed configuration case ####Case 1: Monitoring a Web site (HTTP) Suppose you want to monitor `example.com`, and the request response status code must start with `2`(such as 200). - **Name **: `Example Website` - **Url**: `https://example.com` - **Type**: Select `HTTP` - **Interval **: `60` (recommended every 60 seconds) - **Timeout **: `20` (20 seconds of no response is considered a timeout) - **Expected Code **: `2` - * Tip: Enter `2` to match all status codes 200-299. Enter `200` to strictly match 200. * - **Expected Payload **: *(Optional)* - If you want to check whether the page contains specific text (such as "Welcome"), you can enter it here.
