Allow bulk upload monitors using a CSV file or JSON file.

[qburst-rupesh]

⚠️ Please verify that this feature request has NOT been suggested before.

• I checked and didn't find similar feature request

🏷️ 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]

I think this is a duplicate of #1190 #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]

@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]

something was lost in translation (what you wrote does not make sense to me) ^^

No front-end code or socket code [...] can be found

That is to be expected, as noted above, I think this issue is a duplicate of other issues and merging them would be benefitial

There are various types of monitors [...] thus it's possible that some information about which [monitor] parameter[s] [..] is lacking

It is unclear why this requires another issue.
A solution should be general enough to not require hardcoded columns or #3967 (comment)

the precise top-to-bottom flow is unable to identify and fully satisfy the criteria that are thought of as generic requirements

It is unclear what you mean by this statement. What makes this issue unique enough to require an additional issue?

[CommanderStorm]

note that our contibution guide is here: https://github.com/louislam/uptime-kuma/blob/1550a5f79270f39007086d8d23c180ba9f63096b/CONTRIBUTING.md

[CommanderStorm]

Duplicate of #1190

[CommanderStorm]

@Vaskata84 this issue is not implemented. No import functionality currently exists. Please see #1190