-
Notifications
You must be signed in to change notification settings - Fork 37
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
Create a mechanism that deploys Observability Stack and Logging Stack using OpenSearch #80
Comments
@dblock @peterzhuamazon @bbarani What do you all think about it? |
Are you looking for something like plural.sh? Haven't tried it myself. |
Yup something along the lines of it but more to be suitable for setting up OpenSearch specific apps/stacks. |
Helm repo can create a new chart. I am not sure if we want to maintain multiple copies of the same mechanism, but consider we already maintain distinct copy of chart and playbook, it makes sense to me to create one for each. |
Logstash with combination of fluentD is used at most places as data collectors, fluentD as an agent captures logs and forwards them to Logstash and Logstash parses the log and pushes to OpenSearch, sometimes Logstash is replaced with kafka or used both in combination for advance usage (with kafka input plugin). This combination of Logstash + fluentD + OpenSearch + OpenSearch-Dashboard would be an ideal logging stack. |
Is your feature request related to a problem? Please describe.
Everyone have their own system and tool to have these kind of stacks setup along with the core OpenSearch and OpenSearch Dashboards. It will be awesome to have a standard setup way which can easily self managed and is cloud agnostic at the same time.
Describe the solution you'd like
There can be multiple solutions to it:
So if I want to deploy a stack with (OpenSearch + Dashboards + Logstash). I can do them at one go at one shot.
Describe alternatives you've considered
There are some blogs around it but nothing that can be standardised. If some standard tools that can be developed. This will help the broader audience and will serve as pretty cool starter for them
Additional context
These can be further extended to build intelligent tooling to solve many more such interesting usecases
The text was updated successfully, but these errors were encountered: