This functionality is experimental and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but experimental features are not subject to the support SLA of official GA features.
« Configure the Console output Change the output codec »
Elastic Docs ›Journalbeat Reference [6.6] ›Configuring Journalbeat ›Configure the output

Configure the output for the Elastic Cloud

edit

Configure the output for the Elastic Cloud

edit

Journalbeat comes with two settings that simplify the output configuration when used together with Elastic Cloud. When defined, these setting overwrite settings from other parts in the configuration.

Example:

cloud.id: "staging:dXMtZWFzdC0xLmF3cy5mb3VuZC5pbyRjZWM2ZjI2MWE3NGJmMjRjZTMzYmI4ODExYjg0Mjk0ZiRjNmMyY2E2ZDA0MjI0OWFmMGNjN2Q3YTllOTYyNTc0Mw=="
cloud.auth: "elastic:YOUR_PASSWORD"

These settings can be also specified at the command line, like this:

journalbeat -e -E cloud.id="<cloud-id>" -E cloud.auth="<cloud.auth>"

cloud.id

edit

The Cloud ID, which can be found in the Elastic Cloud web console, is used by Journalbeat to resolve the Elasticsearch and Kibana URLs. This setting overwrites the output.elasticsearch.hosts and setup.kibana.host settings.

cloud.auth

edit

When specified, the cloud.auth overwrites the output.elasticsearch.username and output.elasticsearch.password settings. Because the Kibana settings inherit the username and password from the Elasticsearch output, this can also be used to set the setup.kibana.username and setup.kibana.password options.

« Configure the Console output Change the output codec »