Skip to content

Document remote Elasticsearch output support for OTel input packages in Fleet #7119

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.

Sign up for GitHub

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

Open
vishaangelova wants to merge 1 commit into
base: main
Choose a base branch
from
+10 −2
Open

Document remote Elasticsearch output support for OTel input packages in Fleet #7119

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions reference/fleet/otel-integrations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,10 +42,12 @@ When the integration policy for the input package is created, {{fleet}} creates

On the OpenTelemetry input package's **Configs** page, you can view a generated sample configuration, which you can use as a starting point to set up the integration on a standalone {{agent}}.

This is a partial configuration because it doesn't include an exporter component. For more information on setting up the exporter, refer to [{{es}} exporter](elastic-agent://reference/edot-collector/components/elasticsearchexporter.md).
This is a partial configuration because it doesn't include an exporter component. OpenTelemetry input packages support sending data using the {{es}} output. For more information on setting up the exporter, refer to [{{es}} exporter](elastic-agent://reference/edot-collector/components/elasticsearchexporter.md).

:::{note}
Currently, OpenTelemetry input packages only support sending data using the {{es}} output.
:applies_to: {serverless: preview, stack: preview 9.5+}

The [remote {{es}} output](/reference/fleet/remote-elasticsearch-output.md) is also supported as an exporter target.
:::

Only {{agents}} on version 9.2 or later can collect OTel data using OpenTelemetry input packages. OpenTelemetry input packages added to an agent policy do not affect enrolled agents on prior versions.
Expand Down
6 changes: 6 additions & 0 deletions reference/fleet/remote-elasticsearch-output.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,12 @@ Both the management cluster (where you configure {{fleet}}) and the remote clust

A remote {{es}} cluster supports the same [output settings](/reference/fleet/es-output-settings.md) as your management {{es}} cluster.

:::{note}
:applies_to: {serverless: preview, stack: preview 9.5+}

The remote {{es}} output can also serve as the exporter target for [OpenTelemetry input packages](/reference/fleet/otel-integrations.md) managed by {{fleet}}.
:::

## Limitations [remote-output-limitations]

These limitations apply to remote {{es}} output:
Expand Down
Loading