TraceWise Status & Monitoring

Description

Show visitors whether your service is up, degraded, or down, and what has happened recently, on any WordPress page.

TraceWise is a hosted uptime and status service from RazorSoft, Inc. This plugin places a published TraceWise status page on your site as five widgets. Visitors see the current status, recent uptime, and incidents. You add them from the WordPress editor.

Public widgets work without a TraceWise account and without an API key. They read a status page that is already public, including the demo page. Publishing your own status page is done in TraceWise, on the plan you choose there. This plugin does not include paid TraceWise features for free.

• Status Badge shows the overall status. Uptime is optional.
• Status Indicator shows a status dot and label. The label can be hidden.
• Status Card shows a short summary and a link to the full status page.
• Uptime History shows daily reliability for 7, 30, or 90 days.
• Incident List shows 5, 10, or 20 recent incidents. Resolved incidents can be hidden.

Use them as Gutenberg blocks or as shortcodes: [tracewise_status], [tracewise_indicator], [tracewise_card], [tracewise_history], and [tracewise_incidents]. Gutenberg, the Site Editor, the Classic Editor, and builders that run shortcodes all work. A Custom HTML block does not run shortcodes.

Save the status page you use most often under TraceWise → Public Status Widgets. Widgets that leave the slug blank use that page. A block or shortcode can name a different public status page. How many public status pages a workspace can publish depends on the TraceWise plan.

An API key is optional. Paste one under TraceWise → Connection when you want to view or manage monitors from WordPress. The TraceWise menu also includes Overview and Monitors, and administrators see a Dashboard widget for overall health. Those screens use the key. The key is encrypted in WordPress and is used only for server-side requests. It is not added to pages, blocks, JavaScript, or REST responses. Public widgets keep working if you never connect a key.

TraceWise plan limits still apply. Those limits include how many monitors a workspace can create, the shortest check interval, how many public status pages it can publish, and the API rate limit. This plugin shows those limits when TraceWise returns them. It does not raise them or change TraceWise prices.

Get started

1. Install and activate TraceWise Status & Monitoring.
2. Open TraceWise → Public Status Widgets. Save demo to preview, or paste the slug of a published status page.
3. Edit a page, insert a TraceWise block, or add a shortcode such as [tracewise_status].
4. Optional: create an API key in TraceWise and paste it under TraceWise → Connection to view or manage monitors.

Display options

Each block and shortcode can set slug, theme, show_uptime, show_label, period, limit, show_resolved, and refresh. Leave slug off to use the default status page.

auto follows the visitor's color scheme. `light` and `dark` set the status colors. Leave `refresh` empty to use the saved setting, use `0` to load once, and use at least `60` to poll. To match a theme, add CSS variables such as `--tw-status-operational` and `--tw-status-surface` on a parent. See the [component documentation](https://www.tracewise.dev/docs/components).

External service and privacy

TraceWise Status & Monitoring contacts https://www.tracewise.dev, an external service operated by RazorSoft, Inc.

• Public widgets send the status-page slug to the hosted embed, https://www.tracewise.dev/embed/status.js, in the visitor’s browser. The embed then requests the published status page. No API key is included. Visitors of a page that contains a widget also receive that script from TraceWise. A page with no TraceWise widget does not load it. Several widgets on one page still load it once. The block editor loads it so the preview can run. The plugin does not accept a custom API URL.
• Optional monitoring management sends the API key from the WordPress server to https://www.tracewise.dev/api/v1. The browser does not receive the key. Responses used on the admin screens are cached briefly in WordPress. A key that can only read monitors can still open the monitor list. Create, edit, and delete stay hidden until TraceWise confirms monitors:write. Manual checks stay hidden until TraceWise confirms checks:run.
• The plugin stores the public widget settings and the encrypted API key in WordPress options. It does not send WordPress user accounts, comments, or post content to TraceWise.
• Uninstall deletes the plugin settings, the encrypted key, and cached monitor views. It does not delete WordPress content and it does not delete the TraceWise account. Deactivation leaves the settings and the key in place.
• Terms of Service: https://www.tracewise.dev/terms
• Privacy Policy: https://www.tracewise.dev/privacy

Translations

The text domain is tracewise-status-monitoring. PHP, block metadata, and the block editor scripts use that domain. The plugin directory, option names, block names, and shortcodes stay tracewise-status so existing sites keep working. The plugin does not ship translation files.