High-Volume AEM CS CDN Log Analysis, Fully In-Browser.

AEM CS CDN Log Analyzer

Upload an xxx.log.gz (or plain .log) file. Analysis stays in your browser and processes logs line by line for reliable, memory-safe insights at scale.

Upload and Analyze

Choose a .log.gz or .log file to begin.

Brief Overview

CDN Log Overview

AEM as a Cloud Service provides CDN publish logs for analysis tasks such as cache hit ratio optimization. The CDN log format is JSON-based and this tool does not support any other log format.

Example Log Line

{
  "timestamp": "2023-05-26T09:20:01+0000",
  "ttfb": 19,
  "cli_ip": "147.160.230.112",
  "cli_country": "CH",
  "rid": "974e67f6",
  "req_ua": "Mozilla/5.0 ... Safari/605.1.15",
  "host": "example.com",
  "url": "/content/hello.png",
  "method": "GET",
  "res_ctype": "image/png",
  "cache": "PASS",
  "status": 200,
  "res_age": 0,
  "pop": "PAR",
  "rules": "match=...,waf=SQLI,action=blocked"
}

Log Fields

Field Name Description
timestampTime the request started after TLS termination.
ttfbTime To First Byte.
cli_ipClient IP address.
cli_country Two-letter ISO 3166-1 alpha-2 country code.
ridRequest identifier used to uniquely identify the request.
req_uaUser-Agent responsible for the HTTP request.
hostRequest authority/host.
urlFull path including query parameters.
methodHTTP method (GET, POST, etc.).
res_ctypeResponse Content-Type.
cacheCache state: HIT, MISS, or PASS.
statusHTTP status code.
res_ageAge of cached response in seconds.
popCDN datacenter / point-of-presence.
rules Matched traffic filter / WAF rule metadata, including block actions when applicable.

CDN logs can also be extended with custom properties using request/response transformations.

Optimizing CDN Cache Configuration

After analyzing your CDN logs, tune cache rules to improve site performance. AEM best practice is to target a cache hit ratio of 90% or higher for cacheable traffic.

Optimize CDN Cache Configuration