Browse and manage Elasticsearch cluster indices, shards, and health through a web browser instead of writing curl commands.
Run Cerebro as a Docker container in front of your Elasticsearch cluster for quick visual administration.
Lock down Cerebro with LDAP authentication so only authorized team members can access the cluster dashboard.
Configure Cerebro to connect to multiple Elasticsearch clusters from a single interface.
Requires Java 11 or newer, Docker is the easiest deployment path, LDAP auth requires environment variables to be configured correctly before startup.
Cerebro is a web-based administration interface for Elasticsearch, an open source search and analytics engine used to store and query large volumes of data. Elasticsearch provides its own APIs but no built-in graphical dashboard for day-to-day management. Cerebro fills that gap by giving administrators a browser-based interface for working with their Elasticsearch clusters. It is released under the MIT license. The tool is built using Scala on the server side, with the Play Framework for the web application layer, AngularJS for the browser interface, and Bootstrap for styling. It requires Java 11 or newer to run. Once started, it is accessible at http://localhost:9000 by default, though both the port and the network address can be changed through command-line flags. Cerebro can be installed in several ways. The simplest is to download a release archive, extract it, and run the startup script included for Linux and macOS or a .bat file for Windows. On Windows, a Chocolatey package is also available that installs it as a Windows service. Docker images are published to Docker Hub for users who prefer containers. For teams that need access control, Cerebro supports LDAP authentication. The LDAP settings are configured through environment variables, covering the server URL, base directory path, user template format, and optional group membership filtering. This is particularly useful when running Cerebro inside Docker, where environment variables can be passed in from a file. Additional settings, such as database configuration and other application-level options, live in a configuration file called conf/application.conf inside the application directory. An alternate configuration file path can be specified at startup using a system property flag.
← lmenezes on gitmyhub — every repo by this author, as a profile.
Verify against the repo before relying on details.