Log streaming
How log streaming works, how to connect it, where we can send data, and in which format.
|
This feature is not available in the UI and is connected on request. It is available only in Anti-bot mode. |
What this feature is
Log streaming sends protection logs to your infrastructure in real time.
How it works. For every request to your web resource, the system creates a log with 20 parameters. It immediately sends the log to the selected receiving endpoint, such as your Kafka cluster or rsyslog receiver.
Who it is useful for. It is useful for customers who want to store logs for a long time, upload them to a SIEM or other monitoring systems, combine them with logs from other sources, or create their own dashboards and alerts.
Key characteristics
-
Secure log transfer is supported with TLS and mTLS.
-
The feature is available only in Anti-bot mode. It is not available in Anti-DDoS mode.
-
This is streaming, not an archive export. Logs are sent in real time, and buffering is not supported. If a log is not delivered at the time of sending, it is not sent later.
Where and how we can send logs
We can send logs to the following receiving endpoints:
-
Kafka in JSON format.
-
An rsyslog receiver in syslog format. Supported protocols: UDP, TCP, TCP + TLS, and TCP + mTLS.
-
A non-standard receiving endpoint. On request, we can discuss a custom arrangement, such as sending logs to S3-compatible storage on your side.
|
We usually send logs over the public network. If our networks directly connect to yours, we can agree to send logs over that internal network connection rather than over the internet. |
Log format
We can send logs in two formats: JSON and syslog. Examples are below.
{
"sid": 29201,
"datetime": 1774275547619,
"scheme": "https",
"host": "example.com",
"remote_addr": "203.0.113.42",
"request": "POST /api/example-endpoint HTTP/2.0",
"referrer": "https://example.com/",
"user_agent": "ExampleApp|4.103.0|Android|16|Example Device",
"cookie": "device_id=example-device-id; classification=human; theme=dark",
"forwarded_for": "198.51.100.24",
"uniq_id": "8Jd0WBgEkqM3",
"score": "human",
"action": "pass",
"reason": "mobile_app",
"profile_name": "example_profile",
"type": "script",
"ja3": "d06ad0468c9ca5743014ff08b66bfc83",
"geo": "DE",
"asn": 64500,
"subnet": "203.0.113.0/24"
}
<134> 2026-03-23T13:55:33Z cdm2 strictera-test[1748630]: 29201,1774275547619,https,example.com,203.0.113.42,POST /api/example-endpoint HTTP/2.0,https://example.com/,ExampleApp|4.103.0|Android|16|Example Device,device_id=example-device-id; classification=human; theme=dark,198.51.100.24,8Jd0WBgEkqM3,human,pass,mobile_app,example_profile,script,d06ad0468c9ca5743014ff08b66bfc83,DE,64500,203.0.113.0/24
|
These examples contain all possible log fields. When connecting the feature, you choose which fields to include in the export. |
Field descriptions
| Field | Description | JSON example | syslog example |
|---|---|---|---|
|
The ID of the resource to which the request was sent. |
|
|
|
The exact time when protection received the request, as a Unix timestamp in milliseconds. |
|
|
|
The URL scheme, or the protocol that the client used to access the resource.
|
|
|
|
The hostname to which the request was sent. |
|
|
|
The request source IP address. |
|
|
|
The HTTP request start line: method, path, and HTTP version. |
|
|
|
The value of the HTTP Referer header. |
|
|
|
The value of the HTTP User-Agent header. |
|
|
|
The value of the HTTP Cookie header. |
|
|
|
The value of the X-Forwarded-For header. |
|
|
|
A unique request ID assigned by the system. |
|
|
|
The class assigned to the request source after analysis.
|
|
|
|
The action protection applied to the request.
|
|
|
|
Why protection applied the
|
|
|
|
If a custom rule was applied to the request, this field contains its ID. If no custom rule was applied, this field contains the name of the triggered profile. A profile is a set of filtering settings. It is an internal service variable: we group protection settings for your resource into separate profiles and assign names to them. |
|
|
|
The requested content type, either static or dynamic.
|
|
|
|
The JA3 fingerprint hash. |
|
|
|
The request source country identified from the IP address. |
|
|
|
The number of the autonomous system that owns the source IP address. |
|
|
|
The subnet that contains the source IP address. |
|
|
Connect log streaming
1. Contact support.
Tell support that you want to connect log streaming.
2. Send us connection details.
To write to Kafka, send us:
-
Broker addresses and ports.
-
The name of the topic to which logs must be written.
-
For a TLS connection, the CA certificate in PEM format that we use to connect to you.
-
For an mTLS connection, the CA certificate and certificate-key pair in PEM format that we use to connect to you.
-
If authorization is enabled, create an account for us and send its username and password.
If access to Kafka is limited by a firewall, ask support for the current Strictera IP addresses that you need to allow.
To write to rsyslog, send us:
-
The address.
-
The port.
-
The tag.
-
The protocol: TCP, UDP, TCP + TLS, or TCP + mTLS.
-
For TCP with TLS, the CA certificate in PEM format that we use to connect to you.
-
For TCP with mTLS, the CA certificate and certificate-key pair in PEM format that we use to connect to you.
|
We can also discuss custom options, such as exporting logs to S3-compatible storage. Contact support if this is relevant to you. |
3. Send the list of fields you need.
Specify which fields you want to receive in the logs. See the complete list in Field descriptions above.
|
If storage space is important, we recommend excluding the |
4. Wait for the configuration to be ready.
We need some time to configure log streaming. Configuration is performed during business hours. We will notify you as soon as it is ready.
5. Confirm that you want to connect the service.
After you confirm, we start sending logs.