Skip to content

Conversation

@vishaangelova
Copy link
Contributor

Summary

This PR documents the “Write to logs streams” setting in the Elasticsearch output settings and Remote Elasticsearch output docs.

Resolves #3855

Generative AI disclosure

  1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
  • Yes
  • No

@github-actions
Copy link

github-actions bot commented Dec 9, 2025

✅ Vale Linting Results

No issues found on modified lines!

@github-actions
Copy link

github-actions bot commented Dec 9, 2025

Copy link
Contributor

@mdbirnstiehl mdbirnstiehl left a comment

Choose a reason for hiding this comment

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

Overall, LGTM! I made one suggestion to emphasize that this setting is only part of the process. Feel free to modify as you see fit.

5. Adjust any settings as preferred. For example, you can update the `compression_level` setting to `4`.
When you create an {{agent}} policy using this output, the output will use the balanced preset options except with the higher compression level, as specified.

**Write to logs streams** {applies_to}`serverless: preview` {applies_to}`stack: preview 9.2`
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't get why these aren't simply H3 - across the whole page. Would it make the "On this page" section hard to read? If not, I don't see why not. You could always make them H4 - then they wouldn't even appear in "On this page".

Copy link
Contributor Author

Choose a reason for hiding this comment

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

As I mentioned in our private conversation on Slack, I think maybe it’s worth keeping the settings out of the heading structure. Skipping heading levels is not good from SEO perspective, but also because these setting names are very diverse and inconsistent. Some are short and undescriptive - which might be a problem from SEO perspective, too - and changing the heading would not really be an option, because these are the names of the actual fields on the UI. Others are long, e.g. "Make this output the default for agent integrations” which is also not a good fit for a heading.

So overall, I think I’d prefer to keep these as they are.

Copy link
Contributor

Choose a reason for hiding this comment

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

Having thought about it better, I agree. Approved!

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.

[Internal]: Update Fleet output settings to include "Write to logs streams"

4 participants