The Juju dashboard
Note: a small number of dashboard features (e.g. the web CLI) are dependent on the deployment environment. These are noted as “requirements” in this document.
Juju Dashboard aims to expose Juju environments, providing at-scale management, status and collaboration features not found in the Juju CLI. It is intended to supplement the CLI experience with aggregate views and at a glance health checks. In particular, it provides a quick way to view details for all the entities in your Juju environment (models, controllers, etc.), and in places also provides functionality related to the ongoing maintenance of your estate.
juju v.3.0, the Juju dashboard was automatically deployed with every controller, but from
juju v.3.0 it needs to be set up by deploying the
juju-dashboard-k8s charm in the controller model and integrating it with the
- Models view
- Model details view
- Controllers view
- Model access management
- Running actions from the dashboard
- Common questions and problems
The models view lists all the models associated with the connected controllers that you have some form of access to. The list displays the models across clouds. This allows you to access the health of all the models at a glance, surfacing any relevant errors so you can quickly investigate what has happened.
The list can be grouped by status, cloud, or owner. The default grouping is by status, which brings the models with errors to the top of the list.
The dashboard provides comprehensive search and filter functionality. This allows you to perform complex filtering of the models list which can be shared via the URL.
The purpose of the model details view is to provide a list of the applications running on that model. In this view you can also manage access to the model.
This view can be accessed by navigating to the model list (click “Models” in the side navigation) and then clicking on the title of a model in the list.
The unit view scopes your list of units to the model and application you are inspecting. This view will give fine-grained information about the status of each unit and information on this public availability.
Requirements: this view is only available for a machine charm environment and will not be visible when deployed on Kubernetes.
The machine view displays all machine instances managed by Juju. It all also displays the machine status and any applications running on the machines.
The machine details view displays all machine information for the selected machine. Machine details is accessible via an application deployed to a model. The machine details view shows a list of the units running on the machine and the applications associated with the units.
The integrations view (sometimes called relations) displays the information about each integration in a model. This view is accessible from the model details view as an option in the tabbed navigation at the top of the page.
This view provides information about each integration and acts as an at a glance overview of the health of your models relations and a status to help you debug any issues.
Applications can be configured from the dashboard. Navigate to an application details page and click the ‘Configure’ button on the left hand side and you will be shown the configuration panel.
By clicking on a configuration option you can see the description for that option that has been provided by the charm maintainer.
Requirements: the web CLI is only available when the dashboard is deployed on a local controller and is not available when using JAAS.
The dashboard provides a way to run Juju CLI commands from the web interface. For full details see the web CLI docs.
The controllers view offers a top level view, monitoring across different controllers, and the possibility to add, edit, and manage controllers. It displays a set of aggregate charts to represent the status of the controllers that have been added to the dashboard. It also displays a table listing each controller and the usage of each entity hosted by the controller.
In addition to the controllers that are returned by the Juju deployment you can register additional controllers in the dashboard. The dashboard will then allow you to see aggregate controller data and allow you to view and manage your models and users across all controllers.
This allows users of JAAS to register additional self-bootstrapped controllers into the same dashboard. It also allows users who manage multiple self-bootstrapped controllers the ability to view all of those controllers and their models in a single dashboard.
If you have admin rights on a model, the dashboard allows you to add, remove, or modify other users’ access to the model. Once model access has been granted, the model will automatically appear in that user’s model list.
To add a user, enter the username of the person you want to grant access too. Then select the permission level you would like to grant. Finally, click the “Add user” button.
When using an external authentication provider the user domain will need to be included in the format
JAAS uses the Ubuntu SSO provider and to allow access to other users you can use the format
If you have write or admin permissions on a model, you can trigger any available action the charmed application provides. If the action requires options, the UI will provide these as a form with help text to describe the options and the default values.
Actions are run on the unit level. To view and trigger actions, visit an application’s unit view, select the units you would like the action to run on, and click the Run actions button. This will bring up a side panel with a list of available actions. Find and select the action you wish to run, provide any necessary options, and click “Run action”.
You can also run action on units of multiple applications of the same type at once. Navigate to the list of applications in a model and perform a search using the search input in the header.
Tick the applications you want to perform actions on and click the ‘Run action’ button. If you’ve selected applications with different charm or revision types you’ll need to choose one charm/revision combination to perform the action.
Once an action has been triggered, the action log displays the status and latest result of the action.
Why can’t I access the dashboard?
To be able to access the dashboard that is deployed on a local controller make sure you run the
juju dashboard command from the same computer as your web browser. This will set up a secure proxy to the dashboard.
If you’ve set up a local controller and this is your first time logging in, make sure you’ve set up a password in Juju with
juju change-user-password [your-username]
To make the dashboard available over your network without using the
juju dashboard command you will need to set up a secure proxy.
If you’re trying to access the web CLI on a local controller, make sure there is nothing blocking the model’s
At the time of writing the web CLI is not available on JAAS.
The machine views are only available when using the dashboard with machine charms, and is not available when using a Kubernetes deployment.
Last updated 2 months ago.