[PR #708] [MERGED] Add CheckCle to Monitoring & Status Pages #1947

Closed
opened 2026-04-15 12:44:33 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/awesome-foss/awesome-sysadmin/pull/708
Author: @kokomo123
Created: 3/17/2026
Status: Merged
Merged: 3/19/2026
Merged by: @nodiscc

Base: masterHead: add-checkcle


📝 Commits (1)

  • 93d6ca7 Add CheckCle to Monitoring & Status Pages

📊 Changes

1 file changed (+2 additions, -1 deletions)

View changed files

📝 README.md (+2 -1)

📄 Description

Migrating uptime pages from awesome-selfhosted, per discussion.

Thank you for taking the time to work on a PR for Awesome-Sysadmin!

To ensure your PR is dealt with swiftly please check the following:

  • Your additions are Free software
  • Software you are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts).
  • Submit one item per pull request. This eases reviewing and speeds up inclusion.
  • Format your submission as follows, where Demo and Clients are optional.
    Do not add a duplicate Source code link if it is the same as the main link.
    Keep the short description under 80 characters and use sentence case
    for it, even if the project's webpage or readme uses another capitalisation.
    Demo links should only be used for interactive demos, i.e. not video demonstrations.
    - [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language`
  • Additions are inserted preserving alphabetical order.
  • Additions are not already listed at awesome-selfhosted
  • The Language tag is the main server-side requirement for the software. Don't include frameworks or specific dialects.
  • You have searched the repository for any relevant issues or PRs, including closed ones.
  • Any category you are creating has the minimum requirement of 3 items.
  • Any software project you are adding to the list is actively maintained.
  • The pull request title is informative, unlike "Update README.md".
    Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb,
    "Remove aaa from bbb" for removing, "Fix license for aaa", etc.

Please take some time to answer the following questions as best you can:

  • Why is it awesome?

It's a intuitive monitoring software, sorta like Uptime Kuma but much more enterprise driven, and monitoring for servers using agents.

  • Have you used it? For how long?
    I have personally spun up a instance in my own homelab, it's been running fine for just a few days but it's pretty snappy and works well, with me exploring, I can customize templates for specific monitoring needs.

  • Is this in a personal or professional setup?

Personal setup, but I can definitely see me using this in a professional environment.

  • How many devices/users/services/... do you manage with it?

Just a few services as I already have uptime kuma, but it's nice for redundancy in case my uptime kuma instance goes down. I haven't explored it further

  • Biggest pros/cons compared to other solutions?
    Pros-
    Can distribute monitoring agents to a variety of servers to check in on them, and your services.
    Very intuitive, straight forward places to setup things without having to type in a ton of stuff, that's what templates are for.
    Customizable monitoring templates
    Very enterprise use, but can help monitor a homelab just fine.

Cons-
Cannot hook into many monitoring services like uptime kuma has already had, and im sure many others.

  • Any other comments about your use case, things you've found excellent, limitations you've encountered... ?
    None so far, but I will explore it more at some point just to get it going and functioning, as it's very new to me so I need to get used to it.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/awesome-foss/awesome-sysadmin/pull/708 **Author:** [@kokomo123](https://github.com/kokomo123) **Created:** 3/17/2026 **Status:** ✅ Merged **Merged:** 3/19/2026 **Merged by:** [@nodiscc](https://github.com/nodiscc) **Base:** `master` ← **Head:** `add-checkcle` --- ### 📝 Commits (1) - [`93d6ca7`](https://github.com/awesome-foss/awesome-sysadmin/commit/93d6ca7e4b9b3362077cf605fad00c471fa93920) Add CheckCle to Monitoring & Status Pages ### 📊 Changes **1 file changed** (+2 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+2 -1) </details> ### 📄 Description Migrating uptime pages from awesome-selfhosted, per discussion. <!-- IF YOUR PULL REQUEST ADDS NEW SOFTWARE TO THE LIST, DO NOT DELETE THE TEXT BELOW. --> <!-- Please make sure relevant boxes are checked [x] --> Thank you for taking the time to work on a PR for Awesome-Sysadmin! To ensure your PR is dealt with swiftly please check the following: - [X] Your additions are [Free software](https://en.wikipedia.org/wiki/Free_software) - [X] Software you are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts). - [X] Submit one item per pull request. This eases reviewing and speeds up inclusion. - [X] Format your submission as follows, where `Demo` and `Clients` are optional. Do not add a duplicate `Source code` link if it is the same as the main link. Keep the short description under 80 characters and use [sentence case](https://en.wikipedia.org/wiki/Letter_case#Sentence_case) for it, even if the project's webpage or readme uses another capitalisation. `Demo` links should only be used for interactive demos, i.e. not video demonstrations. ``- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language` `` - [X] Additions are inserted preserving alphabetical order. - [X] Additions are not already listed at [awesome-selfhosted](https://awesome-selfhosted.net) - [X] The `Language` tag is the main **server-side** requirement for the software. Don't include frameworks or specific dialects. - [X] You have searched the repository for any relevant [issues](https://github.com/awesome-foss/awesome-sysadmin/issues) or [PRs](https://github.com/awesome-foss/awesome-sysadmin/pulls), including closed ones. - [ ] Any category you are creating has the minimum requirement of 3 items. - [X] Any software project you are adding to the list is actively maintained. - [X] The pull request title is informative, unlike "Update README.md". Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb, "Remove aaa from bbb" for removing, "Fix license for aaa", etc. -------------- Please take some time to answer the following questions as best you can: <!-- Failure to answer these questions in a useful and unbiased way will result in your submission being rejected. --> - **Why is it awesome?** It's a intuitive monitoring software, sorta like Uptime Kuma but much more enterprise driven, and monitoring for servers using agents. - **Have you used it? For how long?** I have personally spun up a instance in my own homelab, it's been running fine for just a few days but it's pretty snappy and works well, with me exploring, I can customize templates for specific monitoring needs. - **Is this in a personal or professional setup?** Personal setup, but I can definitely see me using this in a professional environment. - **How many devices/users/services/... do you manage with it?** Just a few services as I already have uptime kuma, but it's nice for redundancy in case my uptime kuma instance goes down. I haven't explored it further - **Biggest pros/cons compared to other solutions?** Pros- Can distribute monitoring agents to a variety of servers to check in on them, and your services. Very intuitive, straight forward places to setup things without having to type in a ton of stuff, that's what templates are for. Customizable monitoring templates Very enterprise use, but can help monitor a homelab just fine. Cons- Cannot hook into many monitoring services like uptime kuma has already had, and im sure many others. - **Any other comments about your use case, things you've found excellent, limitations you've encountered... ?** None so far, but I will explore it more at some point just to get it going and functioning, as it's very new to me so I need to get used to it. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-15 12:44:33 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-sysadmin#1947