> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/edgesight/logpush/field-reference.md).

# Field Reference

Review the available log fields you can include in Real-Time Logpush exports.

Real-Time Logpush allows you to select custom fields to include in your exported logs.\
Fields are grouped by category to help you identify which data points are relevant for performance analysis, debugging, or analytics integration.

Each field represents a specific CDN request or response attribute processed by Medianova’s edge servers.

All logs are delivered in **JSON Lines (`.jsonl`)** format, with each field represented as a key–value pair.

### **Request Details**

| **Field Name**    | **Description**                                |
| ----------------- | ---------------------------------------------- |
| `request_id`      | Unique identifier assigned to each request.    |
| `request_method`  | HTTP method used (GET, POST, etc.).            |
| `request_uri`     | Requested URI including path and query string. |
| `request_param`   | Query parameters sent with the request.        |
| `request_time`    | Total processing time of the request (s).      |
| `scheme`          | Request protocol used (`http` or `https`).     |
| `http_protocol`   | HTTP version (e.g., HTTP/1.1, HTTP/2).         |
| `http_host`       | Value of the Host header.                      |
| `http_referrer`   | Referrer URL sent by the client.               |
| `http_user_agent` | Browser or client user agent.                  |

### **Response & Caching**

| **Field Name**             | **Description**                             |
| -------------------------- | ------------------------------------------- |
| `status`                   | HTTP response status code.                  |
| `content_type`             | MIME type of the response.                  |
| `proxy_cache_status`       | Cache status (HIT, MISS, BYPASS, EXPIRED).  |
| `body_bytes_sent`          | Number of bytes sent in the response body.  |
| `bytes_sent`               | Total bytes sent from CDN to the client.    |
| `upstream_response_time`   | Time taken by origin to respond (s).        |
| `sent_http_content_length` | Length of the response body sent to client. |
| `via`                      | Value of the Via HTTP header.               |

### **Client & Network**

| **Field Name**     | **Description**                               |
| ------------------ | --------------------------------------------- |
| `remote_addr`      | IP address of the client.                     |
| `client_port`      | Source port used by the client.               |
| `asn`              | Autonomous System Number of the client’s ISP. |
| `country_code`     | ISO country code of the client IP.            |
| `isp`              | Internet Service Provider name.               |
| `tcp_info_rtt`     | TCP round-trip time in milliseconds.          |
| `tcp_info_rtt_var` | Variance of TCP round-trip time.              |

### **Security & SSL**

| **Field Name**  | **Description**                      |
| --------------- | ------------------------------------ |
| `ssl_protocol`  | TLS/SSL protocol used.               |
| `ssl_cipher`    | Cipher suite used during handshake.  |
| `resource_uuid` | Unique ID of the CDN resource.       |
| `account_type`  | Account type that owns the resource. |

### **Log Format**

* **File Type:** `.jsonl.gz`
* **Format:** JSON Lines (one request per line)
* **Encoding:** UTF-8
* **Compression:** Gzip
* **Timestamp:** UTC-based (ISO 8601)
* **Delivery Interval:** Every 5 minutes or when file size reaches 5 MB (HTTP) or 50 MB (other destinations)

{% hint style="info" %}
Each `.jsonl.gz` file may contain thousands of log lines, each representing a unique CDN transaction.
{% endhint %}

### **Sample Log Entry**

```json
{
  "account_type": "enterprise",
  "asn": "AS9121",
  "body_bytes_sent": "22535",
  "bytes_sent": "22820",
  "country_code": "TR",
  "http_host": "cdn-medianova.mncdn.com",
  "http_protocol": "HTTP/2.0",
  "proxy_cache_status": "HIT",
  "remote_addr": "1.1.1.1",
  "request_id": "17ba51b735147390088a628eb7f757e9",
  "request_method": "GET",
  "request_uri": "/PROD_REPOSITORY/",
  "resource_uuid": "80bdb1b4-63a2-bd0c60c4e2e0",
  "status": "200",
  "timestamp": "2025-04-13T23:56:32Z",
  "upstream_response_time": "0.12"
}
```

### **Validate a Log File**

Use standard CLI tools to check integrity and content of `.jsonl.gz` files:

```bash
# Decompress and preview
gunzip -c logs-2025-04-13-23-55.jsonl.gz | head -n 3

# Validate JSON structure
jq empty logs-2025-04-13-23-55.jsonl
```

{% hint style="info" %}
For extended schema mapping or advanced analytics integration, contact [Medianova Technical Support](/support-and-troubleshooting/contacting-customer-support.md)
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://clients.medianova.com/products/edgesight/logpush/field-reference.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.