[Ingest] Use current Logstash security settings #4241
Merged
+6
−13
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Vale Linting ResultsSummary: 1 suggestion found 💡 Suggestions (1)
|
Contributor
Author
|
cc:/ @robbavey, please suggest a reviewer. |
3 tasks
vishaangelova
approved these changes
Dec 11, 2025
Contributor
vishaangelova
left a comment
vishaangelova
left a comment
There was a problem hiding this comment.
LGTM! (just noted a tiny typo)
solutions/observability/apm/apm-server/configure-logstash-output.md
Outdated
Show resolved
Hide resolved
…ut.md Co-authored-by: Visha Angelova <[email protected]>
robbavey
requested changes
Dec 12, 2025
Member
robbavey
left a comment
robbavey
left a comment
There was a problem hiding this comment.
We can remove ssl_enabled from the elasticsearch output definitions, it is inferred from hosts field or cloud_id
...ng-data-from-applications/ingest-data-from-relational-database-into-elasticsearch-service.md
Outdated
Show resolved
Hide resolved
...ng-data-from-applications/ingest-data-from-relational-database-into-elasticsearch-service.md
Outdated
Show resolved
Hide resolved
robbavey
reviewed
Dec 12, 2025
Member
robbavey
left a comment
robbavey
left a comment
There was a problem hiding this comment.
I missed a couple from last time
...-from-applications/ingest-data-from-beats-to-elasticsearch-service-with-logstash-as-proxy.md
Outdated
Show resolved
Hide resolved
...-from-applications/ingest-data-from-beats-to-elasticsearch-service-with-logstash-as-proxy.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Rob Bavey <[email protected]>
Co-authored-by: Rob Bavey <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Some security settings for Logstash plugins have been deprecated and removed at 9.0. This PR updates config samples to reflect those changes.
Fixes: #2819
Parent issue: #2743
Generative AI disclosure