shadcn.io is not affiliated with official shadcn/ui
Log Stream Tail Monitoring Block for Solid
A window that tails a typed 60-line sample of one cluster with Pause, a Follow switch, four counted level toggles, a service select, a search that marks matches and a download of the visible lines as a .log file.
Installation
Overview
Watch a service log arrive, hold it still to read it and cut it down to what matters with this log tail for Solid with Ark UI. It is Logbrook, a log tailing tool, showing the made-up cluster prod-cluster-01 in a fixed-height window with no sidebar. The top bar holds the cluster, a state pill ("Replaying a typed sample", "Paused" or "End of sample"), a Pause button that is first in the tab order and a Follow switch. A toolbar has four toggles for Error, Warn, Info and Debug, each with the count of lines so far, a service select and a search field that marks matches inside the lines (the slash key focuses it while focus is in the window). The log is a dark pane in either theme: 24 of a typed 60 lines are there at the start and one more arrives every 1.5 seconds, then it stops on "End of sample" and Pause becomes Replay. Pointing at the log holds it, scrolling up stops following and a button names the new lines waiting. The foot counts the lines on show and downloads them as a real .log file. Guides draw the frame; nothing is measured.
FAQ
How do I use my own log lines?
Edit SAMPLE: each entry is time|level|service|message with the level as E, W, I or D. The counts on the toggles, the service list filter, the search marks, the line count in the foot and the downloaded text are all worked out from the first shown lines of it. For a real stream, append lines to state as they arrive from your log source instead of stepping shown, and keep the same follow logic.
Why does it start by itself, and how do I stop it?
The sample replays so you can see a tail in motion. Pause is the first control in the tab order, pointing at the log also holds it, and when the sample ends it stops on End of sample with a Replay button. With reduced motion on, nothing ticks: the whole sample is shown and paused. The live status speaks a line count about every six seconds, never each line.
What does Follow do?
While it is on, the log stays scrolled to the newest line. Scrolling up turns it off by itself and a button shows how many new lines wait; pressing it, or switching Follow on, jumps back to the end. The page itself never scrolls: only the log region moves.
Is the download real?
Yes. Download visible lines writes the lines that pass the level, service and search filters to a .log file in your browser with the DownloadTrigger; nothing is uploaded.
What stays local in the demo?
The lines are invented (documentation address ranges, made-up services and request ids) and nothing is read from a cluster. The filters, Follow and Pause only change state in the tab. To wire it for real, feed shown's lines from your log API or a WebSocket and keep the region, filters and download as they are.