starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

URL monitor group SMS notification #4340

New issue

Open

opened 2026-02-28 03:58:57 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 03:58:57 -05:00

Owner

Originally created by @pcsystemd on GitHub (Oct 15, 2025).

⚠️ 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

I created sensor groups and activated SMS notifications for one group. It works fine, but when I receive the SMS, the URL variable is empty.
Is it possible to activate a notification for a group and, when the SMS is received, have the URL of the sensor that has crashed?

This may not be possible because the notification is activated for the sensor group, or I am not using the correct variable for the URL of the sensor in the group that is down!

My body is as follows

"body": { "text": "Monitoring - Nom: {{ monitorJSON['name'] }} - Url:{{ monitorJSON['url'] }} -Date:{{ heartbeatJSON['time'] }} \n Message : {{msg}}"

📝 Error Message(s) or Log

🐻 Uptime-Kuma Version

1.23.16

💻 Operating System and Arch

Debian 11

🌐 Browser

Chrome

🖥️ Deployment Environment

Runtime Environment:
- Docker: Version 18.09.3 (Build 774a1f4)
- Docker Compose: Version 1.23.2
- Portainer (BE/CE): Version X.X.X (LTS: Yes/No)
- MariaDB: Version X.X.X (LTS: Yes/No)
- Node.js: Version X.X.X (LTS: Yes/No)
- Kubernetes (K3S/K8S): Version X.X.X (LTS: Yes/No, via [method/tool])
Database:
- SQLite: Embedded
- MariaDB: Embedded/External
Database Storage:
- Filesystem:
  - Linux: ext4/XFS/Btrfs/ZFS/F2FS
  - macOS: APFS/ HFS+
  - Windows: NTFS/ReFS
- Storage Medium: HDD/eMMC/SSD/NVMe
Uptime Kuma Setup:
- Number of monitors: X

Originally created by @pcsystemd on GitHub (Oct 15, 2025). ### ⚠️ Please verify that your question has not already been reported - [x] I have searched the [existing issues](https://github.com/louislam/uptime-kuma/issues?q=is%3Aissue%20sort%3Acreated-desc%20) and found no similar reports. ### 🛡️ Security Policy - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy). ### 📝 Describe your problem I created sensor groups and activated SMS notifications for one group. It works fine, but when I receive the SMS, the URL variable is empty. Is it possible to activate a notification for a group and, when the SMS is received, have the URL of the sensor that has crashed? This may not be possible because the notification is activated for the sensor group, or I am not using the correct variable for the URL of the sensor in the group that is down! My body is as follows `"body": { "text": "Monitoring - Nom: {{ monitorJSON['name'] }} - Url:{{ monitorJSON['url'] }} -Date:{{ heartbeatJSON['time'] }} \n Message : {{msg}}"` ### 📝 Error Message(s) or Log ```bash session ``` ### 🐻 Uptime-Kuma Version 1.23.16 ### 💻 Operating System and Arch Debian 11 ### 🌐 Browser Chrome ### 🖥️ Deployment Environment - **Runtime Environment**: - Docker: Version `18.09.3` (Build `774a1f4`) - Docker Compose: Version `1.23.2` - Portainer (BE/CE): Version `X.X.X` (LTS: Yes/No) - MariaDB: Version `X.X.X` (LTS: Yes/No) - Node.js: Version `X.X.X` (LTS: Yes/No) - Kubernetes (K3S/K8S): Version `X.X.X` (LTS: Yes/No, via `[method/tool]`) - **Database**: - SQLite: Embedded - MariaDB: Embedded/External - **Database Storage**: - **Filesystem**: - Linux: ext4/XFS/Btrfs/ZFS/F2FS - macOS: APFS/ HFS+ - Windows: NTFS/ReFS - **Storage Medium**: HDD/eMMC/SSD/NVMe - **Uptime Kuma Setup**: - Number of monitors: `X`

deekerman added the

feature-request

A:notifications

labels

2026-02-28 03:58:57 -05:00

deekerman commented

2026-02-28 03:59:00 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Oct 15, 2025):

The monitor groups don't currently provide good context about the contained children.
Valid FR, I relabled it

@CommanderStorm commented on GitHub (Oct 15, 2025): The monitor groups don't currently provide good context about the contained children. Valid FR, I relabled it

deekerman commented

2026-02-28 03:59:00 -05:00

Author

Owner

@pcsystemd commented on GitHub (Oct 16, 2025):

Thanks for the information. It would be great to have that option.

@pcsystemd commented on GitHub (Oct 16, 2025): Thanks for the information. It would be great to have that option.

deekerman commented

2026-02-28 03:59:00 -05:00

Author

Owner

@maxmichels commented on GitHub (Oct 27, 2025):

@pcsystemd what would be your expectation? That in the notification you get Info which Check of the group failed? At the moment the notification is triggered on group level and thus do not include the hostname as the group has none defined.

In case i am correct, what would be your expectation in case multiple fail at the same time? Which hostname should be included then?

@maxmichels commented on GitHub (Oct 27, 2025): @pcsystemd what would be your expectation? That in the notification you get Info which Check of the group failed? At the moment the notification is triggered on group level and thus do not include the hostname as the group has none defined. In case i am correct, what would be your expectation in case multiple fail at the same time? Which hostname should be included then?