starred/uptime-kuma

Fork 0

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

[ping] jitter and packet loss in graphs #1144

New issue

Open

opened 2026-02-28 02:11:30 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-28 02:11:30 -05:00

Owner

Originally created by @ItIsSeven on GitHub (Jun 4, 2022).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

UI Feature

🔖 Feature description

I'd love to have SmokePing style graphs like this:

✔️ Solution

It would be awesome if I could just completely replace SmokePing with Uptime-Kuma cause currently I still have to run both. As SmokePing still gives me a lot more data than UptimeKuma can at times as there's not any sort of smoke so I can see jitter and that sort of thing. And the chart doesn't go as far back in terms of history as smokeping can/does.

Or a more modern example would be how CocoPacket have implemented what SmokePing have if you want to use that as some form of inspiration. You'd probably want it more on the lines of how they have it as everything is more modern with the ability to have a dark theme etc...

Originally created by @ItIsSeven on GitHub (Jun 4, 2022). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type UI Feature ### 🔖 Feature description I'd love to have SmokePing style graphs like this: ![image](https://user-images.githubusercontent.com/63268023/172022210-2a818488-748f-4113-a7b4-7a0a71794c51.png) ### ✔️ Solution It would be awesome if I could just completely replace SmokePing with Uptime-Kuma cause currently I still have to run both. As SmokePing still gives me a lot more data than UptimeKuma can at times as there's not any sort of smoke so I can see jitter and that sort of thing. And the chart doesn't go as far back in terms of history as smokeping can/does. Or a more modern example would be how CocoPacket have implemented what SmokePing have if you want to use that as some form of inspiration. You'd probably want it more on the lines of how they have it as everything is more modern with the ability to have a dark theme etc...

deekerman added the

feature-request

A:dashboard

A:monitor

labels

2026-02-28 02:11:30 -05:00

deekerman commented

2026-02-28 02:11:33 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jun 3, 2023):

@ItIsSeven Could you please rework this issue to be more specific what Feature of SmokePing you would like to be implemented?
Please limit yourself to one issue per issue and run a duplication search for each of the issues.
Like this, I am not sure what your feature request is ^^

@CommanderStorm commented on GitHub (Jun 3, 2023): @ItIsSeven Could you please rework this issue to be more specific what Feature of SmokePing you would like to be implemented? Please limit yourself to one issue per issue and run a duplication search for each of the issues. Like this, I am not sure what your feature request is ^^

deekerman commented

2026-02-28 02:11:33 -05:00

Author

Owner

@CM000n commented on GitHub (Jul 18, 2023):

I am also in favor of this feature request.
It would be absolutely cool if uptime-kuma could enrich its graphs with more information about packet loss on ping requests.

Similar to smokping, this would require sending multiple packets with each ping request (smokeping sends 20 per request).

The packet loss could then be calculated for each request and be displayed in the graph with a different color for its average value. The outliers outside the average are also shown in the graph, but without color coding (smoke around the average). The more frequently the data points occur for a request for a certain time, the darker the coloring of the "smoke".

@CM000n commented on GitHub (Jul 18, 2023): I am also in favor of this feature request. It would be absolutely cool if uptime-kuma could enrich its graphs with more information about packet loss on ping requests. Similar to smokping, this would require sending multiple packets with each ping request (smokeping sends 20 per request). The packet loss could then be calculated for each request and be displayed in the graph with a different color for its average value. The outliers outside the average are also shown in the graph, but without color coding (smoke around the average). The more frequently the data points occur for a request for a certain time, the darker the coloring of the "smoke".

deekerman commented

2026-02-28 02:11:33 -05:00

Author

Owner

@smitty-nieto commented on GitHub (Dec 13, 2023):

I concur. We need packetloss alerting as well. We have a client currently that is seeing 30-80% packet loss.
While I'd love for uptime to be our primary monitor, it doesn't support anything more than an up/down check.

@smitty-nieto commented on GitHub (Dec 13, 2023): I concur. We need packetloss alerting as well. We have a client currently that is seeing 30-80% packet loss. While I'd love for uptime to be our primary monitor, it doesn't support anything more than an up/down check.

deekerman commented

2026-02-28 02:11:33 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 13, 2023):

We need packetloss alerting as well.

packetloss alerting is not covered by this issue. This Issue only covers enhancing the graph for ping-monitors.
=> Please open another issue

@CommanderStorm commented on GitHub (Dec 13, 2023): > We need packetloss alerting as well. packetloss alerting is not covered by this issue. This Issue only covers enhancing the graph for ping-monitors. => Please open another issue

deekerman commented

2026-02-28 02:11:34 -05:00

Author

Owner

@ShadowJonathan commented on GitHub (Dec 15, 2023):

Notable remark about this feature request; I'd like for this to be visible on public status pages

@ShadowJonathan commented on GitHub (Dec 15, 2023): Notable remark about this feature request; I'd like for this to be visible on public status pages

deekerman commented

2026-02-28 02:11:34 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 15, 2023):

@ShadowJonathan What you are requesting is tracked in other issues and not here (⇒ less duplicates):

adding latency/ping graphs to the status page is tracked in #637
adding quick stats to the status page is tracked in https://github.com/louislam/uptime-kuma/issues/1667

Here is our contribution guide

@CommanderStorm commented on GitHub (Dec 15, 2023): @ShadowJonathan What you are requesting is tracked in other issues and not here (⇒ less duplicates): - adding latency/ping graphs to the status page is tracked in #637 - adding quick stats to the status page is tracked in https://github.com/louislam/uptime-kuma/issues/1667 Here is our [contribution guide](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md)