$ juju version
2.9.31-ubuntu-amd64
Although juju status accepts "kubeflow-dashboard/0" as a selector. debug-log command doesn't print anything if "kubeflow-dashboard/0" is used as a selector.
$ juju debug-log -n5 --no-tail -i kubeflow-dashboard/0
-> empty
$ juju debug-log -n5 --no-tail -i kubeflow-dashboard
application-kubeflow-dashboard: 05:03:51 INFO juju.worker.caasoperator.uniter.kubeflow-dashboard/0.operation ran "update-status" hook (via hook dispatching script: dispatch)
application-kubeflow-dashboard: 05:08:03 INFO juju.worker.caasoperator.uniter.kubeflow-dashboard/0.operation ran "update-status" hook (via hook dispatching script: dispatch)
application-kubeflow-dashboard: 05:12:13 INFO juju.worker.caasoperator.uniter.kubeflow-dashboard/0.operation ran "update-status" hook (via hook dispatching script: dispatch)
application-kubeflow-dashboard: 05:18:05 INFO juju.worker.caasoperator.uniter.kubeflow-dashboard/0.operation ran "update-status" hook (via hook dispatching script: dispatch)
application-kubeflow-dashboard: 05:22:25 INFO juju.worker.caasoperator.uniter.kubeflow-dashboard/0.operation ran "update-status" hook (via hook dispatching script: dispatch)
-> print entries including kubeflow-dashboard/0
$ juju status kubeflow-dashboard/0
Model Controller Cloud/Region Version SLA Timestamp
kubeflow microk8s-localhost microk8s/localhost 2.9.31 unsupported 05:20:45Z
App Version Status Scale Charm Channel Rev Address Exposed Message
kubeflow-dashboard res:oci-image@858a90f active 1 kubeflow-dashboard stable 64 10.152.183.201 no
Unit Workload Agent Address Ports Message
kubeflow-dashboard/0* active idle 10.1.60.53 8082/TCP
