You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
This would help me bulk-edit monitors or use git to manage uptime-kuma configuration.
Describe the solution you'd like
A json/yaml file with a minimal description of monitors which can be inserted into the database during the startup of uptime-kuma.
The minimal description would be similar to what is required on the UI :
type,
name,
url,
timeout,
retries,
tags,
notifications (there is a catch there if the notification does not exist)
In case monitors are present in database and a file is found at startup, the name field would be used to detect duplicates and not import them again.
Describe alternatives you've considered
Altering the backup file to reimport it again, but a lot of fields are overwhelming to just add a bunch of monitors.
Additional context
The next step would be to configure the instance of uptime-kuma (auth, theme, global notfications, ...) using a file, but it does not feel that important
The text was updated successfully, but these errors were encountered:
Is it a duplicate question?
No
Is your feature request related to a problem? Please describe.
This would help me bulk-edit monitors or use git to manage uptime-kuma configuration.
Describe the solution you'd like
A json/yaml file with a minimal description of monitors which can be inserted into the database during the startup of uptime-kuma.
The minimal description would be similar to what is required on the UI :
In case monitors are present in database and a file is found at startup, the name field would be used to detect duplicates and not import them again.
Describe alternatives you've considered
Altering the backup file to reimport it again, but a lot of fields are overwhelming to just add a bunch of monitors.
Additional context
The next step would be to configure the instance of uptime-kuma (auth, theme, global notfications, ...) using a file, but it does not feel that important
The text was updated successfully, but these errors were encountered: