[DOCS]: Remove Example: Detect threats with EQL from reference #130716
+3
−333
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
charlotte-hoblik
added
>docs
|
Pinging @elastic/es-docs (Team:Docs) |
|
@charlotte-hoblik do you have a redirect pending for this page? |
|
@leemthompo I do not have a redirect set up, I think the issue with the build has been solved by updating the TOC in the repo. |
|
@charlotte-hoblik we would still need to setup a redirect to the docs-content page before merging this change, otherwise google will report 404s on https://www.elastic.co/docs/reference/query-languages/eql/eql-ex-threat-detection |
|
Thank you for clearing this up for me @leemthompo 🙇 I hope I've added the redirect file correctly. Let me know if I need to adjust anything. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removes the
Detect threats with EQLexample from the Elasticsearch reference content as it has been duplicated. The page will stay live in the docs-content repository: https://www.elastic.co/docs/explore-analyze/query-filter/languages/example-detect-threats-with-eqlConnected to: elastic/docs-content#1289