A single console for all your supervision
A multi-backend web interface for Nagios, Icinga, Naemon, and Shinken, installed and maintained by DINAO. Centralize all your monitoring servers on a single console, hosted in France.
What is Thruk?
Thruk is a multi-backend web supervision interface for Naemon, Nagios, Icinga, and Shinken, based on the Livestatus API. Designed as a « drop-in » replacement for the original interface, it retains all its functions while adding improvements designed for large-scale installations: better ergonomics and many useful addons.
Written in Perl with the Plack framework and executed as a FastCGI process, Thruk connects to monitoring engines via the Perl Monitoring::Livestatus module. This architecture allows it to operate independently of the supervision server and be installed on a separate host.
Its strength lies in its ability to aggregate multiple Nagios, Icinga, Naemon, or Shinken servers within a single interface, thereby centralizing all monitoring of an infrastructure. Authentication is delegated to the web server (mod_auth_basic, LDAP, MySQL…), facilitating integration into a corporate directory.
Host Thruk at DINAO
Resource tiers compatible with Thruk prerequisites (minimum 1 vCPU / 1 Go / 5 Go). Hosted in France, fully managed.
- 1 dedicated vCPU
- 2 Go RAM
- 20 GB NVMe
- Daily backups
- Managed & monitored by DINAO
- 2 dedicated vCPU
- 4 Go RAM
- 40 GB NVMe
- Daily backups
- Managed & monitored by DINAO
- 4 dedicated vCPU
- 8 Go RAM
- 80 GB NVMe
- Daily backups
- Managed & monitored by DINAO
- 8 dedicated vCPU
- 16 Go RAM
- 160 GB NVMe
- Daily backups
- Managed & monitored by DINAO
Technical details
You might be wondering…
Does Thruk replace Nagios?
No, Thruk is a web interface that connects to your existing Nagios, Icinga, Naemon, or Shinken servers via Livestatus. It modernizes and centralizes their viewing without replacing the supervision engine.
Can I connect multiple monitoring servers?
Yes. This is Thruk's main advantage: aggregating multiple backends on a single interface, ideal for centralizing monitoring across multiple sites or teams.
How is authentication handled?
Authentication is handled at the web server level (LDAP, Active Directory, basic auth…). DINAO configures the method best suited to your organization.
Are technical skills required?
Daily use is done via the web interface. DINAO manages installation, connection to Livestatus backends, security, and updates.
Does my supervision data remain private?
Yes. The console and its data remain on your instance hosted in France. No monitoring telemetry is transmitted to a third party.
