mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Allow bulk upload monitors using a CSV file or JSON file. #2818
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#2818
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 @qburst-rupesh on GitHub (Nov 20, 2023).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
New Monitor
🔖 Feature description
Here, we would like to propose the addition of a new functionality, such as the ability to upload a CSV or JSON file for mass or bulk creation on additional monitors.
For example, I would like to upload 2 monitors one for https://hackernoon.com/ and second for https://www.diffchecker.com/
so there should be facility for uploading file from VueJS frontend with file validation (File type may be CSV or JSON whichever easy and compatible with our system) and after successfully submit the file new monitor should be create one for hackernoon and second for diffchecker and rest of the operation should be act as as it is like.
@louislam and all other contributers
✔️ Solution
The bulk upload monitor option is available on the right side when you click Add Monitor. The user uploads the file from there, and it is sent to the backend node.js over a socket.
It is necessary for us to read and save the file, then create the monitors using the given keys or parameters. and then unlink or delete file after our operation will be completed for avoiding junks.
❓ Alternatives
NA
📝 Additional Context
NA
@CommanderStorm commented on GitHub (Nov 20, 2023):
I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/1190 https://github.com/louislam/uptime-kuma/issues/2297
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^
@qburst-rupesh commented on GitHub (Nov 21, 2023):
@CommanderStorm No front-end code or socket code with file type inspection and file unlinking to prevent trash can be found. There are various types of monitors, such as TCP, MQTT, and https, thus it's possible that some information about which parameter to send when choosing a monitor type is lacking. Thus, it appears that the precise top-to-bottom flow is unable to identify and fully satisfy the criteria that are thought of as generic requirements.
@CommanderStorm commented on GitHub (Nov 21, 2023):
something was lost in translation (what you wrote does not make sense to me) ^^
That is to be expected, as noted above, I think this issue is a duplicate of other issues and merging them would be benefitial
It is unclear why this requires another issue.
A solution should be general enough to not require hardcoded columns or https://github.com/louislam/uptime-kuma/pull/3967#issuecomment-1786493484
It is unclear what you mean by this statement. What makes this issue unique enough to require an additional issue?
@CommanderStorm commented on GitHub (Nov 21, 2023):
note that our contibution guide is here:
github.com/louislam/uptime-kuma@1550a5f792/CONTRIBUTING.md@CommanderStorm commented on GitHub (Dec 13, 2023):
Duplicate of https://github.com/louislam/uptime-kuma/issues/1190
@Vaskata84 commented on GitHub (Aug 30, 2024):
Hi I'm using the new version of kuma 1.23.13 and I can't import a big json file with many 1500 hosts I made it look one to one with a downloaded file and I added the new hosts. I do this with this script because there are many hosts.
@CommanderStorm commented on GitHub (Aug 30, 2024):
@Vaskata84 this issue is not implemented. No import functionality currently exists. Please see #1190