Skip to content

[IngestArch] Add serverless config sample 8.19 #1895

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

Closed
karenzone wants to merge 1 commit into from
+6 −5
Closed

[IngestArch] Add serverless config sample 8.19 #1895

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
11 changes: 6 additions & 5 deletions docs/en/ingest-arch/13-multitenant.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,8 +16,8 @@ These logs need to be sent to different {es} clusters and to S3 for backup and a
In such use cases, agents send the data to {ls} as a routing mechanism to different destinations.
Note that the System and Windows integrations must be installed on all {es} clusters to which the data is routed.

Sample config::
+
==== Sample config: Sending data to both {ech} and {es-serverless}

[source,ruby]
input {
elastic_agent {
Expand All @@ -34,19 +34,20 @@ filter {
output {
if [@metadata][tenant] == "tenant01" {
elasticsearch {
cloud_id => "<cloud id>"
hosts => "ELASTICSEARCH_ENDPOINT_URL" <1>
api_key => "<api key>"
}
} else if [@metadata][tenant] == "tenant02" {
elasticsearch {
cloud_id => "<cloud id>"
cloud_id => "<cloud id>" <2>
api_key => "<api key>"
}
}
}

<1> Use the `hosts` option with the Elasticsearch endpoint URL to send data to Elasticsearch Serverless
<2> Use `cloud_id` to send data to Elastic Cloud Hosted

[discrete]
[[multi-resources]]
==== Resources

Expand Down