Gjallar brings zero-dependency monitoring to Go

Developer brvier has released Gjallar, a lightweight monitoring service designed to provide essential visibility without the complexity of modern distributed platforms. Built as a single static Go binary, the tool aims to solve the common friction of deploying monitoring agents in restricted environments.

Constructed from approximately 3,400 lines of Go and licensed under MIT, Gjallar operates using a single YAML configuration file and one SQLite database for state management. A primary technical achievement is the complete elimination of CGO (CGO_ENABLED=0), allowing for zero-dependency deployment. This is achieved through pure-Go replacements, including pgx for PostgreSQL, go-ora for Oracle, pro-bing for ICMP, and modernc.org/sqlite for SQLite. Notably, the use of go-ora allows the tool to query Oracle databases without requiring the installation of the Oracle Instant Client.

The push for simplicity

The project was born from a need to monitor a heterogeneous fleet—including HTTP, PostgreSQL, Oracle, Redis, Elasticsearch, ICMP, and Prometheus—without the burden of operating a full-scale monitoring stack. The author noted that platforms like Prometheus and Grafana can evolve into distributed systems that eventually require their own dedicated monitoring, creating a cycle of increasing complexity.

By focusing on a "back-to-basics" approach, Gjallar ensures that the entire system remains maintainable. As brvier put it: "A tool whose whole state fits in one SQLite file and whose whole behaviour fits in one YAML file is a tool you still understand at 3 a.m., eighteen months after you wrote it."

Engineering for reliability

Under the hood, Gjallar employs a lock-free alert pipeline. In this architecture, one goroutine is assigned per monitor to send results to a single consumer goroutine, which then manages the system state and handles all SQLite writes. To ensure high availability during updates, the tool supports hot reloading of its configuration via SIGHUP, performing full validation of the new configuration before applying any changes. For visibility, it includes a status page featuring history that is refreshed via HTMX.

Industry implications

This approach highlights a growing trend toward "boring technology" in infrastructure tooling, where maintainability and ease of deployment are prioritized over an exhaustive feature set. By creating an "scp-able" binary that removes external library dependencies, Gjallar reduces the operational friction typically associated with monitoring legacy or minimal environments. It serves as a case study in how reducing the surface area of a tool can increase its long-term reliability.

What to watch

As the project moves forward, the primary focus remains on maintaining the minimalist footprint while supporting a diverse range of targets. While the current implementation solves specific pain points regarding Oracle and CGO dependencies, the long-term utility of the tool will depend on whether its limited feature set remains sufficient for users who are actively moving away from the complexity of distributed monitoring ecosystems.