Real-time Logs
Introduction
Real-time logs provide detailed insights into the interactions between client requests and server responses. They are generated and uploaded in batches every 30s. Once processed, you can access them directly in the Client Panel and a dedicated S3 bucket.
The main purpose is to provide near-immediate visibility into system activities for the given content of a specific CDN Resource or multiple CDN Resources. This helps to quickly analyze statistics, detect anomalies, and resolve issues before they are escalated into major incidents.
Setup
If our Real-time logs aren’t accessible already to you, please contact our team at support@cdn77.com so we may permit access to the new feature. Once this feature is enabled on your CDN77 account, simply log into the Client Panel and click Traffic logs on the side navigation bar, then select Real-time logs.
- First, you will be prompted to create a new dedicated object storage for the Real-time logs.
2. Once created, navigate back to the Real-time logs page and click the Create new log configuration button in the top right corner. Choose the log configuration with your preferred Log format (TSV, CSV, JSON)
3. You will receive a confirmation with the Bucket and Folder location within a dedicated CDN77 Object Storage. Please note that the logs generated in a gzip file within these folders will be accessible for 30 days, after which they will be deleted.
4. After setup is complete we will start collecting the logs. You may view the most recently logged request lines directly in the CDN77 Client Panel by navigating to the Real-time Logs section, then clicking on the ellipsis for the desired Log configuration and select View log configuration. This section will show the last 300 requests, or all requests in the last one hour, depending on which limit is hit first.
5. Full logs are also batched and uploaded to the object storage as a gzip file for deeper analysis.
Pricing
Real-time logs are stored in the EU-1 cluster (HDD, located in Prague, Czech Republic).
- Real-time logs are stored on CDN77 Object Storage, standard CDN77 Object Storage pricing applies, and can be viewed here.
- The initial cost for CDN77 Real-time log is $100/month per account, which includes 5 billion log requests.
- Anything beyond that is priced at $0.02 per million log requests.
Log Fields
| Description | |
|---|---|
startTimeMsinteger | Unix timestamp at which the edge received a request from the client. |
locationIDstring | Server location in the following format city name & country code (e.g. pragueCZ, frankfurtDE, losangelesUSCA, vancouverCABC) |
tcpRTTusinteger | TCP round-trip time for the initial request on a connection in microseconds. |
cacheAgeinteger | Time in seconds that the requested content has been stored in the cache. |
cacheStatusstring | Indicates whether the request was served from cache (HIT/MISS/EXPIRED). |
timestampstring | The exact timestamp of when the request was logged in UTC +0. |
timeToFirstByteMsinteger | The time (in milliseconds) it takes from the moment our edge server receives a request to the first response byte sent. |
clientIPstring | The IP address of the requesting client. |
clientPortinteger | The source port of the client making the request. |
serverIPstring | The IP address of the edge server handling the request. |
serverPortinteger | The port on which the edge server is receiving the request. |
clientRequestBytesinteger | The total number of bytes sent by the client in the request. |
clientRequestProtocolstring | The protocol version used in the request (e.g., HTTP/1.1, HTTP/2, HTTP/3). |
clientRequestSchemestring | The request scheme (http or https). |
clientRequestHoststring | The host/domain the client requested. |
clientRequestMethodstring | The HTTP method used (GET, POST, etc.). |
clientRequestPathstring | The requested URL path, including query parameters. |
clientRequestRangestring | The Range header value, if the client requested partial content. |
clientRequestCompletedboolean | Indicates whether the client request was fully completed (true/false). |
clientRequestConnTimeoutboolean | Indicates whether the connection from the server to the client has timed out or not. |
clientRequestServerPushboolean | Indicates if the request was initiated via HTTP/2 Server Push. |
responseStatusinteger | The HTTP status code returned in response (200, 404, etc.). |
clientSSLProtocolstring | The SSL/TLS protocol version used in the request. |
clientSSLCipherstring | The encryption cipher used for the SSL/TLS connection. |
clientSSLFlagsinteger | Indicates if SSL session was reused. 0 for no; 1 for yes. |
clientRequestRefererstring | Represents the Referer header value in the client’s request. |
clientRequestAcceptstring | Represents the Accept header value in the client’s request. |
clientRequestUserAgentstring | User agent reported by the client. |
clientRequestContentTypestring | The Content-Type header in the request, indicating the data format sent by the client. |
clientRequestViastring | Represents the Via header value in the client’s request. |
clientRequestXForwardedForstring | Represents the X-Forwarded-For header value in the client’s request. |
responseBytesinteger | The total number of bytes sent by the server in the response. |
responseContentTypestring | The Content-Type header in the response, indicating the data format sent by the server. |
responseContentEncodingstring | The encoding applied to the response. NONE means no compression. |
responseContentRangestring | The Content-Range header value, if the response is a partial content delivery. |
clientCountrystring | 2-letter ISO-3166 country code of the client IP address. |
clientASNinteger | The Autonomous System Number (ASN) associated with the client’s IP. |
resourceIDinteger | A unique ID of the CDN77 Resource. |
Updated on 31st March, 2025