Session based JSON Query monitor #4032

Closed
opened 2026-02-28 03:48:48 -05:00 by deekerman · 1 comment
Owner

Originally created by @hanserasmus on GitHub (Mar 13, 2025).

⚠️ Please verify that this question has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

Hi All

I want to add devices via the JSON Query monitor type. The problem is that the source of these devices is behind a session based API. So I cannot use basic authentication to retrieve them, I need to have an active cookie which is set when I call the API. Anyone have any idea how to set up such a monitor in Uptime Kuma? If it is even possible?

TIA.

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

Version: 1.23.16

💻 Operating System and Arch

Ubuntu 24.04

🌐 Browser

Firefox 136.1.0

🖥️ Deployment Environment

  • Runtime: Docker
  • Database: sqlite
  • Filesystem used to store the database on: ext4
  • number of monitors: Not many yet
Originally created by @hanserasmus on GitHub (Mar 13, 2025). ### ⚠️ Please verify that this question has NOT been raised before. - [x] I checked and didn't find similar issue ### 🛡️ Security Policy - [x] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem Hi All I want to add devices via the JSON Query monitor type. The problem is that the source of these devices is behind a session based API. So I cannot use basic authentication to retrieve them, I need to have an active cookie which is set when I call the API. Anyone have any idea how to set up such a monitor in Uptime Kuma? If it is even possible? TIA. ### 📝 Error Message(s) or Log _No response_ ### 🐻 Uptime-Kuma Version Version: 1.23.16 ### 💻 Operating System and Arch Ubuntu 24.04 ### 🌐 Browser Firefox 136.1.0 ### 🖥️ Deployment Environment - Runtime: Docker - Database: sqlite - Filesystem used to store the database on: ext4 - number of monitors: Not many yet
deekerman 2026-02-28 03:48:48 -05:00
  • closed this issue
  • added the
    help
    label
Author
Owner

@CommanderStorm commented on GitHub (Mar 14, 2025):

You will have to use the push monitor and write monitoring with session handling and your query into a small cronjob

@CommanderStorm commented on GitHub (Mar 14, 2025): You will have to use the push monitor and write monitoring with session handling and your query into a small cronjob
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#4032
No description provided.