Access the dashboard

Juju has a dashboard available to help with the tasks of managing and monitoring your Juju environment. The dashboard comes with every controller providing the controller was not created with the --no-gui option.

This page covers the following topics:

Dashboard set up

To view the URL and login credentials for the dashboard, use the following command:

juju dashboard

This will produce output similar to the following:

Dashboard for controller "my-controller is enabled at:

Your login credential is:

username: admin

password: 1d191f0ef257a3fc3af6be0814f6f1b0

If you don’t want to copy and paste the URL manually, typing juju dashboard --browser will open the link in your default browser automatically.

Your browser will give you an error message when you open the URL warning that the site certificate should not be trusted. This is because Juju is generating a self-signed SSL certificate rather than one from a certificate authority (CA). Depending on your browser, choose to manually proceed or add an exception to continue past the browser’s error page.

After opening the Juju dashboard URL, you are greeted with the login window, where you will have to provide the credentials to access the model. These credentials can be copied from the output of juju dashboard.

If you’d rather not have your login credentials displayed in the output of juju dashboard, they can be suppressed by adding the --hide-credential argument.

Upgrading Juju Dashboard

The upgrade-dashboard command downloads the latest published dashboard from the streams and replaces the one on the controller. To verify which versions of the dashboard are available before the upgrade, try juju upgrade-dashboard --list.

If you want to upgrade (or downgrade) to a specific version of the dashboard, provide the revision as a parameter to the upgrade-dashboard command, where the revision listed by the juju upgrade-dashboard --list. For example:

juju upgrade-dashboard 0.2.0

If you’d like to try a version of the dashboard that has not been published in the streams and is not listed yet, you are able to provide the blob either from a charmed operator or from the manually built dashboard. For example:

juju upgrade-dashboard /path/to/release.tar.bz2

In order to upgrade the dashboard, you’ll have to have proper access rights to the controller. When an administrator upgrades the dashboard, the users will have to reload the open sessions in the browser.

I just discovered a Settings for the Dashboard to disable analytics. What analytics is this? What information it collects? Where it sends to? Why it is enabled by default?

The analytics in question here are for google analytics. When a feature is opened it sends a ping that says something like { category: "config", action: "opened" } We use it to get an idea if users are using the features we implement. It’s disabled if you use a system to block GA like uBlock Origin or if you toggle that switch off.

1 Like