<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Oleksandr Zhyhalo</title>
    <description>The latest articles on DEV Community by Oleksandr Zhyhalo (@oleksandrzhyhalo).</description>
    <link>https://dev.to/oleksandrzhyhalo</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3964733%2F35ec25d7-3fe0-41fc-aee9-3f0260749d0b.png</url>
      <title>DEV Community: Oleksandr Zhyhalo</title>
      <link>https://dev.to/oleksandrzhyhalo</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/oleksandrzhyhalo"/>
    <language>en</language>
    <item>
      <title>I built a self-hosted log search tool for my team</title>
      <dc:creator>Oleksandr Zhyhalo</dc:creator>
      <pubDate>Tue, 09 Jun 2026 08:24:42 +0000</pubDate>
      <link>https://dev.to/oleksandrzhyhalo/i-built-a-self-hosted-log-search-tool-for-my-team-7di</link>
      <guid>https://dev.to/oleksandrzhyhalo/i-built-a-self-hosted-log-search-tool-for-my-team-7di</guid>
      <description>&lt;h2&gt;
  
  
  The backstory
&lt;/h2&gt;

&lt;p&gt;Some time ago I adopted &lt;a href="https://quickwit.io/" rel="noopener noreferrer"&gt;Quickwit&lt;/a&gt; at my company. For anyone who hasn't used it: Quickwit is a search engine that runs full-text search directly on object storage (S3 or anything S3-compatible). It decouples compute from storage, so you don't pay to keep big indexes warm to search older data. That model fits logs well.&lt;/p&gt;

&lt;p&gt;It worked well for us, but there was a gap. Quickwit is excellent at the search engine part and leaves the rest to you by design: no end-user experience around it, and little access control. We were missing what a team needs day to day, like a usable UI, authentication, and gated ingest.&lt;/p&gt;

&lt;p&gt;I started building that layer myself. It turned into Rootprint.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it is
&lt;/h2&gt;

&lt;p&gt;Besides the basics you'd expect for working with logs (controlling the view, seeing context around a log line, a filters panel, a histogram, severity-aware views), it adds:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;User management&lt;/strong&gt; with Google and GitHub authentication&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Authenticated endpoints&lt;/strong&gt; to ingest data&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cluster stats&lt;/strong&gt; so you can see what's going on&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A user activity overview&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Control over sources&lt;/strong&gt;, and more&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It runs on your own infrastructure, and it's Apache-2.0 licensed.&lt;/p&gt;

&lt;h2&gt;
  
  
  The stack
&lt;/h2&gt;

&lt;p&gt;I wanted it light and fast, so:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Backend:&lt;/strong&gt; Hono running on Bun&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Frontend:&lt;/strong&gt; Svelte 5 + SvelteKit, with Tailwind and DaisyUI&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How it plugs in
&lt;/h2&gt;

&lt;p&gt;Rootprint connects to any Quickwit instance through an environment variable. One caveat: it needs &lt;strong&gt;Quickwit 0.9+&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;To get started, grab the Docker Compose file and run it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-o&lt;/span&gt; docker-compose.yml https://docs.rootprint.io/files/docker-compose.full.yaml
docker compose up &lt;span class="nt"&gt;-d&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The docs cover the rest of the installation options: &lt;a href="https://docs.rootprint.io/install/docker-compose" rel="noopener noreferrer"&gt;docs.rootprint.io/install/docker-compose&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it's going
&lt;/h2&gt;

&lt;p&gt;I want to build a platform for &lt;strong&gt;logs and traces&lt;/strong&gt; that holds up against anything else out there. Right now I'm focused on the log search experience; traces are on the roadmap but not built yet.&lt;/p&gt;

&lt;p&gt;It's still early and pre-1.0, so expect breaking changes between releases.&lt;/p&gt;

&lt;h2&gt;
  
  
  I'd love your feedback
&lt;/h2&gt;

&lt;p&gt;If this sounds useful, I'd appreciate you trying it out and telling me what's broken, confusing, or missing. Feedback and contributors are welcome.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Source code: &lt;a href="https://github.com/rootprint/rootprint" rel="noopener noreferrer"&gt;github.com/rootprint/rootprint&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Docs: &lt;a href="https://docs.rootprint.io" rel="noopener noreferrer"&gt;docs.rootprint.io&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Thanks for reading.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>devops</category>
      <category>monitoring</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
