Skip to content

[Website]: Document / check what happens when not providing es_datastream_name #3705

@lucabelluccini

Description

@lucabelluccini

Type of issue

None

What documentation page is affected

https://www.elastic.co/docs/reference/integrations/awsfirehose

What happened?

We should clarify what happens if someone doesn't define es_datastream_name.

From the docs, it looks like it should go to logs-awsfirehose-default data stream, but from a recent test it seems it doesn't and requests are rejected with a 400 error.

Still, it's unclear what data stream will be used when shipping logs or metrics not supported by the integration.

  • Or we're not honoring the default logs-awsfirehose-default data stream
  • Or the setting es_datastream_name is mandatory when shipping logs or metrics not supported by AWS Firehose integration.

Additional info

This requires engineering check prior to be documented.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Team:ObsIssues owned by the Observability Docs Teamsource:webIssues originating from the elastic.co docs

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions