api integration for displaying which monitors do have maintenance and give informations about it #3327

Closed
opened 2026-02-28 03:25:48 -05:00 by deekerman · 2 comments
Owner

Originally created by @einlichtvogel on GitHub (May 11, 2024).

🏷️ Feature Request Type

API / automation options

🔖 Feature description

An endpoint or an section in the metrics api to display informations about maintenance, and which service it has, for how long, etc.

✔️ Solution

like already said above

Alternatives

web-scraping the status page, and building the informations together for yourself

📝 Additional Context

No response

Originally created by @einlichtvogel on GitHub (May 11, 2024). ### 📑 I have found these related issues/pull requests - ### 🏷️ Feature Request Type API / automation options ### 🔖 Feature description An endpoint or an section in the metrics api to display informations about maintenance, and which service it has, for how long, etc. ### ✔️ Solution like already said above ### ❓ Alternatives web-scraping the status page, and building the informations together for yourself ### 📝 Additional Context _No response_
deekerman 2026-02-28 03:25:48 -05:00
Author
Owner

@CommanderStorm commented on GitHub (May 11, 2024):

I think this is covered in #118 as the currently planned solution would essentially offer all current socket.io calls as REST endpoints
=> closed as a duplicate

@CommanderStorm commented on GitHub (May 11, 2024): - we currenlty don't have a REST api see #118 for further context and the working plan to get there - Please refer to https://uptime-kuma-api.readthedocs.io/en/latest/api.html#uptime_kuma_api.UptimeKumaApi.get_maintenances for a python api wrapper around the internal socket.io api - or https://github.com/BigBoot/AutoKuma?tab=readme-ov-file#kuma-cli-- for a cli of the same I think this is covered in #118 as the currently planned solution would essentially offer all current socket.io calls as REST endpoints => closed as a duplicate
Author
Owner

@CommanderStorm commented on GitHub (May 11, 2024):

Ah forgot about the metrics:

We already have this metric

# HELP monitor_status Monitor Status (1 = UP, 0= DOWN, 2= PENDING, 3= MAINTENANCE)
# TYPE monitor_status gauge
monitor_status{monitor_name="online",monitor_type="http",monitor_url="https://google.com",monitor_hostname="null",monitor_port="null"} 1
monitor_status{monitor_name="under maintenacne",monitor_type="http",monitor_url="https://example.com",monitor_hostname="null",monitor_port="null"} 3
@CommanderStorm commented on GitHub (May 11, 2024): Ah forgot about the metrics: We already have this metric ``` # HELP monitor_status Monitor Status (1 = UP, 0= DOWN, 2= PENDING, 3= MAINTENANCE) # TYPE monitor_status gauge monitor_status{monitor_name="online",monitor_type="http",monitor_url="https://google.com",monitor_hostname="null",monitor_port="null"} 1 monitor_status{monitor_name="under maintenacne",monitor_type="http",monitor_url="https://example.com",monitor_hostname="null",monitor_port="null"} 3 ```
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#3327
No description provided.