Edge sinking structure adjustment

[jidixuelangas]

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

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project 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:

[CommanderStorm]

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

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

• Remote Executors #84
• API functionality #118
• Notifications via proxy #616
• Notifications via a proxy (squid) #2588

Footnotes

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

[CommanderStorm]

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