Adding a section on how to get the controller logs.

[mbruzek]

Addressing #1060. This information was not obvious to me. The core developers shared this with me and I wanted to make sure we had it documented.

[AdamIsrael]

"the the" -> "the"

"In Juju 2.0+" -> "Beginning with Juju 2.0,"

[mbruzek]

I am embarrassed, thank you for finding these errors.

[AdamIsrael]

Maybe add how to read the logs, i.e., tail -f /var/log/juju/blah, after sshing to the machine.

[mbruzek]

@AdamIsrael the tail command is why you are there in the first place (because you missed the juju debug-log in the first place)! I would resist telling someone what to do with the log files because there are so many different ways and reasons to be viewing the logs (more|less|grep|vi|nano|emacs).

[evilnick]

Probably also worth referencing the general logging page, which already documents how to retrieve controller logs amongst other things

../troubleshooting-logs.md

[mbruzek]

@AdamIsrael and @evilnick thanks for the review. I have addressed your comments in the latest commit. Please let me know if you find anything else.

[chuckbutler]

+1 LGTM