Access to log data requires an Enterprise account. Contact your account manager or our sales department at 1 (866) 200 - 5463 to upgrade your account.
Our access log data describes each request served by Edgio.
- Availability for this log data is only guaranteed for 2 hours.
- Use the following environment-specific data, which is available from the desired environment’s Logs tab, to access log data:
- Base AWS S3 bucket URL
- Key ID
- Secret access key

Access Log Fields
An access log file may contain the following fields:
-
er (Number): Indicates whether we sent a custom response as a result of the send method. Returns
1
for custom responses and0
for all other responses. -
hrid (String): If the response is served from cache, this field indicates the unique ID of the request whose response was cached. This value matches the ID reported by the
x-edg-hit-request-id
response header. -
t (String): Returns the same value as the xmt access log field.
-
xmt (String): Indicates the value for the x-edg-t response header (e.g.,
eh=4,ect=2,ecc=hit
). Thex-edg-t
response header contains time measurements for each Edgio POP component through which a request was routed. -
xut (String): Indicates the value for the
x-edg-user-t
response header (e.g.,fetch:/path=123
). Thex-edg-user-t
response header contains performance metrics.
Log Aggregation Tools
Edgio temporarily stores log data within Amazon S3. Use a log aggregation tool to extract log data from AWS S3. Here are a few popular log aggregation tools:
- Sematext | [Logagent docs]
- Sumo Logic | [S3 ingest docs]
- AWS Athena | [docs]
- Splunk | [S3 ingest docs]
- Loggly | [S3 ingest docs]