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

Doc: Logstash output.elasticsearch index can be alias or datastream #1179

Merged
merged 8 commits into from
Apr 30, 2024

Conversation

karenzone
Copy link
Contributor

Starts with @stefnestor 's work in #1136, and bumps gemspec and changelog version to v.11.22.6

stefnestor and others added 7 commits May 29, 2023 07:10
👋 howdy, team! Support's noticed some user setup confusion on `index` being able to point to aliases/datastreams and not just indices. This mini expansion helps users understand that "index" used here means "indexing into" which can point to index/alias/datastream. TIA!
@karenzone karenzone self-assigned this Apr 29, 2024
Copy link
Contributor

@mashhurs mashhurs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one minor change requested and LGTM.

CHANGELOG.md Outdated Show resolved Hide resolved
Co-authored-by: Mashhur <99575341+mashhurs@users.noreply.github.com>
@karenzone karenzone merged commit 1321073 into logstash-plugins:main Apr 30, 2024
2 checks passed
@karenzone karenzone deleted the 1136-stefnestor branch April 30, 2024 00:15
@karenzone
Copy link
Contributor Author

Published to rubygems.org at v11.22.6

stefnestor added a commit to elastic/beats that referenced this pull request May 22, 2024
👋 Playing forward logstash-plugins/logstash-output-elasticsearch#1179, our client-side docs think `index` indicates a literal Elasticsearch index when in now this means any ingest target (index, alias, or data stream).
stefnestor added a commit to elastic/beats that referenced this pull request May 24, 2024
👋 Playing forward logstash-plugins/logstash-output-elasticsearch#1179, our client-side docs think `index` indicates a literal Elasticsearch index when in now this means any ingest target (index, alias, or data stream).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants