GET
/
cdn
/
advanced
/
v1
/
logs
Get CDN logs
curl --request GET \
  --url https://api.gcore.com/cdn/advanced/v1/logs \
  --header 'Authorization: <api-key>'
{
  "data": [
    {
      "timestamp": 1633914371,
      "client_ip": "1.1.1.1",
      "cname": "test.domain.com",
      "resource_id": 100,
      "path": "/awesome-site",
      "method": "GET",
      "user_agent": "Mozilla/5.0 (compatible; MSIE 6.0; Windows 95; Trident/3.1)",
      "status": 200,
      "size": 17340162,
      "cache_status": "HIT",
      "datacenter": "m9",
      "referer": "https://www.test.com/",
      "sent_http_content_type": "image/jpeg",
      "tcpinfo_rtt": 70
    }
  ],
  "meta": {
    "count": 129874732
  }
}

Authorizations

​
Authorization
string
header
required

API key for authentication. Make sure to include the word apikey, followed by a single space and then your token. Example: apikey 1234$abcdef

Query Parameters

​
from
string
required

Start date and time of the requested time period (ISO 8601/RFC 3339 format, UTC.) Difference between "from" and "to" cannot exceed 6 hours. Examples: * &from=2021-06-14T00:00:00Z * &from=2021-06-14T00:00:00.000Z

​
to
string
required

End date and time of the requested time period (ISO 8601/RFC 3339 format, UTC.) Difference between "from" and "to" cannot exceed 6 hours. Examples: * &to=2021-06-15T00:00:00Z * &to=2021-06-15T00:00:00.000Z

​
offset
integer
default:0

Number of log records to skip starting from the beginning of the requested period.

​
limit
integer
default:100

Maximum number of log records in the response.

Required range: 1 <= x <= 1000
​
<field>__<op>
string

Field to which the filter is applied and the operator to be applied. In case of multiple values specified, the filters will be combined using the AND operator. Possible values:

  • method - Request HTTP method. Possible values: 'CONNECT', 'DELETE', 'GET', 'HEAD', 'OPTIONS', 'PATCH', 'POST', 'PUT', 'TRACE'. Operations: eq, ne, in, not_in. Multiple values for 'in' & 'not_in' are separated by a comma.
  • client_ip - IP address of the client who sent the request. Operations: eq, ne, in, not_in.
  • status - Status code in the response. Possible values: integer. Operations: gt, gte, lt, lte, eq, ne, in, not_in. Multiple values for 'in' & 'not_in' are separated by a comma.
  • size - Response size in bytes. Possible values: integer. Operations: gt, gte, lt, lte, eq, ne, in, not_in. Multiple values for 'in' & 'not_in' are separated by a comma.
  • cname - Custom domain of the requested CDN resource. Operations: eq, ne, in, not_in, contains. For the 'contains' operation, the minimum length of the value is 3 characters.
  • resource_id - ID of the requested CDN resource. Possible values: integer. Operations: gt, gte, lt, lte, eq, ne, in, not_in. Multiple values for 'in' & 'not_in' are separated with comma.
  • cache_status - Caching status. Possible values: 'MISS', 'BYPASS', 'EXPIRED', 'STALE', 'PENDING', 'UPDATING', 'REVALIDATED', 'HIT', '-'. Operations: eq, ne, in, not_in. Multiple values for 'in' & 'not_in' are separated by a comma.
  • datacenter - Data center where request was processed. Operations: eq, ne, in, not_in, contains. To filter the CDN logs by 2xx status codes, use: * &status__gte=200&status__lt=300
​
ordering
string

Sorting rules. Possible values:

  • method - Request HTTP method.
  • client_ip - IP address of the client who sent the request.
  • status - Status code in the response.
  • size - Response size in bytes.
  • cname - Custom domain of the requested resource.
  • resource_id - ID of the requested CDN resource.
  • cache_status - Caching status.
  • datacenter - Data center where request was processed.
  • timestamp - Date and time when the request was made. Parameter may have multiple values separated by a comma. By default, ascending sorting is applied. To sort in descending order, add '-' prefix. Example: * &ordering=-timestamp,status
​
fields
string
default:timestamp,path,method,referer,user_agent,client_ip,status,size,cname,resource_id,cache_status,datacenter,sent_http_content_type,tcpinfo_rtt

A comma-separated list of returned fields. Supported fields are presented in the responses section. Example: * &fields=timestamp,path,status

Response

200 - application/json

Successful.

The response is of type object.