-
Notifications
You must be signed in to change notification settings - Fork 27
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
Add quick settings view #1107
Merged
Merged
Add quick settings view #1107
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
matiasmoreno876
approved these changes
Sep 1, 2021
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.
LGTM!
gabiwassan
approved these changes
Sep 1, 2021
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.
LGTM
Machi3mfl
reviewed
Sep 1, 2021
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.
CR ✅
LGTM!
frankeros
added a commit
that referenced
this pull request
Sep 14, 2021
* Enhance/show-agents-node-name (#1103) * Add agent's cluster node name on agent's details * Add new column to Agents overview table to show their cluster node name. - New column's visibility can be toggled as any other column. - Found out that there was already some code to display the nodes, but the object holding the data (clusterInfo) returns null. Most probably some change on the API broke this and no one noticed until now. * Fix broken request to fecth cluster info Agents overview controller launched an API request to detect whether Wazuh works on cluster mode or not. It looks like the API endpoints have changed and the requested endpoints does not provide such information anymore. This information is used to generate the search filters for the table, so the broken request resulted on the filtering by node_name tag not showing on the search-bar filters. - Added a new route state resolver to 'agents' view in order to fetch cluster information ('/cluster/status/). modified: SplunkAppForWazuh/appserver/static/js/config/routes/agents-states.js modified: SplunkAppForWazuh/appserver/static/js/controllers/agents/agents/agentsCtrl.js * fix: table in reports show different columns than UI * doc: add changelog Co-authored-by: Franco Charriol <francocharriol@gmail.com> * Take sourcetype filter for internal queries from inputs.conf (#1104) * Added new service sourceTypeStorageService.js * feat: replace all source type in queries with the selected value * doc: add changelog * Added try catch strategy sourceTypeStorageService.js * Add quick settings view (#1107) * feat: add sourcetype as filter * feat: add selectAPI on wz-menu.js * feat: add dropdown constructor * fix: remove this * fix: get apiList * Added modal wazuh api selector * fix: added index and source type selector on menu * fix: missing value * Daft sourcetype and index selectors - buggy * fixed update emitter * fix: remove listeners * fix: remove listeners * Added Index and SourceType selectors * fix: reload page on change * Fixed onchange reload * Fixed unregister to stopListening * fix: reload refresh sourcetype * doc: add changelog * fix: remove comment line Co-authored-by: Federico Rodriguez <federico.rodriguez@wazuh.com> * fix: quick selector throw error * fix: improve exception logging * fix: add missing params Co-authored-by: Álex <alex-r-b@hotmail.com> Co-authored-by: Matias Ezequiel Moreno <49887871+matiasmoreno876@users.noreply.github.com> Co-authored-by: Federico Rodriguez <federico.rodriguez@wazuh.com>
8 tasks
4 tasks
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.
Hi team, this resolves:
Closes #1101