Bug 722584

Sorry this is so late, it kinda slipped my mind that I had to write this up for you.

A lot of this goes away; it's a significantly thinner UI now and you've covered a lot of it already.

Previously, there were two commands: one user-readable and one programmatic. The thing is, most of the user-readable stuff has been moved into the synchronization screen. That shows the results of the most recent repo and CDS syncs, as well as if the CDS is up or not.

So if you want to treat this in terms of a migration from the 1.2 monitoring docs to 2.0, you can mention that all the user-readable stuff has been moved and covered in Chapter 9.

The programmatic interface is simpler now too. The user calls a command on the rhui-manager. The exit code from that command indicates the health of the 

=====================
$ rhui-manager --username admin --password admin status

$ echo $?
0
=====================

Users should automate running that command and inspecting the exit code to determine if the RHUI is running correctly or not.

Remove the list of exit code translations, they aren't valid anymore. It's zero = happy, non-zero = someone gets a text message at the wee hours of the morning.

Again if you want to talk in terms of migration from 1.2 to 2.0, there's no timestamp field anymore since you're running the command on your own. Previously it was run from a cron job.

Also, you might want to mention that they really should use the "--username" and "--password" flags as indicated in the screenshot above. This will bypass the authentication certificate, which is only valid for a week at which point they'd need to log in again. So rather than having to keep updating that cert on their own, they can just pass the credentials every time and bypass it entirely.

(let me know if that last paragraph wasn't clear, I'm having trouble thinking straight today)