[Log Explorer] Show message column by default

[weltenwort]

📓 Summary

For time-based dataviews Discover shows the timestamp field and a mixed "document" field by default. In the log-explorer profile we want to show the timestamp and the message field by default when the user selects a dataset.

• 🛑 blocked by: [Logs+] Implement Logs Dataset selector #159907

✔️ Acceptance criteria

• When the user navigates to Discover with the log-explorer profile...
  • if the URL state is empty, the columns are initialized as
    • the timestamp field of the dataview
    • the field message
  • if the URL state is pre-populated but the columns state is an empty list, the columns are initialized as
    • the timestamp field of the dataview
    • the field message
  • if the URL state is pre-populated and the columns state has content, they are restored from the URL
• When the user selects a dataset in the dataset selector and the columns application state is an empty list, the columns are initialized as
  • the timestamp field of the dataview
  • the field message
• When the user selects a dataset in the dataset selector and the columns application state has content, the columns are kept as they were before

💡 Implementation hints

• This is an intermediate step towards supporting full curation of the columns via packaged or generated saved searches.

[elasticmachine]

Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI)

[tonyghiani]

💡 Implementation hint

Doing some attempt while waiting on the blocked task, should be achievable with a call to

stateContainer.appState.update({ columns: [TIMESTAMP_FIELD, MESSAGE_FIELD] });

[tonyghiani]

@weltenwort regarding some additional acceptance criteria for this task, what do you think about:

• When the user lands on the log-explorer profile...
  • if the URL state is empty, should initialize the columns selection to @timestamp and message.
  • if the URL state is pre-populated...
    • in case the columns state is an empty list, should initialize the columns selection to @timestamp and message.
    • in case the columns has content, should restore the existing selection.
• When the user selects a dataset in the dataset selector...
  • in case the columns state is an empty list, should initialize the columns selection to @timestamp and message.
  • in case the columns has content, should restore the existing selection.

The user could update the columns selection while navigating the datasets, so I thought would be correct to keep their selection if they apply a custom one, so that it can be restored from the URL too. Does it sound correct?

[weltenwort]

Yes, these look good 👍 thank you!

[weltenwort]

ℹ️ I've updated the ACs with your proposed content (just phrased a bit differently).