Prometheus logging noise due to cloning tags: Added label "tag" is not included in initial labelset #4605

New issue

Open

opened 2026-02-28 04:09:02 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-28 04:09:02 -05:00

Owner

Originally created by @gaopenghua-2022 on GitHub (Jan 14, 2026).

The cloned entry, despite being tagged, does not display the tag after being saved. It requires re-editing and saving again

🛡️ Security Policy

I have read and agree to Uptime Kuma's Security Policy.

📝 Description

No response

👟 Reproduction steps

copy-save

👀 Expected behavior

show the tag when I save the copy data

😓 Actual Behavior

not show the tag

🐻 Uptime-Kuma Version

latest

💻 Operating System and Arch

centos7.9

🌐 Browser

google

🖥️ Deployment Environment

centos7

📝 Relevant log output

Originally created by @gaopenghua-2022 on GitHub (Jan 14, 2026). ### 📑 I have found these related issues/pull requests The cloned entry, despite being tagged, does not display the tag after being saved. It requires re-editing and saving again ### 🛡️ Security Policy - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy). ### 📝 Description _No response_ ### 👟 Reproduction steps copy-save ### 👀 Expected behavior show the tag when I save the copy data ### 😓 Actual Behavior not show the tag ### 🐻 Uptime-Kuma Version latest ### 💻 Operating System and Arch centos7.9 ### 🌐 Browser google ### 🖥️ Deployment Environment centos7 ### 📝 Relevant log output ```bash session ```

deekerman added the

bug

A:deployment

A:metrics

labels

2026-02-28 04:09:02 -05:00

deekerman commented

2026-02-28 04:09:05 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jan 14, 2026):

cannot reproduce on our latest nightly

docker run --pull always --net host ghcr.io/louislam/uptime-kuma:nightly2

There is a bit of an issue with prometheus screaming bloody murder, but that is not the bug that you reported.

2026-01-14T10:43:01+01:00 [PROMETHEUS] ERROR: Caught error Error: Added label "tag" is not included in initial labelset: [
  'monitor_id',
  'monitor_name',
  'monitor_type',
  'monitor_url',
  'monitor_hostname',
  'monitor_port'
]
    at validateLabel (/app/node_modules/prom-client/lib/validation.js:20:10)
    at set (/app/node_modules/prom-client/lib/gauge.js:144:2)
    at Gauge.set (/app/node_modules/prom-client/lib/gauge.js:29:3)
    at Prometheus.update (/app/server/prometheus.js:162:36)
    at Proxy.handleTlsInfo (/app/server/model/monitor.js:2053:26)
    at async TLSSocket.<anonymous> (/app/server/model/monitor.js:636:29)

@CommanderStorm commented on GitHub (Jan 14, 2026): cannot reproduce on our latest nightly ```bash docker run --pull always --net host ghcr.io/louislam/uptime-kuma:nightly2 ``` There is a bit of an issue with prometheus screaming bloody murder, but that is not the bug that you reported. ``` 2026-01-14T10:43:01+01:00 [PROMETHEUS] ERROR: Caught error Error: Added label "tag" is not included in initial labelset: [ 'monitor_id', 'monitor_name', 'monitor_type', 'monitor_url', 'monitor_hostname', 'monitor_port' ] at validateLabel (/app/node_modules/prom-client/lib/validation.js:20:10) at set (/app/node_modules/prom-client/lib/gauge.js:144:2) at Gauge.set (/app/node_modules/prom-client/lib/gauge.js:29:3) at Prometheus.update (/app/server/prometheus.js:162:36) at Proxy.handleTlsInfo (/app/server/model/monitor.js:2053:26) at async TLSSocket.<anonymous> (/app/server/model/monitor.js:636:29)

deekerman commented

2026-02-28 04:09:07 -05:00

Author

Owner

@xfactor-toml commented on GitHub (Jan 27, 2026):

I will try to fix this issue.

@xfactor-toml commented on GitHub (Jan 27, 2026): I will try to fix this issue.