starred/uptime-kuma

Fork 0

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

Cropped monitor names in nested groups #4202

New issue

Open

opened 2026-02-28 03:54:32 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 03:54:32 -05:00

Owner

Originally created by @tobias-carlbom on GitHub (Jul 13, 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

Hi,

Is it a know problem that the monitoring item name gets cropped in nested groups?
Please see image below:

I plan to add more nested groups but this problem seems to be "worse" if i add more sub levels to the tree.

The reason that i am repeating eg Carlboms Data on many monitoring items (having long names), is that i need this metadata in the notifications.

I am experiencing this in tag Latest and in tag Beta.

📝 Error Message(s) or Log

🐻 Uptime-Kuma Version

2.0.0-beta.3

💻 Operating System and Arch

Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux

🌐 Browser

Firefox 139.0.4

🖥️ Deployment Environment

Runtime Environment:
- Docker: Version 28.3.2 (Build Wed Jul 9 16:13:56 2025)
- Docker Compose: Version v2.5.0
- CasaOS: 0.4.14
Database:
- SQLite: Embedded
Database Storage:
- Filesystem:
  - Linux: ext4
- Storage Medium: NVMe
Uptime Kuma Setup:
- Number of monitors: 100

Originally created by @tobias-carlbom on GitHub (Jul 13, 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 Hi, Is it a know problem that the monitoring item name gets cropped in nested groups? Please see image below: <img width="1039" height="573" alt="Image" src="https://github.com/user-attachments/assets/558434a8-02f7-43ae-b1cb-94583c2efbe8" /> <img width="674" height="464" alt="Image" src="https://github.com/user-attachments/assets/33963c5b-31c6-496e-8f85-256e23db1d77" /> I plan to add more nested groups but this problem seems to be "worse" if i add more sub levels to the tree. The reason that i am repeating eg Carlboms Data on many monitoring items (having long names), is that i need this metadata in the notifications. I am experiencing this in tag Latest and in tag Beta. ### 📝 Error Message(s) or Log ```bash session ``` ### 🐻 Uptime-Kuma Version 2.0.0-beta.3 ### 💻 Operating System and Arch Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux ### 🌐 Browser Firefox 139.0.4 ### 🖥️ Deployment Environment - **Runtime Environment**: - Docker: Version `28.3.2` (Build `Wed Jul 9 16:13:56 2025`) - Docker Compose: Version `v2.5.0` - CasaOS: `0.4.14` - **Database**: - SQLite: Embedded - **Database Storage**: - **Filesystem**: - Linux: ext4 - **Storage Medium**: NVMe - **Uptime Kuma Setup**: - Number of monitors: `100`

deekerman added the

labels

2026-02-28 03:54:32 -05:00

deekerman commented

2026-02-28 03:54:36 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jul 13, 2025):

No, this is not known. Feel free to add a PR to fix the CSS in this department.

@CommanderStorm commented on GitHub (Jul 13, 2025): No, this is not known. Feel free to add a PR to fix the CSS in this department.

deekerman commented

2026-02-28 03:54:36 -05:00

Author

Owner

@VNRARA commented on GitHub (Jul 13, 2025):

Found the issue:

I think the width should be 100% with the "none" setting.

@VNRARA commented on GitHub (Jul 13, 2025): Found the issue: <img width="1587" height="657" alt="Image" src="https://github.com/user-attachments/assets/1097aca2-8a89-49a9-8e46-9415c938cbf9" /> I think the width should be 100% with the "none" setting.

deekerman commented

2026-02-28 03:54:36 -05:00

Author

Owner

@nklsgod commented on GitHub (Aug 23, 2025):

I will fix this Issue asap :)

@nklsgod commented on GitHub (Aug 23, 2025): I will fix this Issue asap :)