How to filter in juju-debug-log Kubernetes model


#1

Does debug-log filtering in k8s models still work? I’m not getting any sensible result.

merlijn@travers:~$ juju debug-log --replay --no-tail | tail
tracer: set flag endpoint.sse-endpoint.changed.ingress-address
tracer: set flag endpoint.sse-endpoint.changed.private-address
tracer: set flag endpoint.sse-endpoint.joined
tracer: set flag sse-endpoint.consumer.available
application-ep8: 16:52:07 DEBUG unit.ep8/0.juju-log tracer: hooks phase, 0 handlers queued
application-ep8: 16:52:07 DEBUG unit.ep8/0.juju-log tracer>
tracer: main dispatch loop, 1 handlers queued
tracer: ++   queue handler reactive/sse-endpoint.py:28:send_information
application-ep8: 16:52:07 INFO unit.ep8/0.juju-log Invoking reactive handler: reactive/sse-endpoint.py:28:send_information
application-ep8: 16:52:07 INFO juju.worker.uniter.operation ran "update-status" hook
merlijn@travers:~$ juju debug-log --replay --no-tail --include application-ep8 | tail
merlijn@travers:~$ juju debug-log --replay --no-tail --include unit-ep8-0 | tail
merlijn@travers:~$

#2

This does look like a bug.

https://bugs.launchpad.net/juju/+bug/1825439

You can see all known k8s issues here:

https://bugs.launchpad.net/juju/+bugs?field.tag=k8s