juju status should include a timestamp

[John A Meinel]

In discussing on the mailing list, and looking through various points of feedback, it seems everyone agrees that having a "Time:" field in status is always useful.
It helps to put it in there, so whenever you share status with another person, it gives just a little bit more context about what was going on.

[John A Meinel (jameinel)]

Some question as to whether it should be the client or server timestamp, but as long as we include a complete timestamp with a TZ offset, I think we can just do either.

[Simon Richardson (simonrichardson)]

I have a few questions about which type of output of the bug refers to when considering the status CLI, is it all of the outputs or just tabular? For example, should the output be the first line of the status in tabular mode?

[John A Meinel (jameinel)]

All outputs. It makes the most sense to embed the timestamp as something
like UTC timestamp with timezone offset in the FullStatus output. And then
it gets rendered appropriately in the various outputs.

I probably would have the timestamp rendered the same as "juju debug-log".
I don't remember whether that is exposed in the clients TZ, or the servers
or UTC. (I probably would allow for a '--utc' flag that allows it to be UTC
always.)

That way 'juju debug-log' correlates with 'juju status' timestamps.

On Wed, Apr 25, 2018 at 5:53 PM, Simon Richardson <
<email address hidden>> wrote:

> I have a few questions about which type of output of the bug refers to
> when considering the status CLI, is it all of the outputs or just
> tabular? For example, should the output be the first line of the status
> in tabular mode?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1765404
>
> Title:
> juju status should include a timestamp
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1765404/+subscriptions
>

[Anastasia (anastasia-macmood)]

It looks like this did go into 2.4-beta2 milestone as originally intended. Just this report was not updated.

Related code changes are in https://github.com/juju/juju/pull/8661