-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Use a other node Elasticsearch for config #909
Comments
I found a solution with httpd and urlrewrite. |
Would you mind making a gits of the config you made? Thanks! |
I have not tested it yet but I will draw the configuration "sample/apache_ldap.conf" |
w33ble
pushed a commit
to w33ble/kibana
that referenced
this issue
Sep 13, 2018
* Feat: brush up centeredResizeManipulation (cherry picked from commit de3490f) * Feat: activate centeredResizeManipulation on Alt key (cherry picked from commit 845b81f)
Merged
7 tasks
2 tasks
ecezalp
added a commit
to ecezalp/kibana
that referenced
this issue
Apr 12, 2021
…ert Side Panel (elastic#909) (elastic#95604) [Security Solution] Adds Threat Summary and Threat Info views to Alert Side Panel (elastic/security-team/909)
ecezalp
added a commit
that referenced
this issue
Apr 13, 2021
…ert Side Panel (#909) (#95604) (#96879) [Security Solution] Adds Threat Summary and Threat Info views to Alert Side Panel (elastic/security-team/909) Co-authored-by: Kibana Machine <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
We want to differentiate reading and configuration in ElasticSearch.
It would be nice to offer the possibility to specify a ElasticSearch node for each case.
Cordialy.
The text was updated successfully, but these errors were encountered: