debug log misses data

[Ian Booth]

debug log can fail to report all records. But you can ssh into the controller and look at logsink.log or machine-0.log and see the records are there. I haven't found the trigger for this behaviour - it doesn't seem to always occur.

[Tim Penhey (thumper)]

If we can't action it immediately, it shouldn't be critical.

[Tim Penhey (thumper)]

Logs only make it into debug-log if the agent is connected. Have you confirmed that this isn't the problem?

[Ian Booth (wallyworld)]

Yes, the log entries make it to logsink.log and machine-0.log on the controller. Just not to debug-log output.

[Tim Penhey (thumper)]

If you re-run debug-log do you see them then?

[Ian Booth (wallyworld)]

Not that I recall - pretty sure they are missing

[Tim Penhey (thumper)]

There are other situations where the log messages don't get from the agents to the API server.

If the agent loses connectivity to the controller it batches up the log messages in memory. If the agent is restarted, or crashes, those logs are not sent to the controller.

[Launchpad Janitor (janitor)]

[Expired for juju because there has been no activity for 60 days.]