Repository navigation
[Monitoring] Remove node_resolver Setting - #21181
Merged
pickypg merged 3 commits intoJul 27, 2018
Merged
Conversation
This is a breaking change that removes the `xpack.monitoring.node_resolver` setting. This setting was deprecated in 5.6, and in 6.1 the setting was limited to `uuid` explicitly. Beginning in 7.0, after this is merged, the setting will no longer exist.
lcawl
reviewed
Jul 24, 2018
| === Deprecated kibana.yml setting `xpack.monitoring.node_resolver` has been removed | ||
| *Details:* This setting has been deprecated since 5.6, when it was explicitly recommended to use `uuid` as its value. | ||
|
|
||
| *Impact:* The setting is no longer needed to use the best way to determine node uniqueness, its persistent UUID. No newline at end of file |
Contributor
There was a problem hiding this comment.
It might be nice to clarify the impact with something like this (stolen from https://www.elastic.co/guide/en/kibana/6.3/xpack-monitoring.html):
This setting is no longer necessary. If you enable {monitoring} across the Elastic Stack, a monitoring agent runs on each Elasticsearch node, Logstash node, Kibana instance, and Beat to collect and index metrics. Each node and instance is considered unique based on its persistent UUID, which is written to the path.data directory when the node or instance starts.
lcawl
approved these changes
Jul 24, 2018
lcawl
left a comment
Contributor
There was a problem hiding this comment.
The documentation changes LGTM
Contributor
💚 Build Succeeded |
patrykkopycinski
pushed a commit
to patrykkopycinski/kibana
that referenced
this pull request
May 6, 2026
This is a breaking change that removes the `xpack.monitoring.node_resolver` setting. This setting was deprecated in 5.6, and in 6.1 the setting was limited to `uuid` explicitly. Beginning in 7.0, after this is merged, the setting will no longer exist.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a breaking change that removes the
xpack.monitoring.node_resolversetting. This setting was deprecated in 5.6, and in 6.1 the setting was limited touuidexplicitly. Beginning in 7.0, after this is merged, the setting will no longer exist.Closes #21095