Option to hide timestamps on console logs page

[JamesNK]

Description

Fixes #5457

Demo:

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Is this introducing a breaking change?
      • Yes
        • Link to aspire-docs issue (please use this breaking-change template):
      • No
        • Link to aspire-docs issue (please use this doc-idea template):
  • No

Microsoft Reviewers: Open in CodeFlow

[samsp-msft]

Cut the date, but keep the time. The dashboard is not typically used to inspect data from long time periods ago, but understanding the delta and frequency of the log messages based on time is important. Showing a long date isn't needed.

[maddymontaquila]

Cut the date, but keep the time. The dashboard is not typically used to inspect data from long time periods ago, but understanding the delta and frequency of the log messages based on time is important. Showing a long date isn't needed.

Ya agree with @samsp-msft here.

However this is implemented should play nicely with what we decide to do in the future if we start saving dashboard UI state for a local user - ie, resizing/hiding/adding columns, details window pane size

[JamesNK]

Today the timestamp matches the ISO 8601 standard. All developers will recognize what it is. I hesitate to change it to just the time, because then it's no longer immediately recognisable as a timestamp.

I also don't want to overload the user with choice. I think the best choices are simple on and off, which means show all (full timestamp) or nothing.

[adamint]

This looks good to me, but a request if possible would be to add a command to toggle UTC/local time

[maddymontaquila]

Today the timestamp matches the ISO 8601 standard. All developers will recognize what it is. I hesitate to change it to just the time, because then it's no longer immediately recognisable as a timestamp.

I also don't want to overload the user with choice. I think the best choices are simple on and off, which means show all (full timestamp) or nothing.

This makes sense. I'd keep it on by default then, but add the option to change it. I think most people are going to expect timestamps like a regular logfile

[JamesNK]

The experience here isn't a log file though, it's console output. A default console doesn't include a timestamp with every line. e.g. Windows command prompt or Windows terminal don't include a timestamp.

[maddymontaquila]

Sure - but we call them "console logs" on the dashboard and I feel like they're spiritually logs. I'm willing to bend if you and others (@leslierichardson95 mainly) feel strongly that it's worth changing the default behavior though

[drewnoakes]

My vote would be to keep timestamps by default. They add a lot of information when looking at logs to understand system behaviour, and if users don't find the option to turn them on then they'll be missing out on that info.

I agree with @samsp-msft that the date could be hidden by default though. I don't think a value like 12:34:56.123 is confusing in a log view. It's pretty obviously a timestamp. The full date could be in a tool tip.

[JamesNK]

PR feedback applied. Seems like consensus is to leave timestamp by default.

Further changes to tweak page can be in follow up PRs.

[JamesNK]

BTW this PR depends on #6819 being merged first.

[JamesNK]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).