Skip to content

Conversation

karenzone
Copy link
Contributor

@karenzone karenzone commented Aug 25, 2025

Related: https://github.com/elastic/docs-content-internal/issues/176

Add page with details about sending Logstash output to Elasticsearch Serverless

PREVIEW: https://docs-v3-preview.elastic.dev/elastic/logstash/pull/18034/reference/connecting-to-serverless

Follow-up PR:

#18166

@karenzone karenzone self-assigned this Aug 25, 2025
@github-actions
Copy link
Contributor

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@karenzone karenzone added docs backport-active-9 Automated backport with mergify to all the active 9.[0-9]+ branches labels Aug 25, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Aug 25, 2025

🔍 Preview links for changed docs

@elastic elastic deleted a comment from mergify bot Aug 25, 2025
@karenzone karenzone requested a review from ppf2 September 5, 2025 20:08
@karenzone karenzone marked this pull request as ready for review September 5, 2025 20:09
@karenzone
Copy link
Contributor Author

karenzone commented Sep 5, 2025

@ppf2, thanks for the issue.
Please take a look and let me know what you think.

@karenzone karenzone requested a review from robbavey September 5, 2025 22:20
@karenzone karenzone changed the title Doc: Add Logstash to serverless page Doc: Add Logstash-to-serverless page Sep 11, 2025
Copy link
Member

@robbavey robbavey left a comment

Choose a reason for hiding this comment

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

Questions around whether we should document the filter and input here, and some changes I'd like to see to clarify the purpose of xpack.management.*

- https://www.elastic.co/guide/en/logstash/current/connecting-to-cloud.html
---

# Sending data to {{es-serverless}} [logstash-to-elasticsearch-serverless]
Copy link
Member

Choose a reason for hiding this comment

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

Do we also need to document the Elasticsearch input and Elasticsearch filter here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This suggestion warrants discussion. The content in this PR is currently unavailable in our docs, and I don't want to hold it up. Please elaborate on what you think we need to say about input and filter in this context, and we can handle in a followup PR. I'll open a new issue if we need it.

Copy link
Member

Choose a reason for hiding this comment

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

My thinking here is that everything that we state around cloud IDs, and API keys in the Communication between LS and ES-serverless section that mention the Elasticsearch output, also hold for the Elasticsearch input and filter plugins.

Copy link
Member

@robbavey robbavey left a comment

Choose a reason for hiding this comment

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

LGTM - let's follow up with content on other plugins that communicate with Elasticsearch

@karenzone karenzone merged commit feabee2 into elastic:main Sep 15, 2025
11 checks passed
@karenzone karenzone deleted the 176-send-to-svrless branch September 15, 2025 17:00
@github-actions
Copy link
Contributor

@Mergifyio backport 9.0 9.1

@mergify
Copy link
Contributor

mergify bot commented Sep 15, 2025

backport 9.0 9.1

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Sep 15, 2025
mergify bot pushed a commit that referenced this pull request Sep 15, 2025
karenzone added a commit that referenced this pull request Sep 15, 2025
(cherry picked from commit feabee2)

Co-authored-by: Karen Metts <[email protected]>
karenzone added a commit that referenced this pull request Sep 15, 2025
(cherry picked from commit feabee2)

Co-authored-by: Karen Metts <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-active-9 Automated backport with mergify to all the active 9.[0-9]+ branches docs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants