starred/uptime-kuma

Fork 0

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

MQTT monitor type doesn't store ping data. #1033

New issue

Open

opened 2026-02-28 02:07:53 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 02:07:53 -05:00

Owner

Originally created by @geoffsmith82 on GitHub (Apr 26, 2022).

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

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

Description

After adding and configuring the MQTT monitor type, it records that the server is up/down but it doesn't store ping times.

👟 Reproduction steps

Add MQTT monitor type and configure with settings.

👀 Expected behavior

Something like

😓 Actual Behavior

🐻 Uptime-Kuma Version

1.15

💻 Operating System and Arch

Ubuntu 20.04

🌐 Browser

99.01

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

No response

Originally created by @geoffsmith82 on GitHub (Apr 26, 2022). ### ⚠️ Please verify that this bug 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) ### Description After adding and configuring the MQTT monitor type, it records that the server is up/down but it doesn't store ping times. ### 👟 Reproduction steps Add MQTT monitor type and configure with settings. ### 👀 Expected behavior Something like ![image](https://user-images.githubusercontent.com/9402374/165263516-12b6db7a-7717-42f4-b117-1c0140c08ca4.png) ### 😓 Actual Behavior ![image](https://user-images.githubusercontent.com/9402374/165263698-61a22bfe-eb8e-4cdc-a734-1da6204bdcb8.png) ### 🐻 Uptime-Kuma Version 1.15 ### 💻 Operating System and Arch Ubuntu 20.04 ### 🌐 Browser 99.01 ### 🐋 Docker Version _No response_ ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output _No response_

deekerman added the

feature-request

question

A:monitor

type:enhance-existing

labels

2026-02-28 02:07:53 -05:00

deekerman commented

2026-02-28 02:07:56 -05:00

Author

Owner

@chakflying commented on GitHub (Apr 26, 2022):

Reference #875, I think there is no generic way to measure latency in the pub-sub model.

@chakflying commented on GitHub (Apr 26, 2022): Reference #875, I think there is no generic way to measure latency in the pub-sub model.

deekerman commented

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

Author

Owner

@geoffsmith82 commented on GitHub (Apr 27, 2022):

If I am getting what you mean... I would think it would be the time between sending the pub command and receiving the response back that is accepted as up via the sub message. Or are you talking about an implementation detail?

@geoffsmith82 commented on GitHub (Apr 27, 2022): If I am getting what you mean... I would think it would be the time between sending the pub command and receiving the response back that is accepted as up via the sub message. Or are you talking about an implementation detail?

deekerman commented

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

Author

Owner

@CommanderStorm commented on GitHub (Apr 14, 2024):

Issue was likely resolved by https://github.com/louislam/uptime-kuma/pull/3857, will have to see after the beta release, because I don't have a good setup to test mqtt

@CommanderStorm commented on GitHub (Apr 14, 2024): Issue was likely resolved by https://github.com/louislam/uptime-kuma/pull/3857, will have to see after the beta release, because I don't have a good setup to test mqtt