Openstatus
www.openstatus.dev
chore: blog post
authored by
Maximilian Kaske
and committed by
Maximilian Kaske
4984ec25
e60e1412
+77
apps/web/public/assets/posts/openstatus-light-viewer/data-table-popover.png
apps/web/public/assets/posts/openstatus-light-viewer/data-table-popover.png
This is a binary file and will not be displayed.
apps/web/public/assets/posts/openstatus-light-viewer/data-table.png
apps/web/public/assets/posts/openstatus-light-viewer/data-table.png
This is a binary file and will not be displayed.
+77
apps/web/src/content/posts/openstatus-light-viewer.mdx
+77
apps/web/src/content/posts/openstatus-light-viewer.mdx
···
1
+
---
2
+
title: OpenStatus Light Viewer
3
+
description: The perfect companion for the vercel-edge-ping project
4
+
author:
5
+
name: Maximilian Kaske
6
+
url: https://x.com/mxkaske
7
+
avatar: /assets/authors/max.png
8
+
publishedAt: 2025-03-30
9
+
image: /assets/posts/openstatus-light-viewer/data-table.png
10
+
tag: engineering
11
+
---
12
+
13
+
The first real-world use case of the [logs.run](https://logs.run/light) project and a simple yet effective showcase of the [data-table-filters](https://github.com/openstatusHQ/data-table-filters) project.
14
+
15
+
A few months ago, we released [light.openstatus.dev](https://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](https://github.com/openstatusHQ/vercel-edge-ping).
16
+
17
+
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](https://github.com/openstatusHQ/vercel-edge-ping/tree/main/tb/pipes) in Tinybird. You can then access your values via [logs.run/light](https://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](https://light.openstatus.dev).
18
+
19
+
20
+
21
+
### Folder Structure
22
+
23
+
Here's a snapshot of the current **Folder Structure**:
24
+
25
+
```json
26
+
/src/app/light
27
+
├── api
28
+
│ └── route.tsx
29
+
├── client.tsx
30
+
├── columns.tsx
31
+
├── constants.tsx
32
+
├── layout.tsx
33
+
├── page.tsx
34
+
├── query-options.ts
35
+
└── search-params.ts
36
+
```
37
+
38
+
- **`client.tsx`**: Client component that queries the API and performs minor data transformations.
39
+
- **`columns.tsx`**: TanStack column array configuration.
40
+
- **`constants.tsx`**: Filter and sheet fields configuration.
41
+
- **`layout.tsx`**: Simple layout component.
42
+
- **`page.tsx`**: Server component to cache `nuqs` search parameters.
43
+
- **`query-options.ts`**: Infinite query options used in `client.tsx`.
44
+
- **`search-params.ts`**: `nuqs` query parameters configuration.
45
+
46
+
We explore most of these files in the [Guide (WIP)](https://logs.run/guide) to support you in building your own data-table.
47
+
48
+
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.
49
+
50
+
We're taking you along on this journey.
51
+
52
+
---
53
+
54
+
55
+
### What is the `vercel-edge-ping` project?
56
+
57
+
The [`vercel-edge-ping`](https://github.com/openstatusHQ/vercel-edge-ping) project is a lightweight, community edition of OpenStatus with the following basic features:
58
+
59
+
- Notification Channels (Slack, Discord, etc.)
60
+
- Cron Job (via Vercel or GitHub Actions)
61
+
- Storage (Tinybird)
62
+
63
+
### Do I need to self-host the `data-table-filters` project to access my data?
64
+
65
+
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 <kbd>⌘ + J</kbd>. Enter the base URL, and the `tb_endpoint` cookie will be set automatically. Delete the cookie manually if needed.
66
+
67
+
Use the [data-table-filters](https://github.com/openstatusHQ/data-table-filters) to build your own logs tables.
68
+
69
+
### Is an authentication system provided?
70
+
71
+
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.
72
+
73
+
---
74
+
75
+
### We are looking for more use cases!
76
+
77
+
Please reach out to [ping@openstatus.dev](mailto:ping@openstatus.dev) if you have specific use cases you'd like to see in action. Your feedback will help us refine the configuration, routes, and component APIs.