Added cluster.name to monitoring index #377
Merged
Conversation
This file contains 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
added 5 commits
April 17, 2018 09:21
|
LGTM! Now we will properly filter clusters in our monitoring visualization! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello team, this pull request ables the App to store the
cluster.nameproperty on the monitoring daily index. Assuming the agent from the/agentsrequest comes with the field{ cluster: { name: 'wazuh-cluster-01' } }we'll store it as it. If the agent doesn't come with that field, we'll store it as{ cluster: { name: 'disabled' } }. On the other hand, whenever we are on a non-cluster environment we'll still able to know it from the.wazuhindex like on the other app packages.This PR solves #375
Best,
Jesús