--- name: azion-send-logs-to-an-http-endpoint description: >- Create a stream that sends the logs of your applications to an HTTP or HTTPS URL, in Azion Console or with the Azion API, and confirm the delivery. --- # Send logs to an HTTP endpoint You can send the logs of a stream to any URL that receives HTTP or HTTPS `POST` requests from Azion Console or with the Azion API. To change the body of each request, such as to send a JSON array, refer to [Customize the HTTP POST payload](/en/documentation/guides/platform/observability/data-stream-set-payload/). [Data Stream](/en/documentation/platform/data-stream/) sends the log lines of each batch in the body of `POST` requests to your URL. In the stream form, the endpoint is set in the field labeled **Connector**, and the HTTP endpoint is its *Standard HTTP/HTTPS POST* option. Use it for a platform that has no option of its own in that list. For every field and its bounds, refer to [Endpoints](/en/documentation/platform/data-stream/endpoints/#standard-httphttps-post). 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](/en/documentation/platform/data-stream/stream-settings/#permissions). - A [workload](/en/documentation/platform/workloads/) on the account that receives requests. - The URL that receives the logs. It must start with `http://` or `https://` and accept `POST` requests. - The headers your platform requires to accept the requests, such as an access key. Data Stream sends them with every request. - An endpoint that receives each batch within 20 seconds. After 20 seconds, the send ends with status `504`. For the timeout, refer to [Data Stream limits](/en/documentation/platform/data-stream/limits/#default-limits). **Console** - Access to Azion Console. To sign in, refer to [How to access Azion Console](/en/documentation/guides/platform/account-and-billing/how-to-access-azion-console/). **API** - A personal token. To create one, refer to [How to manage a personal token](/en/documentation/guides/platform/account-and-billing/personal-tokens/). - The ID of the workload. - `curl`. --- ## Create the stream The stream collects from the workload you choose, through a workload filter. Unlike sampling, a workload filter leaves your other streams active. **Console** To create the stream in Azion Console: 1. **Open Data Stream** Access [Azion Console](https://console.azion.com/) > **Data Stream**. 2. **Select + Stream** 3. **Name the stream** In the **General** section, enter a **Name**. For example: `logs-to-http`. 4. **Select the data source** In the **Input** section, select *Applications* in **Data Source**. 5. **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. 6. **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. 7. **Select the template** In the **Render Template** section, select *Applications Event Collector* in **Template**. 8. **Select the HTTP endpoint** In the **Output** section, select *Standard HTTP/HTTPS POST* in **Connector**. It is the default option. 9. **Enter the URL** In **URL**, enter the URL that receives the logs. For example: `https://logs.example.com/ingest`. 10. **Keep the payload settings** Keep `$dataset` in **Payload Format**, `\n` in **Payload Log Line Separator**, and `1000000` in **Payload Max Size**. With these values, the endpoint receives one log line per line, in NDJSON format. 11. **Enter the headers** In **Custom Headers**, enter one header in the **Header** field, written `header-name:value`. For example: `Authorization:Bearer [API KEY]`. The Console requires at least one header. To add another one, select **Header**. The Console takes up to five headers. 12. **Keep the stream active** In the **Status** section, keep **Active** turned on. 13. **Select Save** The Console shows `Your data stream has been created`. The stream appears in the **Data Stream** list with `HTTP` in the **Connector** column and the **Active** status. **API** 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, `` with the ID of your workload, and the URL and the header with your own: ```bash curl -X POST 'https://api.azion.com/v4/workspace/stream/streams' \ -H 'Content-Type: application/json' \ -H 'Authorization: Token [TOKEN VALUE]' \ -d '{ "name": "logs-to-http", "active": true, "inputs": [ { "type": "raw_logs", "attributes": { "data_source": "workloads" } } ], "transform": [ { "type": "filter_workloads", "attributes": { "workloads": [] } }, { "type": "render_template", "attributes": { "template": 2 } } ], "outputs": [ { "type": "standard", "attributes": { "url": "https://logs.example.com/ingest", "headers": { "Authorization": "Bearer [API KEY]" }, "log_line_separator": "\\n", "payload_format": "$dataset", "max_size": 1000000 } } ] }' ``` The `workloads` data source is *Applications* in the Console, and template `2` is *Applications Event Collector*. The API requires the `headers` key: to send no header, set it to `{}`. The API answers `201` with the stored stream: ```json { "state": "executed", "data": { "id": 12347, "name": "logs-to-http", "last_editor": "user@example.com", "created": "2026-01-01T12:10:22.000000Z", "last_modified": "2026-01-01T12:10:22.000000Z", "product_version": "1.0", … "outputs": [ { "type": "standard", "attributes": { "url": "https://logs.example.com/ingest", "log_line_separator": "\\n", "payload_format": "$dataset", "max_size": 1000000, "headers": { "Authorization": "Bearer [API KEY]" } } } ] } } ``` Keep the `id`: it identifies the stream in every later request, such as `/v4/workspace/stream/streams/12347`. A `url` with another scheme is refused with `32006` `Invalid URL Scheme`. For every key of the body, refer to [Stream settings](/en/documentation/platform/data-stream/stream-settings/#stream-object). The API and the Console save the stream without contacting the URL. A wrong URL or header surfaces only when the stream sends. An activation takes effect after one to two minutes. --- ## Confirm the delivery [Real-Time Events](/en/documentation/platform/real-time-events/data-sources/#data-stream) 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. **Console** To find the sends in Azion Console: 1. **Open Real-Time Events** Access [Azion Console](https://console.azion.com/) > **Real-Time Events**. 2. **Select the Data Stream data source** 3. **Read the latest sends** Each row is one send. Find the rows with `HTTP_POST` in **Endpoint Type**, and read their **Status Code**. A **Status Code** of `200` means your endpoint accepted the batch. **Streamed Lines** gives the number of log lines in the batch. **API** 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: ```bash curl -X POST 'https://api.azion.com/v4/events/graphql' \ -H 'Content-Type: application/json' \ -H 'Authorization: Token [TOKEN VALUE]' \ -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 { "data": { "dataStreamedEvents": [ { "ts": "2026-01-01T12:02:04Z", "endpointType": "HTTP_POST", "statusCode": 200, "streamedLines": 2, "dataStreamed": 2797 } ] } } ``` A send to an HTTP endpoint carries `HTTP_POST` in `endpointType`. A `statusCode` of `200` means your 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](/en/documentation/devtools/graphql/gql-real-time-events-fields/#datastreamedevents-data-stream). Any status other than `200` is the answer of your endpoint, with two exceptions. `503` means Data Stream found the endpoint unavailable, and `504` means the endpoint did not receive the batch within 20 seconds. A URL that accepts no `POST` request answers each send with its own error, such as `405`. For the causes, refer to [Troubleshoot Data Stream](/en/documentation/platform/data-stream/troubleshooting/). --- ## Next steps - [Customize the HTTP POST payload](/en/documentation/guides/platform/observability/data-stream-set-payload.md): Send the log lines as a JSON array, or change the separator and the request size. - [Endpoints](/en/documentation/platform/data-stream/endpoints.md#standard-httphttps-post): Every field of the HTTP endpoint, with its type, bounds, and API name. - [Edit, stop, or delete a stream](/en/documentation/guides/platform/observability/delete-data-stream.md): Change the URL or the headers, pause the stream, or remove it. - [Troubleshoot Data Stream](/en/documentation/platform/data-stream/troubleshooting.md): Find what to change when a send returns a status other than 200.