observability plugin - URLs and passwords
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Snap |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
While trying out the observability plugin in 2023.2/edge a few thoughts came to mind.
Its really easy to enable and to retrieve the dashboard-url however I think that users need a bit more information than this to get started with this feature.
Really we should direct them to the catalogue landing page which then has links to grafana, prometheus and alertmanager - users will also need credentials to access some of these services (grafana only right now).
My proposal would be that the dashboard-url plugin command would point users to the catalogue landing page and provide them with any required credentials for access.
Note that this only applies for embedded COS only - remote COS (not yet implemented) would not need to have these features.
| Changed in snap-openstack: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| tags: | added: bseng-1652 |
This issue still applies.
In the document, it still points users to a Juju run command just after a sunbeam command.
Without having `sunbeam observability dashboard-url --creds`, `sunbeam observability credentials` or something like that, UX is not great.
https:/ /microstack. run/docs/ observability# login-grafana- dashboard- 3
$ sunbeam observability dashboard-url 192.168. 151.86/ observability- grafana
http://
$ juju run --model observability grafana/leader get-admin-password
Running operation 3 with 1 task
- task 4 on unit-grafana-0
Waiting for task 4... 192.168. 151.86/ observability- grafana
admin-password: SELjNXo5iSuA
url: http://
$ sunbeam observability -h
Usage: sunbeam observability [OPTIONS] COMMAND [ARGS]...
Manage Observability.
Options:
-h, --help Show this message and exit.
Commands:
dashboard-url Retrieve COS Dashboard URL.