-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Release notes for 9.2.0 #18313
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
base: 9.2
Are you sure you want to change the base?
Release notes for 9.2.0 #18313
Conversation
🔍 Preview links for changed docs |
PRs with RN sections:
PRs that look like maybe might be of note:
The main ones I'm curous about are the metrics around pq (epecially around compression) and the user defined metrics. |
docs/release-notes/index.md
Outdated
|
||
**Elastic_integration Filter - 9.2.0** | ||
|
||
404: Not Found |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Proposed fix #18315
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to see a little more detail in a few of these areas
* Logging improvement while handling exceptions in the pipeline, ensuring that chained exceptions propagate enough information to be actionable. [#17935](https://github.com/elastic/logstash/pull/17935) | ||
* [Support for using ES|QL queries](https://github.com/logstash-plugins/logstash-filter-elasticsearch/pull/194) in the Elasticsearch filter to add improved flexibility when ingesting data from Elasticsearch is now in Technical Preview. | ||
* Gauge type metrics, such as current and peak connection counts of Elastic Agent, are now available in the `_node/stats` API response when the `vertices=true` parameter is included. These metrics are particularly useful for monitoring {{ls}} plugin activity on the {{ls}} Integration dashboards [#18090](https://github.com/elastic/logstash/pull/18090) | ||
* Improve logstash release artifacts file metadata: mtime is preserved when buiilding tar archives [#18091](https://github.com/elastic/logstash/pull/18091) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we could add some explanation as to what this means (no more epoch timestamps for artifacts)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I could, but one thing to note here is that this is a copied RN from a 9.1.z patch release. If we do this we would probably want to do it everywhere?
docs/release-notes/index.md
Outdated
|
||
##### Event compression for persisted queue | ||
|
||
* Support for event compression in the persisted queue, controlled by the per-pipeline `queue.compression` setting, which defaults to `none` [#18121](https://github.com/elastic/logstash/pull/18121) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yaauie Can you add detail here, and add color about the (backwards compatible) reduction in queue size without compression, and the new compression capabilities (and restrictions)
* Added metrics for pq compression [#18227](https://github.com/elastic/logstash/pull/18227) | ||
|
||
##### Batch performance metrics | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In Andrea's absence, I can add a little info here to as to what we are providing, and how users can get to the metrics
docs/release-notes/index.md
Outdated
|
||
**Elastic_integration Filter - 9.2.0** | ||
|
||
404: Not Found |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we might need a few more details here... ;)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep, I proposed a bugfix #18315 and updated with the output based on running that script with the proposed patch.
Add changes based on generated message with #18315
Co-authored-by: Rob Bavey <rob.bavey@elastic.co>
Co-authored-by: Rye Biesemeyer <yaauie@users.noreply.github.com>
No description provided.