Skip to content

[AWS Firehose] Improve Firehose documentation #4818

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

Merged

Conversation

Kavindu-Dodan
Copy link
Contributor

@Kavindu-Dodan Kavindu-Dodan commented Feb 11, 2025

Description

Improves AWS Firehose documentation, aligning with the update done on AWS Firehose Integration documentation at elastic/integrations#12732

Further, updates all Firehose related documentations to have the same or similar recommended configurations.

Documentation sets edited in this PR

Check all that apply.

  • Stateful (docs/en/observability/*)
  • Serverless (docs/en/serverless/*)
  • Integrations Developer Guide (docs/en/integrations/*)
  • [] None of the above

Related issue

Related : elastic/integrations#12150
Related : #4784

Checklist

  • Product/Engineering Review
  • Writer Review

Follow-up tasks

Select one.

  • This PR does not need to be ported to another doc set because:
    • The concepts in this PR only apply to one doc set (serverless or stateful)
    • The PR contains edits to both doc sets (serverless and stateful)
  • This PR needs to be ported to another doc set:
    • Port to stateful docs: <link to PR or tracking issue>
    • Port to serverless docs: <link to PR or tracking issue>

@Kavindu-Dodan Kavindu-Dodan added needs-writer-review backport-8.16 Automated backport with mergify backport-8.17 Automated backport with mergify labels Feb 11, 2025
@Kavindu-Dodan Kavindu-Dodan requested a review from a team as a code owner February 11, 2025 22:41
Copy link
Contributor

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

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.

Copy link
Contributor

Warning

It looks like this PR modifies one or more .asciidoc files. These files are being migrated to Markdown, and any changes merged now will be lost. See the migration guide for details.

@Kavindu-Dodan Kavindu-Dodan requested a review from zmoog February 11, 2025 22:41
@Kavindu-Dodan
Copy link
Contributor Author

Kavindu-Dodan commented Feb 11, 2025

Warning

It looks like this PR modifies one or more .asciidoc files. These files are being migrated to Markdown, and any changes merged now will be lost. See the migration guide for details.

Not an urgent change, hence can wait till the freeze is lifted.

Copy link
Contributor

Warning

It looks like this PR modifies one or more .asciidoc files. These files are being migrated to Markdown, and any changes merged now will be lost. See the migration guide for details.

@zmoog
Copy link
Contributor

zmoog commented Feb 12, 2025

@alaudazzi, this is a change that we need to ship on 8.x.

Should we:

  • open a new PR targeting the 8.x branch with the update in asciidoc and
  • open a new PR targeting main with the exact change in markdown when the freeze lifts

?

Copy link
Contributor

@zmoog zmoog left a comment

Choose a reason for hiding this comment

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

The current changes looks good.

We also mention the es_datastream_name parameter in other Firehose focused guides:

  • monitor-aws-cloudtrail-firehose.asciidoc
  • monitor-aws-cloudwatch-firehose.asciidoc
  • monitor-aws-firewall-firehose.asciidoc
  • monitor-aws-waf-firehose.asciidoc

where we suggest to use a log-specific data stream name instead of the one with routing.

I see the following possible enhancements and alignments with the changes already in this PR:

  • align the endpoint URL format (https://<cluster-id>.es.<region>.<csp>.elastic-cloud.com instead of https://my-deployment.es.us-east-1.aws.elastic-cloud.com).
  • suggesting to use logs-awsfirehose-default instead of the log specific one for better flexibility
  • mention that logs-awsfirehose-default is for logs only and the routing data stream is different; these are logs focused guide, but users new to the service may use the wrong one

WDYT?

@alaudazzi
Copy link
Contributor

@zmoog

as per email sent on Jan 17

We are freezing only the main/master public-facing Docs. You can continue to make changes to the 8.x Docs by creating PRs in the 8.x branches.
Before 29-Jan, you can create and merge 9.0.0 Docs PRs using the main/master branches.
During the documentation freeze, open issues for 9.0.0 Docs changes and we’ll add the Docs post migration.
For 9.0.0 beta1, rc1, and rc2, we will temporarily publish release notes in the AsciiDoc system.
We’ll open changes to the 9.0.0 Docs to everyone on 21-Feb.

For questions, post in the #docs Slack channel.

This comment was marked as duplicate.

@Kavindu-Dodan
Copy link
Contributor Author

@zmoog

align the endpoint URL format (https://.es...elastic-cloud.com instead of https://my-deployment.es.us-east-1.aws.elastic-cloud.com).

Yes, I updated all relevant documents to have this URL format. And I had to remove Important notice as I had to add new section mentioning S3 backups. This was missing in some docs and IMO this is important

suggesting to use logs-awsfirehose-default instead of the log specific one for better flexibility

Since es_datastream_name optional, I removed this from all docs except for the Firehose core document ingest-aws-firehose.asciidoc. This IMO avoids confusion for end users.

@alaudazzi thank you for the input. This PR can wait but appreciate a review when you have time 🙏

@Kavindu-Dodan Kavindu-Dodan requested a review from zmoog February 12, 2025 19:07
@Kavindu-Dodan Kavindu-Dodan force-pushed the chore/update-firehose-documentation branch from d034ce1 to ae4d1fe Compare February 12, 2025 19:11

This comment was marked as duplicate.

@zmoog
Copy link
Contributor

zmoog commented Feb 12, 2025

Yes, I updated all relevant documents to have this URL format. And I had to remove Important notice as I had to add new section mentioning S3 backups. This was missing in some docs and IMO this is important

LGTM, thanks.

This PR can wait but appreciate a review when you have time 🙏

If I'm getting this right, from Feb 21, the docs in main will be in markdown only, so:

  • main: we need to convert this PR in markdown
  • 8.x: we need to create another PR targeting this branch with these changes in asciidoc

@alaudazzi ?

alaudazzi
alaudazzi previously approved these changes Feb 13, 2025
Copy link
Contributor

@alaudazzi alaudazzi left a comment

Choose a reason for hiding this comment

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

I left some minor editing suggestions, otherwise LGTM.

This comment was marked as duplicate.

1 similar comment
Copy link
Contributor

Warning

It looks like this PR modifies one or more .asciidoc files. These files are being migrated to Markdown, and any changes merged now will be lost. See the migration guide for details.

zmoog
zmoog previously approved these changes Feb 17, 2025
Copy link
Contributor

@zmoog zmoog left a comment

Choose a reason for hiding this comment

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

LGTM

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>
Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>
Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>
Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>
Copy link
Contributor

Warning

It looks like this PR modifies one or more .asciidoc files. These files are being migrated to Markdown, and any changes merged now will be lost. See the migration guide for details.

@Kavindu-Dodan
Copy link
Contributor Author

@alaudazzi will it be possible to get a review ?

Besides, the freeze is lift on doc changes. However, it seems observability-docs is still in asciidoc format. So I assume changes are still allowed here ?

@Kavindu-Dodan
Copy link
Contributor Author

I have opened this PR for Docs-Content repository - elastic/docs-content#578

alaudazzi
alaudazzi previously approved these changes Feb 27, 2025
Copy link
Contributor

@alaudazzi alaudazzi left a comment

Choose a reason for hiding this comment

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

Left a minor editing suggestion, otherwise LGTM.

….asciidoc

Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com>
Copy link
Contributor

Warning

It looks like this PR modifies one or more .asciidoc files. These files are being migrated to Markdown, and any changes merged now will be lost. See the migration guide for details.

Copy link
Contributor

@alaudazzi alaudazzi left a comment

Choose a reason for hiding this comment

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

LGTM

@Kavindu-Dodan Kavindu-Dodan merged commit 9813ea7 into elastic:main Feb 27, 2025
5 of 6 checks passed
mergify bot pushed a commit that referenced this pull request Feb 27, 2025
* update firehose endpoint and data stream details

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* improve api key and retry duration section

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* fix wording of storage location

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* improve further by modifying all related documents

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* Update docs/en/observability/cloud-monitoring/aws/ingest-aws-firehose.asciidoc

Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com>

---------

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>
Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com>
(cherry picked from commit 9813ea7)

# Conflicts:
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudtrail-firehose.asciidoc
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudwatch-firehose.asciidoc
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-firewall-firehose.asciidoc
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-waf-firehose.asciidoc
mergify bot pushed a commit that referenced this pull request Feb 27, 2025
* update firehose endpoint and data stream details

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* improve api key and retry duration section

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* fix wording of storage location

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* improve further by modifying all related documents

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* Update docs/en/observability/cloud-monitoring/aws/ingest-aws-firehose.asciidoc

Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com>

---------

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>
Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com>
(cherry picked from commit 9813ea7)
alaudazzi pushed a commit that referenced this pull request Feb 28, 2025
* update firehose endpoint and data stream details

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* improve api key and retry duration section

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* fix wording of storage location

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* improve further by modifying all related documents

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* Update docs/en/observability/cloud-monitoring/aws/ingest-aws-firehose.asciidoc

Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com>

---------

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>
Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com>
(cherry picked from commit 9813ea7)

Co-authored-by: Kavindu Dodanduwa <Kavindu-Dodan@users.noreply.github.com>
Kavindu-Dodan added a commit to elastic/docs-content that referenced this pull request Feb 28, 2025
## Description

Improves AWS Firehose documentation, aligning with the update done on
AWS Firehose Integration documentation at
elastic/integrations#12732

This is a follow-up of
elastic/observability-docs#4818 for the new doc
content repository.


### Related issue

Related PR - elastic/observability-docs#4818 
Related : elastic/integrations#12150 
Related : elastic/observability-docs#4784

---------

Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com>
Kavindu-Dodan added a commit that referenced this pull request Feb 28, 2025
* update firehose endpoint and data stream details

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* improve api key and retry duration section

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* fix wording of storage location

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* improve further by modifying all related documents

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* Update docs/en/observability/cloud-monitoring/aws/ingest-aws-firehose.asciidoc

Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com>

---------

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>
Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com>
(cherry picked from commit 9813ea7)

# Conflicts:
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudtrail-firehose.asciidoc
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudwatch-firehose.asciidoc
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-firewall-firehose.asciidoc
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-waf-firehose.asciidoc
Kavindu-Dodan added a commit that referenced this pull request Feb 28, 2025
* update firehose endpoint and data stream details

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* improve api key and retry duration section

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* fix wording of storage location

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* improve further by modifying all related documents

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* Update docs/en/observability/cloud-monitoring/aws/ingest-aws-firehose.asciidoc

Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com>

---------

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>
Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com>
(cherry picked from commit 9813ea7)

# Conflicts:
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudtrail-firehose.asciidoc
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudwatch-firehose.asciidoc
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-firewall-firehose.asciidoc
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-waf-firehose.asciidoc
Kavindu-Dodan added a commit that referenced this pull request Feb 28, 2025
* update firehose endpoint and data stream details

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* improve api key and retry duration section

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* fix wording of storage location

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* improve further by modifying all related documents

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* Update docs/en/observability/cloud-monitoring/aws/ingest-aws-firehose.asciidoc

Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com>

---------

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>
Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com>
(cherry picked from commit 9813ea7)

# Conflicts:
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudtrail-firehose.asciidoc
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudwatch-firehose.asciidoc
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-firewall-firehose.asciidoc
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-waf-firehose.asciidoc
Kavindu-Dodan added a commit that referenced this pull request Mar 3, 2025
* update firehose endpoint and data stream details

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* improve api key and retry duration section

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* fix wording of storage location

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* improve further by modifying all related documents

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

* Update docs/en/observability/cloud-monitoring/aws/ingest-aws-firehose.asciidoc

Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com>

---------

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>
Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com>
(cherry picked from commit 9813ea7)

# Conflicts:
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudtrail-firehose.asciidoc
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudwatch-firehose.asciidoc
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-firewall-firehose.asciidoc
#	docs/en/observability/cloud-monitoring/aws/monitor-aws-waf-firehose.asciidoc

Co-authored-by: Kavindu Dodanduwa <Kavindu-Dodan@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.16 Automated backport with mergify backport-8.17 Automated backport with mergify needs-writer-review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants