Registering a monitor target #2101

New issue

Open

opened 2026-02-28 02:43:00 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 02:43:00 -05:00

Owner

Originally created by @confiar on GitHub (Apr 13, 2023).

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

I checked and didn't find similar feature request

🏷️ Feature Request Type

API

🔖 Feature description

It would be very convenient if monitor registration is possible through API.

✔️ Solution

It would be nice if the API had required and optional parameters, and a method that could register the monitor target through http request was applied.

❓ Alternatives

I would like to be able to upload a csv file or register multiple monitor targets in a csv format on the web in bulk.

📝 Additional Context

No response

Originally created by @confiar on GitHub (Apr 13, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type API ### 🔖 Feature description It would be very convenient if monitor registration is possible through API. ### ✔️ Solution It would be nice if the API had required and optional parameters, and a method that could register the monitor target through http request was applied. ### ❓ Alternatives I would like to be able to upload a csv file or register multiple monitor targets in a csv format on the web in bulk. ### 📝 Additional Context _No response_

deekerman added the

feature-request

A:api

labels

2026-02-28 02:43:00 -05:00

deekerman commented

2026-02-28 02:43:04 -05:00

Author

Owner

@jonnymccullagh commented on GitHub (Apr 14, 2023):

I achieve this via Ansible with:
https://github.com/lucasheld/ansible-uptime-kuma
Ultimately I am defining each monitor in yaml e.g.

uptime_kuma_http_monitors:
  - name: "website1.com"
    url: "https://website1.com"
    tag: "prod"
    state: "present"
  - name: "website2.co.uk"
    url: "https://website2.co.uk"
    tag: "prod"
    state: "present"
  - name: "website3.co.uk"
    url: "https://website3.co.uk"
    tag: "dev"
    state: "present"

@jonnymccullagh commented on GitHub (Apr 14, 2023): I achieve this via Ansible with: https://github.com/lucasheld/ansible-uptime-kuma Ultimately I am defining each monitor in yaml e.g. ``` uptime_kuma_http_monitors: - name: "website1.com" url: "https://website1.com" tag: "prod" state: "present" - name: "website2.co.uk" url: "https://website2.co.uk" tag: "prod" state: "present" - name: "website3.co.uk" url: "https://website3.co.uk" tag: "dev" state: "present" ```

deekerman commented

2026-02-28 02:43:05 -05:00

Author

Owner

@confiar commented on GitHub (May 3, 2023):

thank you for the answer first

but it's not working.
please help me.

An error occurs when I enter the command below.

ansible-galaxy collection install git+https://github.com/lucasheld/ansible-uptime-kuma.git

ERROR! Invalid collection name 'git+https', name must be in the format .. Please make sure namespace and collection name contains characters from [a-zA-Z0-9_] only.

@confiar commented on GitHub (May 3, 2023): thank you for the answer first but it's not working. please help me. An error occurs when I enter the command below. ansible-galaxy collection install git+https://github.com/lucasheld/ansible-uptime-kuma.git ERROR! Invalid collection name 'git+https', name must be in the format <namespace>.<collection>. Please make sure namespace and collection name contains characters from [a-zA-Z0-9_] only.

deekerman commented

2026-02-28 02:43:05 -05:00

Author

Owner

@jonnymccullagh commented on GitHub (May 4, 2023):

I had that issue too. That is related to the ansible version as far as I remember. Installing a collection from a git repo source was added in more recent version of ansible. I am using 2.14.3 if that helps.

@jonnymccullagh commented on GitHub (May 4, 2023): I had that issue too. That is related to the ansible version as far as I remember. Installing a collection from a git repo source was added in more recent version of ansible. I am using 2.14.3 if that helps.