-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[DOCS] Describe common use cases for functionbeat #12539
Conversation
@acchen97 I've added a couple of diagrams. Not sure which ingest node processors make sense to show for these examples, though. Can you suggest a few to give a realistic pipeline example in the diagram? |
|
||
. The structured events are indexed into an {es} cluster. | ||
|
||
image::./images/functionbeat-pipeline-cloudwatchlogs.png["{beatname_uc} collects events generated by CloudWatch logs"] |
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 @dedemorton. Shaping up nicely, left a few comments. @kvch and @ph may have have more real-world processor/pipeline examples for these use cases. |
* [DOCS] Describe common use cases for functionbeat * Add diagrams * Comment out section that is not yet true
…astic#12681) * [DOCS] Describe common use cases for functionbeat * Add diagrams * Comment out section that is not yet true
Closes #11867.
The text is ready to review, but I still need to add a couple diagrams, so I'm marking this as in progress.
TODO:
@acchen97 I decided to break this content out into sections so that it will scale as we add support for more use cases that we want to highlight. I also think that adding sections helps users who are scanning the content. I struggled with the notion of presenting use cases without telling folks how to implement them. My compromise was to describe how the data passes through the parts of the stack. I plan to add diagrams so that folks who like to scan can see quickly which parts of the stack are relevant to the use case.
The svg diagram shown here is from the functionbeat page: https://www.elastic.co/products/beats/functionbeat
I'm trying to locate the source so I can use the same images/fonts in the diagrams that show the processing pipeline.