Logs View: Two years in the making, one day of migration
We finally moved data-table-filters into the openstatus dashboard. What it grew into, and how to start using it.
30 stories
We finally moved data-table-filters into the openstatus dashboard. What it grew into, and how to start using it.
After three years of watching what our users monitor, we extracted our own health endpoints into a package. Per-dependency probes, ok | degraded | unhealthy, and adapters for Hono, Elysia, Express, Next.js and TanStack Start.
Self-hosting openstatus used to be a massive hurdle. That's no longer the case — let's see what's changed.
Most uptime monitoring exists so a dashboard can be green, not so you find out first. Why homepage pings, 200s, and single-region checks are theater — and what to monitor instead.
The same status page URL now serves a React page to humans and clean markdown to agents - chosen by Accept: text/markdown or a .md suffix. The page drops from ~60k tokens of HTML to ~1.2k of markdown, with the answer in the frontmatter. Here's how and why.
A build log: wiring an AI agent to openstatus webhooks so it writes the status page report itself, and the things that bit me along the way.
A year after our Reality Check post: what we shipped, what we killed, what we got wrong, and the people who helped us see what we couldn't. The honest receipt — positioning, design, distribution, ~8× the Google impression rate, and a defensible wedge.
Stop clicking. Start chatting. The new openstatus AI chat turns the dashboard into a conversation — with pretty tool cards and an MCP server for your own agents.
One package, one table, zero blind spots. How we wrangled CRUD from three surfaces into a single source of truth - and got a workspace-wide audit log almost for free. Another step toward compliance.
Design patterns for building CLIs that work for both developers and AI agents: TTY detection, wizard fallback, structured errors, and JSON output.
Import your entire status page setup — components, incidents, maintenances, subscribers, and monitors — from Atlassian Statuspage, Better Stack, or Instatus with our new one-click importer.
We have rebuilt the data-table-filters with a single schema, state management adapters, shadcn registry distribution, and an AI agent skill.
An always-green status page isn't a sign of reliability — it's a sign of opacity. Why the industry rewards dishonesty and what buyers should do about it.
Manage incidents from Slack with natural language — no slash commands, no context switching.
How we implemented a two-phase QR code flow to securely link Telegram groups to OpenStatus using Redis, polling, and stale-update filtering — no webhooks needed.
From duplicated components across three apps to a clean registry - our journey to building a shadcn/ui - compatible component library.
We're unifying our internal tRPC API and public REST API into a single ConnectRPC service. Here's how we're doing it—and how AI is accelerating the migration.
A major architectural refactor that decouples status pages from monitors, enabling flexible status reporting and better self-hosting support.
Showing 18 of 30 stories
Load more storiesGet the top AI news and tools straight to your inbox every week.
Weekly · AI news
Join 15,000+ AI enthusiasts