juju debug-log help needs to be updated
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Jon Seager |
Bug Description
Juju 2.2.2
The examples section contains
-----
Examples:
Exclude all machine 0 messages; show a maximum of 100 lines; and continue to
append filtered messages:
juju debug-log --exclude machine-0 --lines 100
Include only unit mysql/0 messages; show a maximum of 50 lines; and then
exit:
juju debug-log -T --include unit-mysql-0 --lines 50
Show all messages from unit apache2/3 or machine 1 and then exit:
juju debug-log -T --replay --include unit-apache2-3 --include machine-1
Show all juju.worker.uniter logging module messages that are also unit
wordpress/0 messages, and then show any new log messages which match the
filter:
juju debug-log --replay
--include unit-wordpress-0
Show all messages from the juju.worker.uniter module, except those sent from
machine-3 or machine-4, and then stop:
juju debug-log --replay --no-tail
--exclude machine-3 \
--exclude machine-4
----
However the -T flag isn't supported any longer. It appears that it's supposed to imply --no-tail
additionally, the current version supports the same unit syntax as the rest of the juju unit commands so `unit-worpress-0` can also be expressed as `worpress/0`
description: | updated |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: helpdocs usability |
tags: |
added: helptext removed: helpdocs |
Changed in juju: | |
milestone: | none → 2.9.31 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
milestone: | 2.9.31 → 2.9.30 |
milestone: | 2.9.30 → 2.9.31 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
https:/ /github. com/juju/ juju/pull/ 14054