Operators using Sensu 1 needed a shared view of checks and failures across their monitored systems. Uchiwa provided that dashboard, aggregating Sensu instances and offering actions such as silencing selected checks. Uchiwa and Sensu 1 reached end of life together, so replacing the interface also requires understanding the backend monitoring generation. Preserve connections, permissions and operational workflows when moving: showing similar check names in a new UI does not prove that event handling and notifications remain equivalent.
Current guidance
The original Uchiwa project is a Go backend and AngularJS dashboard for Sensu 1. Its upstream README explicitly announces end of life on December 31, 2019 and states that Uchiwa and Sensu 1 are superseded by Sensu Go. The old chart and package repositories should therefore be treated as historical recovery material, not a current monitoring UI recommendation.
An inherited dashboard may aggregate several Sensu datacenters and expose controls for silencing or resolving events. Inventory those connections, user access, filters and operational workflows before replacing it. A new UI displaying checks does not automatically preserve the backend’s event processing, subscriptions, handlers or escalation rules.
Plan the Sensu backend migration using the current vendor guide, then validate the operator experience with representative failures, recoveries and suppressions. Translate authorization deliberately and verify that read-only users cannot perform state-changing actions. Preserve configuration exports and required monitoring history before removing old services. Avoid putting an unsupported dashboard behind a new ingress and assuming the external TLS endpoint resolves the lifecycle problem in the application itself.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
Uchiwa is a simple yet effective open-source dashboard for the Sensu monitoring framework. This chart bootstraps an Uchiwa deployment on a Kubernetes cluster using the Helm package manager.
Multiple Sensu Instances
Uchiwa aggregates the data of all your Sensu instances in order to offer a unified view of your infrastructure. Each instance is represented as a data center and can be easily filtered.
Real-Time
All data is automatically refreshed, at a configurable interval, and does not require a page reload, which makes Uchiwa ready to be displayed on bigger screens.
Silence Checks and Clients
Uchiwa provides an easy mechanism to silence any check or client for a determined or unlimited period of time. Context can be easily added by supplying a reason upon stash creation.
Unified Client View
Uchiwa aggregates all information concerning a specific client within a unique view. Custom content can easily be added to a client or an event through Sensu in order to provide a better context.
Simple Filtering
Uchiwa makes it easy to filter all Sensu data based on any properties, such as a team name or a client subscription. The filtered results can also be shared with a simple link.
Multiple Themes
Two themes are provided with Uchiwa and additional themes can easily be created with Sass stylesheets. Contribute to Uchiwa with yours!
Silencing
Uchiwa provides an easy mechanism to silence any check or client for a determined or unlimited period of time. Context can be easily added by supplying a reason upon stash creation.
Uchiwa High Availability
If you are using Uchiwa built-in authentication and wish to run multiple instances of Uchiwa together, you will need to adjust your configuration.
Uchiwa generates a temporary key during its launch, which is later destroyed once the process is stopped or restarted. This key is used for generating and validating the signatures of the JSON Web Tokens (JWT) for authentication.
This behavior is problematic when multiple instances of Uchiwa are used behind a load balancer or if the Uchiwa process needs to be frequently restarted.
Sources & further reading
Spotted something that needs another look?
Help improve this page →