Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.16](backport #4468) Update Logs Explorer docs with new summary column #4489

Merged
merged 2 commits into from
Nov 6, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Nov 6, 2024

Description

Adding the summary column removed the smart fields (except the actions smart field). I've removed the smart fields info from the docs. If we decided to cover the summary column, it should probably be in the discover docs as it applies to both Logs Explorer and Discover and we already defer to the Discover docs for most of the documents table.

I've also updated the screenshots to show the summary column.

Documentation sets edited in this PR

Check all that apply.

  • Stateful (docs/en/observability/*)
  • Serverless (docs/en/serverless/*)
  • Integrations Developer Guide (docs/en/integrations/*)
  • None of the above

Related issue

Closes #4317

Checklist

  • Product/Engineering Review
  • Writer Review

Follow-up tasks

Select one.

  • This PR does not need to be ported to another doc set because:
    • The concepts in this PR only apply to one doc set (serverless or stateful)
    • The PR contains edits to both doc sets (serverless and stateful)
  • This PR needs to be ported to another doc set:
    • Port to stateful docs: <link to PR or tracking issue>
    • Port to serverless docs: <link to PR or tracking issue>

This is an automatic backport of pull request #4468 done by [Mergify](https://mergify.com).

(cherry picked from commit bc7c5be)

# Conflicts:
#	docs/en/serverless/images/log-explorer.png
#	docs/en/serverless/images/log-menu.png
#	docs/en/serverless/logging/view-and-monitor-logs.asciidoc
@mergify mergify bot requested a review from a team as a code owner November 6, 2024 19:28
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Nov 6, 2024
Copy link
Contributor Author

mergify bot commented Nov 6, 2024

Cherry-pick of bc7c5be has failed:

On branch mergify/bp/8.16/pr-4468
Your branch is up to date with 'origin/8.16'.

You are currently cherry-picking commit bc7c5be7.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   docs/en/observability/explore-logs.asciidoc
	modified:   docs/en/observability/images/log-explorer.png
	modified:   docs/en/observability/images/log-menu.png

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/en/serverless/images/log-explorer.png
	deleted by us:   docs/en/serverless/images/log-menu.png
	deleted by us:   docs/en/serverless/logging/view-and-monitor-logs.asciidoc

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

Copy link
Contributor

github-actions bot commented Nov 6, 2024

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@mdbirnstiehl mdbirnstiehl merged commit f5e7415 into 8.16 Nov 6, 2024
3 checks passed
@mdbirnstiehl mdbirnstiehl deleted the mergify/bp/8.16/pr-4468 branch November 6, 2024 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport conflicts There is a conflict in the backported pull request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant