You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With #17974 we introduced a config setting to enable ECS logging. This adds the MVP of ECS keys to any log lines. It was only the first step towards ECS logging and requires more work in libbeat and other beats to be fully compliant with ECS. Enabling logging.ecs changes the log format, and therefore is opt-in. When holding a logger instance one needs to be able to distinguish whether or not ECS logging is enabled to avoid conflicting changes, e.g. changing a log key from url: "xxx" (string) to url.original: "xxx" }(url being an object).
The text was updated successfully, but these errors were encountered:
Derive information whether ECS logging is enabled from any
logger instance as requirement to make decisions about logging keys to
use.
closeselastic#18815
With #17974 we introduced a config setting to enable ECS logging. This adds the MVP of ECS keys to any log lines. It was only the first step towards ECS logging and requires more work in libbeat and other beats to be fully compliant with ECS. Enabling
logging.ecs
changes the log format, and therefore is opt-in. When holding a logger instance one needs to be able to distinguish whether or not ECS logging is enabled to avoid conflicting changes, e.g. changing a log key fromurl: "xxx"
(string) tourl.original: "xxx" }
(url being an object).The text was updated successfully, but these errors were encountered: