-
Notifications
You must be signed in to change notification settings - Fork 713
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
User facing documentation for Logstash on ECK #6585
Conversation
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.
I think we can update the container version in all recipes from 8.6.1
to 8.7.0
, especially Logstash stack monitoring only works with 8.7+
For the todo, we will need to cover pipeline reload use case.
} | ||
} | ||
output { | ||
stdout { codec => rubydebug } |
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.
As elasticsearch cluster is included in the sample, I think the pipeline can have es-output example
elasticsearch {
hosts => [ "${DEFAULT_ELASTICSEARCH_HOSTS}" ]
user => "${DEFAULT_ELASTICSEARCH_USER}"
password => "${DEFAULT_ELASTICSEARCH_PASSWORD}"
cacert => "${DEFAULT_ELASTICSEARCH_CA_CERTS}"
}
send_to => 'prod' | ||
} | ||
pipeline { | ||
send_to => 'qa' |
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.
👍 nice pipeline-to-pipeline example
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.
Nearly! I forgot to remove some old pipelines 🤦
need a section for es-output to point users to customize users and roles |
=== Single Pipeline defined in CRD | ||
|
||
[source,sh,subs="attributes"] | ||
---- | ||
kubectl apply -f {logstash_recipes}/logstash-eck.yaml | ||
---- | ||
|
||
Deploys Logstash with a single pipeline defined in the CRD |
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.
Is it intentional to repeat this Single Pipeline defined in CRD
section?
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.
It is not 🤦
* <<{p}-logstash-technical-preview-limitations,Technical Preview Limitations>> | ||
|
||
|
||
NOTE: Running Logstash on ECK is compatible only with Logstash 8.7+. |
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.
Do we need to remove this? I do see LS 8.6.1 versions are in settings (ex: logstash.yml) and as I understood stack monitoring for Logstash requires 8.7.0+.
Or, we can change all configs version to 8.7.0 to align with this note.
* In the init container: copy the Elasticsearch configuration, and then create links. * Set default security context for Elasticsearch containers, including the sidecars. * Add E2E check for securityContext.
…ic#6724) * Introduce HasWarnings interface * Update samples in config/recipes * Update example in docs * Update CRD/API documentation * Update Helm Charts * Add checkPolicyID for next major release
* Update module go.elastic.co/apm/v2 to v2.4.1 * Update module go.elastic.co/apm/module/apmzap/v2 to v2.4.1 * Update module go.elastic.co/apm/module/apmhttp/v2 to v2.4.1 * Update module go.elastic.co/apm/module/apmelasticsearch/v2 to v2.4.1 --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Thibault Richard <[email protected]>
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.
Did a quick pass LGTM, found a few nits only.
docs/orchestrating-elastic-stack-applications/logstash.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/logstash.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/logstash.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/logstash.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/logstash.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/logstash.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/logstash.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/logstash.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/logstash.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/logstash.asciidoc
Outdated
Show resolved
Hide resolved
I referenced the new file from the Orchestrating Elastic Stack applications landing page. |
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.
I had a second pass and left a few editing suggestions.
docs/orchestrating-elastic-stack-applications/logstash.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/logstash.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/logstash.asciidoc
Outdated
Show resolved
Hide resolved
|
||
Deploys Logstash with the pipeline defined in a secret and referred to via `pipelinesRef` | ||
|
||
===== Pipeline as mounted volume - `logstash-pipelinevolume.yaml` |
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.
Proposal which implies to rename the file.
===== Pipeline as mounted volume - `logstash-pipelinevolume.yaml` | |
===== Pipeline as mounted volume - `logstash-pipeline-as-volume.yaml` |
docs/orchestrating-elastic-stack-applications/logstash.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/logstash.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/logstash.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/logstash.asciidoc
Outdated
Show resolved
Hide resolved
This commit introduces a technical preview of the Logstash Operator for ECK The Logstash operator introduces a Logstash CRD: This operator provides support for: * Defining logstash.yml in config or configRef sections of the CRD * Integration with Elasticsearch clusters via the use of elasticsearchRefs, and environment variable substitution to introduce those elasticsearch references into logstash pipelines. * Definition of pipelines.yml in pipelines or pipelinesRef sections of the CRD with support for pipeline definition in volume mounts * Support for multiple pipeline and pipeline->pipeline configurations * Support for automatic pipeline reload in logstash pods when a pipeline change is detected without triggering a full restart of the pod. * Stack monitoring support via sending metrics and logs to a monitoring elasticsearch cluster via the use of monitoring.logs.elasticsearchRefs and monitoring.metrics.elasticsearchRefs * Support for defining multiple services for logstash plugins. Logstash nodes are created as StatefulSets - we expect in later versions of the logstash operator to support persistence in Logstash nodes, including persistent queues and dead letter queues. A work in progress PR includes documentation and recipes on how to use this logstash operator. There are also samples in this PR located under config/samples/logstash/* Co-authored-by: Michael Morello <[email protected]> Co-authored-by: Rob Bavey <[email protected]> Co-authored-by: Kaise Cheng <[email protected]> Co-authored-by: kaisecheng <[email protected]> Co-authored-by: Michael Morello <[email protected]> Co-authored-by: Thibault Richard <[email protected]> Co-authored-by: Peter Brachwitz <[email protected]>
This adds a new flag `--container-repository` to the operator to be able to specify a global container repository. With this it is now possible to use DockerHub images for example: `--container-registry docker.io --container-repository=elastic`. --------- Co-authored-by: Peter Brachwitz <[email protected]>
This adjusts the number of volumes expected from Beats sidecars in the Logstash Stack Monitoring unit tests. Why? Because we don't test PRs with an automatic merge of the main branch (🐛🐞), we missed that the tests in elastic#6732 had to be updated to take into account the changes made by elastic#6703, which adds a new temp volume to the Beats sidecars.
2d57563
to
16694f1
Compare
Still a work in progress - will need elasticsearchRef to work fully
Co-authored-by: Thibault Richard <[email protected]> Co-authored-by: Arianna Laudazzi <[email protected]> Co-authored-by: Peter Brachwitz <[email protected]>
I've answered all the comments on this PR, and created a new one retargeted to the |
Work in Progress docs
Includes