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.

Sign up for GitHub

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

Jump to bottom

merge dev to 2.4 #101

Merged
merged 7 commits into from
May 31, 2024
Merged

merge dev to 2.4 #101

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
b3a54e5
Update docker.rst
fyodorr May 31, 2024
963655f
update firewall
dougburks May 31, 2024
a2e4fe0
Merge pull request #100 from fyodorr/patch-1
dougburks May 31, 2024
6aa95c1
fix formatting
dougburks May 31, 2024
50ca189
update firewall
dougburks May 31, 2024
298972f
show example of notification alerters enabled
jertel May 31, 2024
aaa1b24
update notifications
dougburks May 31, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docker.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ By default, Docker configures its network bridge with an IP address of ``172.17.
Containers
----------

Our Docker containers all belong to a common Docker bridge network, called ``so-elastic-net``. Each container is also aliased, so that communication can occur between the different docker containers using said alias. For example, communication to the ``so-elasticsearch`` container would occur through an alias of ``elasticsearch``.
Our Docker containers all belong to a common Docker bridge network, called ``sobridge``. Each container is also aliased, so that communication can occur between the different docker containers using said alias. For example, communication to the ``so-elasticsearch`` container would occur through an alias of ``elasticsearch``.

You may come across interfaces in ``ifconfig`` with the format ``veth*``. These are the external interfaces for each of the Docker containers. These interfaces correspond to internal Docker container interfaces (within the Docker container itself).

Expand Down
6 changes: 5 additions & 1 deletion firewall.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,9 +64,13 @@ Elastic Agent:
- TCP/8443 (All nodes to Manager) - Elastic Agent binary updates
- TCP/5055 (All nodes to Manager, Fleet nodes, Receiver nodes) - Elastic Agent data

Search nodes from/to Manager:
Elastic cluster nodes (manager and all search nodes) to all other Elastic cluster nodes (manager and all search nodes):

- TCP/9200 - Logstash connecting to :ref:`elasticsearch`
- TCP/9300 - Node-to-node for :ref:`elasticsearch`

Search nodes to Manager:

- TCP/9696 - :ref:`redis`

Elastic Fleet nodes to Manager:
Expand Down
7 changes: 6 additions & 1 deletion notifications.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,12 @@ Once the alerter parameters are configured, as described above, the next step is

Navigate to the :ref:`administration` -> Configuration screen. Next, locate the ``soc -> config -> server -> modules -> elastalertengine`` settings.

In the **Additional Alerters** configuration setting, add the name of each alerter that should be activated, one alerter name per line.
In the **Additional Alerters** configuration setting, add the name of each alerter that should be activated, one alerter name per line. For example, to add both slack and email:

::

slack
email

.. image:: images/config-item-soc-additionalAlerters.png
:target: _images/config-item-soc-additionalAlerters.png
Expand Down
Loading