[doc] document log sending
@@ -11,6 +11,7 @@ Elastic Java APM Agent provides the following log features:
- <<log-correlation-ids>> : Automatically inject correlation IDs that allow navigation between logs and traces.
- <<log-reformatting>> : Automatically reformat plaintext logs in {ecs-logging-ref}/intro.html[ECS logging] format.
- <<log-error-capturing>> : Automatically captures exceptions for calls like `logger.error("message", exception)`.
+- <<log-sending>> : Automatically send logs to APM Server without filebeat
Those features are part of {observability-guide}/application-logs.html[Application log ingestion strategies].
@@ -63,6 +64,13 @@ As a result, when an exception is reported to the logger:
- An `error.id` is generated and injected into logger MDC for the duration of the logger invocation
- Logger output will contain the `error.id` if the log format allows it (plaintext still requires some configuration)
+[float]
+[[log-sending]]
+=== Log sending (experimental)
+
+The agent can automatically capture and send logs directly to APM Server, which allows to ingest log events without relying on filebeat.
+Log sending is controlled by the <<config-log-sending, `log_sending`>> configuration option and is disabled by default.
+
[float]
[[ecs-logging-service-fields]]
=== ECS Logging Service fields
