Can I view logs via the Juju dashboard?

juju
1

Is there any way to view logs (i.e. juju debug-log) via the juju dashboard? If not, would this be a reasonable feature request?

2

Looping in @hatch who’s the main dashboard developer
As far as I’m aware, it’s not supported now but Jeff can comment on future thoughts in that area.
I think the reasoning has been debug-log is more a developer tool (not really an end user / consumer of Juiju thing) and developers prefer the CLI. Plus the CLI is almost always a much better way to access that sort of voluminous info.

3

We’re currently working on adding UI features that are more useful for the long term (day 2 to infinity) operations of your environments. So this is things like:

  • Charm configuration management
  • View/Execute actions
  • Create and consume local and cross-model relations
  • Model sharing and user management.

With that said debug-log support requests have popped up time and time again so it’s definitely on our radar. As @wallyworld said this is typically a feature required by developers of charms and not operators of models but I could potentially see a path where the webcli gains the ability to run debug-log. It does not currently support debug-log.

The webcli is a feature coming with dashboards running in the upcoming Juju 2.9+ that allows you to run a subset (albeit fairly extensive subset) of Juju commands from within the dashboard.

So ultimately yes that’s a reasonable feature request, and you can consider it requested :smile:. We’re always looking for feedback so feel free to post here or create an issue on the Juju Dashboard repo if you have any more ideas.

1 Like
4

Thanks for the feedback, both of you!

If debug-log is intended as a developer tool, is there some other logging mechanism that end users should be using, that I’m just unfamiliar with?

5

I suppose that depends on the kind of logs you’re interested in monitoring.

Everyone has a different workflow but typically you would only be concerned about the charm logs via debug-log when something goes wrong and you have to dig in to find out what happened or you’re actively developing the charm and monitoring its execution.

If you want more long running logs I’d recommend relating your charm to a separate logging system like logstash and monitoring them separately.

Others probably have other opinions so hopefully they will chime in as well :slight_smile: