Send logs to Elasticsearch

Create a stream that sends the logs of your applications to an Elasticsearch index, in Azion Console or with the Azion API, and confirm the delivery.

Last updated

View as Markdown Agent setup

You can send the logs of a stream to an Elasticsearch index from Azion Console or with the Azion API.

Data Stream sends each batch of log lines to the index that ends the URL of the endpoint. In the stream form, the endpoint is set in the field labeled Connector, and Elasticsearch is one of its options. For every field and its bounds, refer to Endpoints.

The example collects the requests of one workload with the Applications data source.

Select your interface once. The prerequisites and every task below show only that path.

Prerequisites

  • An Azion account with the Edit Data Stream permission. For the permissions, refer to Stream settings.
  • A workload on the account that receives requests.
  • An Elasticsearch instance. It can run on any cloud platform, such as an Elastic Cloud deployment.
  • The URL of the instance followed by the name of the index, such as https://elasticsearch.example.com/azion-logs. On Elastic Cloud, the Copy endpoint action of the deployment gives the address of the instance.
  • An Elasticsearch API key. When Elasticsearch creates the key, it returns an encoded value in Base64. Data Stream takes that encoded value. On Elastic Cloud, you create the key in the API console of the deployment.

Create the stream

The stream collects from the workload you choose, through a workload filter. Saving a stream with sampling deactivates your other streams, and a workload filter does not.

To create the stream with the API, send a POST request to https://api.azion.com/v4/workspace/stream/streams. Replace [TOKEN VALUE] with your personal token, <workload-id> with the ID of your workload, [API KEY] with the encoded value of your API key, and the URL with your own:

Shell
01curl -X POST 'https://api.azion.com/v4/workspace/stream/streams' \
02 -H 'Content-Type: application/json' \
03 -H 'Authorization: Token [TOKEN VALUE]' \
04 -d {
05 "name": "logs-to-elasticsearch",
06 "active": true,
07 "inputs": [
08 { "type": "raw_logs", "attributes": { "data_source": "workloads" } }
09 ],
10 "transform": [
11 { "type": "filter_workloads", "attributes": { "workloads": [<workload-id>] } },
12 { "type": "render_template", "attributes": { "template": 2 } }
13 ],
14 "outputs": [
15 {
16 "type": "elasticsearch",
17 "attributes": {
18 "url": "https://elasticsearch.example.com/azion-logs",
19 "api_key": "[API KEY]"
20 }
21 }
22 ]
23 }

The workloads data source is Applications in the Console, and template 2 is Applications Event Collector. The API answers 201 with the stored stream:

JSON
01{
02 "state": "executed",
03 "data": {
04 "id": 12351,
05 "name": "logs-to-elasticsearch",
06 "last_editor": "user@example.com",
07 "created": "2026-01-01T12:10:31.000000Z",
08 "last_modified": "2026-01-01T12:10:31.000000Z",
09 "product_version": "1.0",
10 …
11 "outputs": [
12 {
13 "type": "elasticsearch",
14 "attributes": {
15 "url": "https://elasticsearch.example.com/azion-logs",
16 "api_key": "[API KEY]"
17 }
18 }
19 ]
20 }
21}

The id identifies the stream in every later request, such as /v4/workspace/stream/streams/12351. For every key of the body, refer to Stream settings.

To create the stream in Azion Console:

Open Data Stream

Access Azion Console > Data Stream.

Select + Stream
Name the stream

In the General section, enter a Name. For example: logs-to-elasticsearch.

Select the data source

In the Input section, select Applications in Data Source.

Turn off Sampling

In the Transform section, turn off Sampling while Option is still All Current and Future Workloads, its starting value. A stream cannot carry sampling and a workload filter together.

Choose the workload

In the Transform section, set Option to Filter Workloads. In Available Workload, select your workload and move it to Chosen Workload with the arrow.

Select the template

In the Render Template section, select Applications Event Collector in Template.

Select the Elasticsearch endpoint

In the Output section, select Elasticsearch in Connector.

Enter the index URL

In URL, enter the URL of the instance followed by the index. For example: https://elasticsearch.example.com/azion-logs, where azion-logs is the index.

Enter the API key

In Encoded API Key, paste the Base64 encoded value of your Elasticsearch API key.

Keep the stream active

In the Status section, keep Active turned on.

Select Save

The Console shows Your data stream has been created. The stream appears in the Data Stream list with Elasticsearch in the Connector column and the Active status.

The API and the Console save the stream without contacting the instance. A wrong URL, index, or API key surfaces only when the stream sends. An activation takes effect after one to two minutes.

Confirm the delivery

Real-Time Events records every send of a stream, delivered or not, with the status code the endpoint returned. Send a few requests to the workload, then wait about a minute: a stream sends a batch every 60 seconds, or sooner when it reaches 2,000 log lines.

To read the sends with the API, query the dataStreamedEvents dataset of the Real-Time Events GraphQL API. Replace the dates with a range that covers the activation of the stream:

Shell
01curl -X POST 'https://api.azion.com/v4/events/graphql' \
02 -H 'Content-Type: application/json' \
03 -H 'Authorization: Token [TOKEN VALUE]' \
04 -d '{"query":"query { dataStreamedEvents(limit: 20, filter: {tsRange: {begin: \"2026-01-01T12:00:00\", end: \"2026-01-01T12:45:00\"}}, orderBy: [ts_DESC]) { ts endpointType statusCode streamedLines dataStreamed } }"}'

The API answers 200 with one record for each send, the latest first:

JSON
01{
02 "data": {
03 "dataStreamedEvents": [
04 {
05 "ts": "2026-01-01T12:02:04Z",
06 "endpointType": "ELASTICSEARCH",
07 "statusCode": 200,
08 "streamedLines": 2,
09 "dataStreamed": 2797
10 }
11 ]
12 }
13}

For a stream that sends to Elasticsearch, endpointType reads ELASTICSEARCH. A statusCode of 200 means the endpoint accepted the batch, and streamedLines and dataStreamed give its size in log lines and bytes. An empty dataStreamedEvents list means the stream has not sent in the range. For every field, refer to Real-Time Events GraphQL fields.

To find the sends in Azion Console:

Open Real-Time Events

Access Azion Console > Real-Time Events.

Select the Data Stream data source
Read the latest sends

Each row is one send. Find the rows with ELASTICSEARCH in Endpoint Type, and read their Status Code.

A Status Code of 200 means the instance accepted the batch. Streamed Lines gives the number of log lines in the batch.

A status other than 200 is the answer of the endpoint, and 503 means Data Stream found the endpoint unavailable. For the causes, refer to Troubleshoot Data Stream.

Next steps

EndpointsEvery field of the Elasticsearch endpoint, with its type, bounds, and API name.Edit, stop, or delete a streamChange the URL or the API key, pause the stream, or remove it.Troubleshoot Data StreamFind what to change when a send returns a status other than 200.Stream WAF events to a SIEMSend the WAF events of a firewall to the SIEM of your choice.