Add log when firing hook
Bug #1452050 reported by
David Britton
on 2015-05-05
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | juju-core |
Undecided
|
Unassigned | ||
Bug Description
When firing a hook, a simple info message of:
Firing Hook: config-changed
Would be much appreciated.
| Ian Booth (wallyworld) wrote : | #1 |
| Ian Booth (wallyworld) wrote : | #2 |
As discussed on IRC, we'll stick with debug for now.
juju status-history is a great way to see the key information for a unit without having to trawl log files
Marking as invalid because the requested functionality is done already in 1.24
| Changed in juju-core: | |
| status: | New → Invalid |
To post a comment you must log in.


This feature is coming in Juju 1.24 - but the logging is done at debug level rather than info.
Whenever the agent or workload status changes, log entries like so are created:
DEBUG juju.worker. uniter. context context.go:230 [AGENT-STATUS] executing running install hook uniter. context context.go:230 [WORKLOAD-STATUS] maintenance installing charm software
DEBUG juju.worker.
The log messages are of the form <status> <message>
I think we should add a ":" between the status and message to aide readability.
[AGENT-STATUS] executing: running install hook
Note that "executing" for agent status will also show running actions and juju-run scripts etc, not just hooks.
Did you want this logged at info rather than debug?