OpenStatus Light Viewer

› logs.run/light

A few months ago, we released light.openstatus.dev (vercel-edge-ping) - a lightweight community edition of OpenStatus designed to monitor your HTTP endpoints via Vercel's edge regions and notify you if >50% of the requests go down. No dependencies, no UI, just the essentials. For more details, check out our README.

Now, we’re excited to announce support for an extensive dashboard. If you're already using Tinybird to store your data, simply redeploy the latest vercel-edge-ping project and include the updated pipes in Tinybird. You can then access your values via logs.run/light by updating the base URL of the API endpoint (use the floating button in the bottom left corner). By default, it will display demo values from light.openstatus.dev.

Own your data. Build your dashboard.

Get your own lightweight OpenStatus in two steps:

1. One-click deploy vercel-edge-ping
2. Change base URL of the API endpoint

Build your dashboard

For everyone who wants to build their own dashboard with the data-table-filters project, here's a snapshot of the current Folder Structure that's been used:

/src/app/light
├── api
│   └── route.ts
├── client.tsx
├── columns.tsx
├── constants.tsx
├── layout.tsx
├── page.tsx
├── query-options.ts
└── search-params.ts

/src/app/light
├── api
│   └── route.ts
├── client.tsx
├── columns.tsx
├── constants.tsx
├── layout.tsx
├── page.tsx
├── query-options.ts
└── search-params.ts

• route.ts: API endpoint to fetch Tinybird values.
• client.tsx: Tanstack query client to fetch data from route.ts.
• columns.tsx: TanStack column array configuration.
• constants.tsx: Filter and sheet fields configuration.
• layout.tsx: Simple layout component.
• page.tsx: Server component to cache nuqs search parameters.
• query-options.ts: Infinite query options used in client.tsx.
• search-params.ts: nuqs query parameters configuration.

We explore most of these files in the Guide (WIP) to support you in building your own data-table.

We're continuously refining the setup. While some configurations may appear duplicated, our ultimate goal is to consolidate everything into a single configuration file, making it easier to build an infinite logs data table from front to back.

We're taking you along on this journey.

What is the vercel-edge-ping project?

The vercel-edge-ping project is a lightweight, community edition of OpenStatus with the following basic features:

• Notification Channels (Slack, Discord, etc.)
• Cron Job (via Vercel or GitHub Actions)
• Storage (Tinybird)

Do I need to self-host the data-table-filters project to access my data?

Self-hosting is not required. If you have vercel-edge-ping ingesting data into Tinybird and are using the default pipes, you can open the API endpoint configuration. Click the floating button in the bottom left corner or press ⌘ + J. Enter the base URL, and the tb_endpoint cookie will be set automatically. Delete the cookie manually if needed.

Use the data-table-filters to build your own logs tables. Check out logs.run for a guide and more examples.

Is an authentication system provided?

No. The project is auth-agnostic, allowing you to implement your preferred authentication solution if needed. Be aware that your data will be publicly accessible via the API endpoint. We might add basic authentication in the future.

What's next?

We are looking for more use cases. If you don't want to use Vercel, we are planning to add more cloud provider in the future.

Please reach out to ping@openstatus.dev if you have specific use cases you'd like to see in action. Your feedback will help us refine the dashboard configuration and integrate more cloud providers.