-
Notifications
You must be signed in to change notification settings - Fork 63
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
Add new data stream type custom component template to Fleet docs #1335
Add new data stream type custom component template to Fleet docs #1335
Conversation
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
This pull request does not have a backport label. Could you fix it @jillguyonnet? 🙏
|
Hi @kilfoyle 👋 I took the liberty of opening this PR for the documentation side of elastic/kibana#190730 as it seemed quite small 🙂 |
When you install an integration, {fleet} creates two default `@custom` component templates: | ||
. A `@custom` component template allowing customization across all documents of a given data stream type, named following the pattern: `<data_stream_type>@custom`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When you install an integration, {fleet} creates two default `@custom` component templates: | |
. A `@custom` component template allowing customization across all documents of a given data stream type, named following the pattern: `<data_stream_type>@custom`. | |
When you install an integration, {fleet} creates two default `@custom` component templates: | |
* A `@custom` component template allowing customization across all documents of a given data stream type, named following the pattern: `<data_stream_type>@custom`. |
We just need a line break after the line with the colon for the list to render properly. Here's how it'll look:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider an unordered list here? Numbering list items implies procedural steps or a sequence.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @karenzone. I've made that change in the suggestion (and added a second one below).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 🚀
Thanks a lot @jillguyonnet! I always really appreciate when people open up docs PRs. It saves me a lot of time. The text is perfect. Just one small formatting suggestion.
P.S., I think the preview page takes a while. It usually shows up shortly after the docs-build-pr CI finishes up. I added a |
When you install an integration, {fleet} creates a default `@custom` component template for each data stream. The Custom component templates are named following the pattern: `<name_of_data_stream>@custom`. | ||
When you install an integration, {fleet} creates two default `@custom` component templates: | ||
. A `@custom` component template allowing customization across all documents of a given data stream type, named following the pattern: `<data_stream_type>@custom`. | ||
. A `@custom` component template for each data stream, named following the pattern: `<name_of_data_stream>@custom`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
. A `@custom` component template for each data stream, named following the pattern: `<name_of_data_stream>@custom`. | |
* A `@custom` component template for each data stream, named following the pattern: `<name_of_data_stream>@custom`. |
Thank you for your review @kilfoyle @karenzone! I put screenshots in the PR description. Can you please re-approve if everything looks OK? 🙏 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's perfect! 🚀
Thanks a lot @jillguyonnet
LGTM
Add new datastream type custom component template to Fleet data streams docs (cherry picked from commit b50aa87)
Relates elastic/kibana#190730
This PR update the Fleet data stream docs to document the new data stream type custom component template feature.
Before:
After: