mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Add servers via API #821
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#821
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 @manustu on GitHub (Feb 8, 2022).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
API
🔖 Feature description
It would be cool if there was an ability to add a new monitor via a REST API request
✔️ Solution
http://IP_ADDRESS:PORT?ip=192.168.0.1&type=ping&name=example_name&etc...etc
❓ Alternatives
Alternatively, allow to be able to define an external database in config
📝 Additional Context
No response
@Sneeex commented on GitHub (Feb 8, 2022):
I jus wanted to ask if its already possible but seems not.
@OmgImAlexis commented on GitHub (Feb 22, 2022):
Duplicate of https://github.com/louislam/uptime-kuma/issues/118?
@CommanderStorm commented on GitHub (Jul 4, 2023):
@manustu could you please recheck if this a duplacte of #118 ?
If yes, please close this issue, as duplicates only create immortal zombies (and are harder to issue-manage)
If no, what makes this issue distinct?
@kdambekalns commented on GitHub (Dec 12, 2023):
IMHO this is indeed a duplicate of #118
@CommanderStorm commented on GitHub (Feb 8, 2024):
@manustu
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in #118 as this issue is included there
⇒ I am going to close this as a duplicate.