starred/uptime-kuma

Fork 0

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

iframe - Quick Stats Link for Embedding in Site #1278

New issue

Open

opened 2026-02-28 02:15:58 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-28 02:15:58 -05:00

Owner

Originally created by @spower1966 on GitHub (Jul 20, 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

Is it possible to have the Quick States available for embedding in an iFrame ?
Would be great to be able to embed into another web site for quick overview

✔️ Solution

iFrame availability of Quick Stats for be embedded in another web site.
Anonymous connection

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @spower1966 on GitHub (Jul 20, 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 Is it possible to have the Quick States available for embedding in an iFrame ? Would be great to be able to embed into another web site for quick overview ### ✔️ Solution iFrame availability of Quick Stats for be embedded in another web site. Anonymous connection ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman added the

feature-request

A:core

labels

2026-02-28 02:15:58 -05:00

deekerman commented

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

Author

Owner

@kristiandg commented on GitHub (Jul 20, 2022):

Ooo, that's a good one. I'd love that as well, so you could then create a small (more abridged) panel if you wanted, for a website. Selectable to either show all the data, or just the summary banner (All Systems Operational, Partially Degraded, etc), which clicking on that link then takes you to the detailed dashboard. Nice.

@kristiandg commented on GitHub (Jul 20, 2022): Ooo, that's a good one. I'd love that as well, so you could then create a small (more abridged) panel if you wanted, for a website. Selectable to either show all the data, or just the summary banner (All Systems Operational, Partially Degraded, etc), which clicking on that link then takes you to the detailed dashboard. Nice.

deekerman commented

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

Author

Owner

@sacarino commented on GitHub (Sep 8, 2022):

It would be great if this wasn't specifically an iframe. That's a bit limiting.

I'm looking for ways to get that summary data like All Systems Operational, Partially Degraded, but I'd like to be able to style it, etc. to match the client that it would be displayed in.

Maybe this could be an GET endpoint that returns a json payload? Just thinking about the API being discussed in #118

@sacarino commented on GitHub (Sep 8, 2022): It would be great if this wasn't _specifically_ an iframe. That's a bit limiting. I'm looking for ways to get that summary data like `All Systems Operational`, `Partially Degraded`, but I'd like to be able to style it, etc. to match the client that it would be displayed in. Maybe this could be an `GET` endpoint that returns a json payload? Just thinking about the API being discussed in #118

deekerman commented

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

Author

Owner

@ianpogi5 commented on GitHub (Aug 4, 2023):

I think a quick stats api would be great so anyone can embed the data to anywhere they like.

An example would be:

GET https://uptime.example.com/api/quick-stats

And then return something like:

{
    "up": 143,
    "down": 2,
    "maintenance": 0,
    "unknown": 0,
    "pause": 4
}

@ianpogi5 commented on GitHub (Aug 4, 2023): I think a quick stats api would be great so anyone can embed the data to anywhere they like. An example would be: ```api GET https://uptime.example.com/api/quick-stats ``` And then return something like: ```json { "up": 143, "down": 2, "maintenance": 0, "unknown": 0, "pause": 4 } ```

deekerman commented

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

Author

Owner

@CommanderStorm commented on GitHub (Aug 4, 2023):

Look at https://status.yourdomain.xyz/api/status-page/your-status-page-name. It returns a JSON of all the added status monitors, but if you need heartbeat, look at https://status.yourdomain.xyz/api/status-page/heartbeat/your-status-page-name.

@CommanderStorm commented on GitHub (Aug 4, 2023): Look at `https://status.yourdomain.xyz/api/status-page/your-status-page-name`. It returns a JSON of all the added status monitors, but if you need heartbeat, look at `https://status.yourdomain.xyz/api/status-page/heartbeat/your-status-page-name`.

deekerman commented

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

Author

Owner

@Subbeh commented on GitHub (Aug 6, 2023):

Look at https://status.yourdomain.xyz/api/status-page/your-status-page-name. It returns a JSON of all the added status monitors, but if you need heartbeat, look at https://status.yourdomain.xyz/api/status-page/heartbeat/your-status-page-name.

Is there an easy way just to see if the current overall status of the services is degraded/operational? Without having to fetch the entire heartbeat history of all the monitors.

@Subbeh commented on GitHub (Aug 6, 2023): > Look at `https://status.yourdomain.xyz/api/status-page/your-status-page-name`. It returns a JSON of all the added status monitors, but if you need heartbeat, look at `https://status.yourdomain.xyz/api/status-page/heartbeat/your-status-page-name`. Is there an easy way just to see if the current overall status of the services is degraded/operational? Without having to fetch the entire heartbeat history of all the monitors.

deekerman commented

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

Author

Owner

@RK62 commented on GitHub (Sep 3, 2023):

Thanks for the tip. Unfortunately, the links do not give any information about the status of the individual monitors. even if I evaluate the time series, paused monitors continue with the output of the last status.

The suggestion of @ianpogi5 will be a good solution for integrations. Additionally, there is no need to remember to add new monitors to a status page.
If this becomes too complex, an output with the last status of all monitors would be good, so that you can easily count and evaluate yourself. This will be my preferred solution.

@RK62 commented on GitHub (Sep 3, 2023): Thanks for the tip. Unfortunately, the links do not give any information about the status of the individual monitors. even if I evaluate the time series, paused monitors continue with the output of the last status. The suggestion of @ianpogi5 will be a good solution for integrations. Additionally, there is no need to remember to add new monitors to a status page. If this becomes too complex, an output with the last status of all monitors would be good, so that you can easily count and evaluate yourself. This will be my preferred solution.