···1010tag: engineering
1111---
12121313+› [logs.run/light](https://logs.run/light)
1414+1315A 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).
14161517Now, 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).
16181719
1818-1919-Check it out: [logs.run/light](https://logs.run/light)
20202121### Folder Structure
2222···64646565Self-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.
66666767-Use the [data-table-filters](https://github.com/openstatusHQ/data-table-filters) to build your own logs tables.
6767+Use the [data-table-filters](https://github.com/openstatusHQ/data-table-filters) to build your own logs tables. Check out [logs.run](https://logs.run) for a guide and more examples.
68686969### Is an authentication system provided?
7070