How it works
Last updated
Last updated
Whether you're using the online tailer, a client library or the command line tool, you'll first be shown a screen telling you the unique link for your Tailed session:
After pressing a key, any content from the console, stdout or stderr will be captured and sent to your Tailed session (as well as your screen).
By default, the view of the streaming content is pinned so that the most recent content is shown. However, scrolling upward will allow you to view up to 1,000 lines of earlier content. You can jump back to the live tail with the click of a button.
Command Line Tool - written in .NET 7 and then compiled to native binaries.
.NET Client Library - written in .NET Standard 2.1.
Node JS Client Library - written in Node 18.
Communications - uses SignalR over secure websockets.
Web site front end and Zero-Code tailer - written using Svelte 4 with conversion of ANSI escape codes to HTML using Ansi_Up.
Web site back end - written using ASP.NET Core 7.
The content is sent to the tailed.live server over a secure (HTTPS) websocket connection to a group within a SignalR hub. The web page for your session connects to that same hub group and receives the messages that are sent.
Anybody with the link is able to see the content. Messages are sent over a secure connection, but the individual messages themselves are not encrypted. If this is a concern, ensure that you don't send confidential information or credentials.
With both the client libraries and the command line tool, it's possible to specify an alternative hostname to tailed.live. Only the hostname is replaced; the protocol (HTTPS) and the path are unchanged.
No messages are recorded by the server. The SignalR hub code can be reviewed .
You can find the source code to the web site . The Svelte project builds to the wwwroot folder of the .NET project. It is the .NET project which is then published and deployed.
