mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Edge sinking structure adjustment #3098
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#3098
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jidixuelangas on GitHub (Feb 5, 2024).
⚠️ Please verify that this question has NOT been raised before.
🛡️ 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
@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
If you are refering to this, no we have not considered fishing ^^
↩︎
@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