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.x] Asset criticality navigation change (backport #5990) #6001

Merged
merged 2 commits into from
Oct 25, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Oct 25, 2024

Resolves #5976 by updating the name of the Asset criticality page to Entity Store.

Previews

ESS: Asset criticality | Bulk assign asset criticality

Serverless: Open the link in this comment, then navigate to Security -> View serverless docs -> Advanced Entity Analytics -> Entity risk scoring -> Asset criticality.


This is an automatic backport of pull request #5990 done by Mergify.

* Asset criticality navigation change

* Typo

(cherry picked from commit d65c95f)

# Conflicts:
#	docs/serverless/advanced-entity-analytics/asset-criticality.mdx
Copy link
Author

mergify bot commented Oct 25, 2024

Cherry-pick of d65c95f has failed:

On branch mergify/bp/8.x/pr-5990
Your branch is up to date with 'origin/8.x'.

You are currently cherry-picking commit d65c95f9.
  (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/advanced-entity-analytics/asset-criticality.asciidoc

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/serverless/advanced-entity-analytics/asset-criticality.mdx

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

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.

@natasha-moore-elastic natasha-moore-elastic merged commit e42653f into 8.x Oct 25, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant