Edge sinking structure adjustment #3098

Closed
opened 2026-02-28 03:17:54 -05:00 by deekerman · 2 comments
Owner

Originally created by @jidixuelangas on GitHub (Feb 5, 2024).

⚠️ Please verify that this question has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

Hello, our network has several regions, some of which cannot be directly connected to the Internet. I want to ask whether there are plans, plans, and architecture designs that consider the edge sinking structure

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

1.23.11

💻 Operating System and Arch

Rocky Linux 9

🌐 Browser

Google 120

🖥️ Deployment Environment

  • Runtime:
  • Database:
  • Filesystem used to store the database on:
  • number of monitors:
Originally created by @jidixuelangas on GitHub (Feb 5, 2024). ### ⚠️ Please verify that this question has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem Hello, our network has several regions, some of which cannot be directly connected to the Internet. I want to ask whether there are plans, plans, and architecture designs that consider the edge sinking structure ### 📝 Error Message(s) or Log _No response_ ### 🐻 Uptime-Kuma Version 1.23.11 ### 💻 Operating System and Arch Rocky Linux 9 ### 🌐 Browser Google 120 ### 🖥️ Deployment Environment - Runtime: - Database: - Filesystem used to store the database on: - number of monitors:
deekerman 2026-02-28 03:17:54 -05:00
Author
Owner

@CommanderStorm commented on GitHub (Feb 5, 2024):

It is unclear what you mean by "edge sinking structure".
Googling it does not lead to content which I think you are referring to1

deployments

If you want to deploy one uptime kuma instance to each region, that obviously works.
You can also use one central instance and report back using the push-monitors depending on your concrete network restrictions.

If via edge you are referring to serverless tech, this is neither planned nor possible given the current architecture without significat reworking

notifications

I don't know what your network restrictions are concretely but to send notifications internet of some kind is normally required.
Currently, routing notification providers via a proxy is not something we support, but PRs in this area are appreciated. See our contribution guide.

You may already allow outgoing smtp ⇒ maybe smtp smuggling of some sort via the local mail subsystem is an option?

Maybe related


  1. If you are refering to this, no we have not considered fishing ^^
    image ↩︎

@CommanderStorm commented on GitHub (Feb 5, 2024): It is unclear what you mean by "edge sinking structure". Googling it does not lead to content which I think you are referring to[^1] #### deployments If you want to deploy one uptime kuma instance to each region, that obviously works. You can also use one central instance and report back using the push-monitors depending on your concrete network restrictions. If via edge you are referring to serverless tech, this is neither planned nor possible given the current architecture without significat reworking #### notifications I don't know what your network restrictions are concretely but to send notifications internet of some kind is normally required. Currently, routing notification providers via a proxy is not something we support, but PRs in this area are appreciated. See our [contribution guide](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md). You may already allow outgoing smtp ⇒ maybe smtp smuggling of some sort via the [local mail subsystem](https://github.com/louislam/uptime-kuma/issues/2793) is an option? Maybe related - #84 - #118 - #616 - #2588 [^1]: If you are refering to this, no we have not considered fishing ^^ ![image](https://github.com/louislam/uptime-kuma/assets/26258709/c2b84d6e-d982-4270-84b5-c0da4a70f874)
Author
Owner

@CommanderStorm commented on GitHub (Feb 17, 2024):

I have no clue what @jidixuelangas is asking in this issue and they are not responding to my question..
=> closing as not planned

@CommanderStorm commented on GitHub (Feb 17, 2024): I have no clue what @jidixuelangas is asking in this issue and they are not responding to my question.. => closing as not planned
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#3098
No description provided.