Skip to content
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

Separate ELK ES client config from custom index ES client config #3

Closed
nickmarden opened this issue Mar 7, 2018 · 0 comments
Closed
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@nickmarden
Copy link
Contributor

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.

@nickmarden nickmarden added help wanted Extra attention is needed good first issue Good for newcomers labels Mar 7, 2018
@nickmarden 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 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants