-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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.
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
[Logging] Support for ECS and custom event tags #46119
Comments
Pinging @elastic/es-core-infra |
changes between current format and ECS Additional fields from ES are not a problem, but could be migrated. we would map these to the custom fields. The changes from the fields above would apply what other fields should we add to our logs to make it more functional once parsed? additional fields added by ECSLayout ECSLayout defines exceptions these way. considering moving markers to json fields |
cc: @elastic/stack-monitoring for visibility |
ECS specifies
|
sample ECS json log line
with exception
|
closed by #47105 |
To support Elastic Common Schema, some of the fields would have to be renamed and some possibly added to Elasticsearch JSON logs.
There is a project containing a log4j2 layout that can be used to make this task easier. https://github.com/elastic/java-ecs-logging
Also since this would require new fields being added, we should consider making it easier to add more fields in the future to support "special log events" that would make monitoring of Elasticsearch easier. Example would be a special log event when cluster state changes. Draft was done here #44336
The text was updated successfully, but these errors were encountered: