📄️ Backing Up LME Logs
Logging Made Easy (LME) uses built-in Elastic features to back up logs. By default, Elasticsearch supports backing up to filesystems. This is the only supported method in LME. While other backup destinations exist, they require plugins that are not currently supported by LME.
📄️ Certificates
The Logging Made Easy (LME) installation uses multiple Transport Layer Security (TLS) certificates to protect communications between its services and components. These certificates also secure the connection between Elasticsearch and Kibana.
📄️ ElastAlert2 Rule Writing
This page explains how to write and implement alert rules using ElastAlert2, enabling real-time notifications for detections and alerts triggered by Elasticsearch and Wazuh.
📄️ Estimating Data Storage Requirements
Storage needs for Logging Made Easy (LME) vary based on deployment specifics such as the number of agents, the volume and frequency of log generation, and the retention policy applied. The estimates below provide a general guideline based on internal testing and typical usage patterns.
📄️ Elasticsearch Index Lifecycle Management
This page explains how Elasticsearch uses Index Lifecycle Management (ILM) to manage data over time. ILM helps control index storage costs and performance by automatically transitioning data through different phases based on age and usage.
📄️ Podman Volume Management
Overview
📄️ Upgrading
Download Latest Logging Made Easy (LME) Version
📄️ Wazuh Configuration Management
Managing the Wazuh Configuration File
📄️ SBOM Generation
Introduction
📄️ Adding the Wazuh Vulnerability Index in Kibana
Use the steps below to create a new data view for the Wazuh vulnerability index within Kibana.
📄️ Encryption At Rest
To protect data by Elastic Cloud Enterprise, encryption at rest must be configured with disk-level encryption (e.g., dm-crypt). Elastic Cloud Enterprise does not support encryption at rest out of the box. Instead, disk-level encryption (e.g., dm-crypt) must be manually configured on underlying hosts.