mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-24 23:27:25 -04:00
e00b354c26
With https://github.com/elastic/stack-docs/pull/2495 merged, we no longer reuse breaking changes in the Stack Install/Upgrade guide. This removes the related `notable-breaking-changes[]` tags from the 8.9+ docs and updates the RN generator template. ## Out of scope With the removal of these tags, we may no longer need the `notable` property for changelog entries and can likely simplify the logic for the [BreakingChangesGenerator](https://github.com/elastic/elasticsearch/blob/main/build-tools-internal/src/main/java/org/elasticsearch/gradle/internal/release/BreakingChangesGenerator.java). Updating those files is outside the scope of this PR. I've opened https://github.com/elastic/elasticsearch/issues/98145 to track that work.
53 lines
1.5 KiB
Text
53 lines
1.5 KiB
Text
[discrete]
|
|
[[breaking_80_logging_changes]]
|
|
==== Logging changes
|
|
|
|
.{es} JSON logs now comply with ECS.
|
|
[%collapsible]
|
|
====
|
|
*Details* +
|
|
{es}'s {ref}/logging.html[JSON logs] now comply with the
|
|
{ecs-ref}/index.html[Elastic Common Schema (ECS)]. Previously, {es}'s JSON logs
|
|
used a custom schema.
|
|
|
|
*Impact* +
|
|
If your application parses {es}'s JSON logs, update it to support the new ECS
|
|
format.
|
|
====
|
|
|
|
.{es} no longer emits deprecation logs or slow logs in plaintext.
|
|
[%collapsible]
|
|
====
|
|
*Details* +
|
|
{es} no longer emits a plaintext version of the following logs:
|
|
|
|
* Deprecation logs
|
|
* Indexing slow logs
|
|
* Search slow logs
|
|
|
|
These logs are now only available in JSON.
|
|
|
|
Server logs are still available in both a JSON and plaintext format.
|
|
|
|
*Impact* +
|
|
If your application parses {es}'s plaintext logs, update it to use the new ECS
|
|
JSON logs.
|
|
====
|
|
|
|
[[audit-logs-are-rolled-over-and-archived-by-size]]
|
|
.Audit logs are rolled-over and archived by size.
|
|
[%collapsible]
|
|
====
|
|
*Details* +
|
|
In addition to the existing daily rollover, the security audit logs are
|
|
now rolled-over by disk size limit as well. Moreover, the rolled-over logs
|
|
are also gzip compressed.
|
|
|
|
*Impact* +
|
|
The names of rolled over audit log files (but not the name of the current log)
|
|
have changed.
|
|
If you've set up automated tools to consume these files, you must configure them
|
|
to use the new names and to possibly account for `gzip` archives instead of
|
|
plain text. The Docker build of {es} is not affected because it logs on `stdout`,
|
|
where rollover is not performed.
|
|
====
|