github-mirrors/logstash
1
0
Fork 0
mirror of https://github.com/elastic/logstash.git synced 2025-04-24 22:57:16 -04:00
Code Issues Projects Releases Packages Wiki Activity

[Doc]Release notes: Add known issue for monitoring settings (#11816) (#11821)

Browse source 
* Add known issue for monitoring settings

* Incorporate review comments
This commit is contained in:
Karen Metts 2020-04-21 13:42:57 -04:00 • committed by GitHub
parent c0db7f4350
commit 3fbe846b8b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 35 deletions
Download patch file Download diff file Expand all files Collapse all files

45
docs/static/releasenotes.asciidoc vendored
View file

@ -31,43 +31,18 @@ This section summarizes the changes in the following releases:
[[logstash-7-7-0]] [[logstash-7-7-0]]
=== Logstash 7.7.0 Release Notes === Logstash 7.7.0 Release Notes
[float]
[[known-issue-7.7.0]]
==== Known issue
* Monitoring settings. The `xpack.` prefixed monitoring settings were removed
from the `logstash.yml` config template as part of an experimental feature.
Please continue to use the <<monitoring-settings-legacy,monitoring settings>> prefixed
with `xpack.monitoring`.
https://github.com/elastic/logstash/issues/11815[#11815]
==== New features and improvements ==== New features and improvements
===== Improving Stack communication - Monitoring
As the {stack} continues to evolve, improvements across stack components become
necessary to improve performance, internal communication or usability of our
products. {ls} is no different, as we continuously strive to improve its
interaction with the rest of the stack. As such, this release brings
improvements to how Logstash sends monitoring data (from its Internal
Collection) to {es}.
Previous versions of {es} received monitoring data in a Production cluster to
then forward it (internally) to the dedicated Monitoring cluster. Newer versions
improved the process by allowing the data to be sent directly to the Monitoring
cluster instead, in a different data format. Following those changes, Logstash
has now added support to send the monitoring data directly to the Monitoring
cluster, with the caveat that the Production cluster only has to retrieve the
`cluster_uuid`.
https://github.com/elastic/logstash/pull/11106[#11106],
https://github.com/elastic/logstash/pull/11640[#11640],
https://github.com/elastic/logstash/pull/11641[#11641]
Migrating from legacy internal collection to new
<<monitoring-internal-collection,Internal collection>> is straightforward.
** Drop the `xpack.` prefix from your configuration settings.
For example, `xpack.monitoring.enabled` is now `monitoring.enabled`. See
<<monitoring-settings, Monitoring Settings>> for the full list.
** Change the hosts settings and configuration options to point to monitoring
cluster instead of production.
** If you don’t have an Elasticsearch output plugin configured in the pipelines,
add the setting monitoring.cluster_uuid to your logstash.yml.
See <<configuring-logstash, Monitoring Logstash>> for more information
about this and other monitoring options.
===== Improving Logging ===== Improving Logging
Continuing with the Logging improvements made in the past couple of releases, Continuing with the Logging improvements made in the past couple of releases,