This functionality is experimental and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but experimental features are not subject to the support SLA of official GA features.

« Settings for legacy internal collection Secure communication with Elasticsearch »

›

Secure Journalbeat

edit

IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Secure Journalbeat

edit

The following topics provide information about securing the Journalbeat process and securing communication between Journalbeat and other products in the Elastic stack:

Secure communication with Elasticsearch
Secure communication with Logstash
Use security features
Use Linux Secure Computing Mode (seccomp)

« Settings for legacy internal collection Secure communication with Elasticsearch »