-
Notifications
You must be signed in to change notification settings - Fork 144
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 a new section on how to collect any log from CloudWatch using Firehose #3887
base: main
Are you sure you want to change the base?
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 is now in conflict. Could you fix it @alaudazzi? 🙏
|
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.
I expanded steps 2-5 with the new content I added to the public note we used as a raw material source for this topic.
I think it is ready for a review round! 😇
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.
Added some editorial contents. Some of the comments relate to restructuring. If you need help, you can reach out in the obs-docs channel in slack. Hope this is helpful!
docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudwatch-firehose.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudwatch-firehose.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudwatch-firehose.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudwatch-firehose.asciidoc
Outdated
Show resolved
Hide resolved
|
||
In this tutorial, we will write a simple AWS Lambda-based app, collect its application logs, and forward them to Elastic. | ||
|
||
Like many other services and platforms in AWS, Lambda functions natively log directly to CloudWatch out of the box. Lambda functions are a great tool for experimenting on AWS. |
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.
I don't think this sentence is relevant or necessary. I would remove it: "Lambda functions are a great tool for experimenting on AWS."
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.
Yeah, I see. My original intent was to explain why we picked up lambda for this tutorial, but I agree it is irrelevant and adds too little value to stay.
docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudwatch-firehose.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudwatch-firehose.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudwatch-firehose.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudwatch-firehose.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudwatch-firehose.asciidoc
Outdated
Show resolved
Hide resolved
Co-authored-by: DeDe Morton <dede.morton@elastic.co>
@dedemorton, thank you for your helpful review comments and suggestions! I added all the suggestions and addressed the comments on the structure. Let me know what you think when you have time. |
These diagrams help orient users in their journey.
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 couple more comments for ya!
|
||
1. Visit the AWS web console and open the AWS Lambda page. | ||
2. Click **Create function** and select the option to create a function from scratch. | ||
3. Select a **Function name** |
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.
For consistency with other steps
3. Select a **Function name** | |
3. Select a **Function name**. |
Set the **Parameters** in the **Destination settings** section. | ||
|
||
[discrete] | ||
[[firehose-cloudwatch-step-three-desination-settings-parameters]] | ||
=== Parameters | ||
|
||
Use the following parameters: |
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 feels like this line should be in the next section?
Set the **Parameters** in the **Destination settings** section. | |
[discrete] | |
[[firehose-cloudwatch-step-three-desination-settings-parameters]] | |
=== Parameters | |
Use the following parameters: | |
[discrete] | |
[[firehose-cloudwatch-step-three-desination-settings-parameters]] | |
=== Parameters | |
Set the **Parameters** in the **Destination settings** section. | |
Use the following parameters: |
|
||
[discrete] | ||
[[firehose-cloudwatch-step-four-subscription-filter-destination]] | ||
==== Choose destination |
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.
These headings don't display correctly but that's a CSS bug. We have a PR open in elastic/docs to fix this.
|
||
On the AWS console, visit your Firehose stream and check for entries in the *Destination error logs* section. | ||
|
||
If everything is running smoothly, this list will be empty. If there's an error, you can check the details. Here is a delivery stream that fails to send records to the Elastic stack due to bad authentication settings: |
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.
This is a good example to include 👍
This PR:
Closes #3882