You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the ES module is designed in such a way that all accesses to Elasticsearch go to the same cluster endpoint(s).
We would like to be able to send requests related to analytics to one ES endpoint and requests related to our custom document indices (i.e. anything using Indexable) to another ES endpoint. This separation would allow us to upgrade our Elasticsearch usage from ES 1.x to ES 5.x or 6.x independently: first for analytics, then for our custom indices; or vice versa.
The text was updated successfully, but these errors were encountered:
nickmarden
changed the title
Split Kibana/Logstash Elasticsearch client configuration from custom index Elasticsearch client configuration
Split ELK ES client config from custom index ES client config
Jun 8, 2018
nickmarden
changed the title
Split ELK ES client config from custom index ES client config
Separate ELK ES client config from custom index ES client config
Jun 8, 2018
Right now the ES module is designed in such a way that all accesses to Elasticsearch go to the same cluster endpoint(s).
We would like to be able to send requests related to analytics to one ES endpoint and requests related to our custom document indices (i.e. anything using Indexable) to another ES endpoint. This separation would allow us to upgrade our Elasticsearch usage from ES 1.x to ES 5.x or 6.x independently: first for analytics, then for our custom indices; or vice versa.
The text was updated successfully, but these errors were encountered: