logging-changes.asciidoc 1.5 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
  1. [discrete]
  2. [[breaking_80_logging_changes]]
  3. ==== Logging changes
  4. .{es} JSON logs now comply with ECS.
  5. [%collapsible]
  6. ====
  7. *Details* +
  8. {es}'s {ref}/logging.html[JSON logs] now comply with the
  9. {ecs-ref}/index.html[Elastic Common Schema (ECS)]. Previously, {es}'s JSON logs
  10. used a custom schema.
  11. *Impact* +
  12. If your application parses {es}'s JSON logs, update it to support the new ECS
  13. format.
  14. ====
  15. .{es} no longer emits deprecation logs or slow logs in plaintext.
  16. [%collapsible]
  17. ====
  18. *Details* +
  19. {es} no longer emits a plaintext version of the following logs:
  20. * Deprecation logs
  21. * Indexing slow logs
  22. * Search slow logs
  23. These logs are now only available in JSON.
  24. Server logs are still available in both a JSON and plaintext format.
  25. *Impact* +
  26. If your application parses {es}'s plaintext logs, update it to use the new ECS
  27. JSON logs.
  28. ====
  29. [[audit-logs-are-rolled-over-and-archived-by-size]]
  30. .Audit logs are rolled-over and archived by size.
  31. [%collapsible]
  32. ====
  33. *Details* +
  34. In addition to the existing daily rollover, the security audit logs are
  35. now rolled-over by disk size limit as well. Moreover, the rolled-over logs
  36. are also gzip compressed.
  37. *Impact* +
  38. The names of rolled over audit log files (but not the name of the current log)
  39. have changed.
  40. If you've set up automated tools to consume these files, you must configure them
  41. to use the new names and to possibly account for `gzip` archives instead of
  42. plain text. The Docker build of {es} is not affected because it logs on `stdout`,
  43. where rollover is not performed.
  44. ====