-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
Open
Labels
feature-requestRequest for new features to be addedRequest for new features to be added
Description
⚠️ Please verify that your question has not already been reported
- I have searched the existing issues and found no similar reports.
🛡️ Security Policy
- I have read and agree to Uptime Kuma's Security Policy.
📝 Describe your problem
would it be ok, and i'm asking before i start working on it, with you CommanderStorm, to allow including the full response from the api that we use in the monitor?
i would like to be able to parse it using the liquidjs, so that i can customize the message to a human readable format.
{
"current": "2025.1.2",
"latest": "2026.1.2",
"status": "Update"
}
Ex.
Update Rerquired! Current version 2025.1.2 < latest version 2026.1.2
Currently we only expose these AFAIK
Templatability is achieved via the Liquid templating language. Please refer to the [documentation](https://liquidjs.com/) for usage instructions.
{{ msg }} : message of the notification
{{ name }} : service name
{{ status }} : status
{{ hostnameOrURL }} : hostname or URL
{{ heartbeatJSON }} : object describing the heartbeat (only available for UP/DOWN notifications)
{{ monitorJSON }} : object describing the monitor (only available for UP/DOWN/Certificate expiry notifications)
📝 Error Message(s) or Log
🐻 Uptime-Kuma Version
nightly
💻 Operating System and Arch
ubuntu
🌐 Browser
firefox
🖥️ Deployment Environment
docker
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
feature-requestRequest for new features to be addedRequest for new features to be added