Embed Widgets

Embed widgets let you display a live status indicator on any external site — a status page, internal dashboard, or documentation site. Each widget monitors a heartbeat signal and shows whether your service is up, degraded, or down.

Creating a widget

--embed::status:create:api-status

You will be prompted to configure:

• Name — used to reference the widget later
• Allowed origin — the domain allowed to display the embed (e.g. https://yoursite.com)
• Heartbeat timeout — minutes before the widget switches to degraded state (2–5 min)
• Notify on heartbeat miss — optionally send a notification when the heartbeat is missed
• Integration + channel — where to send notifications

Managing widgets

--embed::status                        → list all widgets
--embed::status:api-status             → view details
--embed::status:api-status:edit        → edit configuration
--embed::status:api-status:delete      → delete

How heartbeats work

Your service pings a Loguro heartbeat endpoint at regular intervals. If a ping doesn’t arrive within the timeout window, the widget flips to a degraded/down state and (optionally) fires a notification.

Embedding

Each widget provides an embed snippet — a small script or iframe — that you include in your external site. The snippet uses the widget’s unique token to authenticate and poll for status.

Plan requirements

Embed widget creation requires the Solo plan or higher.

Security

• Each widget token is scoped to a single allowed origin
• Requests from other origins are rejected
• Tokens can be rotated by deleting and recreating the widget

Notes

• Widgets are scoped to the current project
• The allowed origin is normalized to protocol://hostname — path and port are stripped