Skip to content

Comments

[Streams] Update wired streams endpoints#5231

Open
mdbirnstiehl wants to merge 7 commits intoelastic:mainfrom
mdbirnstiehl:wired-streams-endpoints
Open

[Streams] Update wired streams endpoints#5231
mdbirnstiehl wants to merge 7 commits intoelastic:mainfrom
mdbirnstiehl:wired-streams-endpoints

Conversation

@mdbirnstiehl
Copy link
Contributor

@mdbirnstiehl mdbirnstiehl commented Feb 19, 2026

This PR closes #5139 and updates the wired streams docs to include the new endpoints that will be going out in serverless and 9.4.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 19, 2026

✅ Vale Linting Results

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 19, 2026

@mdbirnstiehl
Copy link
Contributor Author

@mohamedhamed-ahmed One thing I wasn't sure on, do users need to specify an endpoint, or is that something that happens automatically? I'm thinking mainly of the ship to wired streams section and whether or not we need to make updates there.

@mdbirnstiehl mdbirnstiehl marked this pull request as ready for review February 19, 2026 22:04
@mdbirnstiehl mdbirnstiehl requested a review from a team as a code owner February 19, 2026 22:04
Copy link
Contributor

@nastasha-solomon nastasha-solomon left a comment

Choose a reason for hiding this comment

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

beans

@mohamedhamed-ahmed
Copy link

@mohamedhamed-ahmed One thing I wasn't sure on, do users need to specify an endpoint, or is that something that happens automatically? I'm thinking mainly of the ship to wired streams section and whether or not we need to make updates there.

@mdbirnstiehl Using one of the new endpoints needs to be explicitly decided depending on the format of logs being sent. We should no longer mention the usage of the old logs endpoint as its now deprecated, users will need to send their logs to either 1 of the 2 new endpoints as there is no way of doing this automatically.

Once you've sent your data to the `/logs` endpoint, open the stream and use the **Partitioning** tab to organize and route the data into meaningful child streams. For example, you can partition your logs into child streams their source or type:
Once you've sent your data to a wired streams endpoint, open the stream and use the **Partitioning** tab to organize and route the data into meaningful child streams. For example, you can partition your logs into child streams their source or type:

- Route application logs to a `logs.myapp` child stream.

Choose a reason for hiding this comment

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

maybe it would be ideal if we can update the examples as well to reflect the new endpoints as we can no longer have a logs.myapp child stream

For example, suppose you have a noisy firewall and a quiet custom application sending logs to the same stream. You don't need to retain the firewall logs for as long and they take up disk space. In this case, you can partition the stream and assign a different [{{ilm-init}} policy or retention setting](./retention.md) to each child stream:

```bash
logs

Choose a reason for hiding this comment

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

here as well

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.

[Streams] Document new wired streams endpoints

3 participants