-
Notifications
You must be signed in to change notification settings - Fork 107
Network sec file renames xlinks #2047
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
base: network-sec-core
Are you sure you want to change the base?
Conversation
|
|
|
|
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this was resolved. found this changelog entry and corresponding PR
::: | ||
|
||
Once the traffic filter has been created, it needs to be assigned to the deployment from which you’re managing monitors from (the deployment containing the {{es}} cluster where your results need to go). | ||
* `1.2.3.4/32` | ||
* `34.89.99.187/32` | ||
|
||
In ECH, ECE, and {{serverless-short}}, after the IP filter has been created, it needs to be associated with the deployment from which you’re managing monitors from (the deployment containing the {{es}} cluster where your results need to go). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nb: replaced the screenshot with more generic instructions so this page wouldn't only work in the context of elastic cloud
Part of elastic/platform-docs-team#682 Rebrands "traffic filters" to "network security" Depends on the following PRs: * elastic/docs-content#1785 * elastic/docs-content#2047
This PR:
part of https://github.com/elastic/platform-docs-team/issues/682