# Logging Overview

The Proxy Network and API creates logs for every single proxy request and API request. These are stored in different objects with different retention and collation policies.

The objects includes in the logging systems:

```
Log
LogSummary
APIRequest

Related Objects include: ResidentialLedger & ProxyUser
```

#### Log Object Types & Definitions

| Object     | Log Type                    |
| ---------- | --------------------------- |
| Log        | Proxy Network Log           |
| LogSummary | Proxy Network Log Collation |
| APIRequest | API Request Log             |

<details>

<summary>Log</summary>

This object represents a single request to our proxy network. Each request is stored as a log for up to 7 days with information such as domain name, proxy user who made the request, status of the request, size of the request.&#x20;

Logs are created for every single Datacenter, Static Residential and Residential Proxy Requests. The network of request is stored as Log.log\_network with `residential` as Residential Proxy, `isp` as Static Residential Proxy and `datacenter` as Static Residential Proxy network respectively.

</details>

<details>

<summary>LogSummary</summary>

This object represents a collation of information from Log objects on a per hour, per network type, per domain, per proxy user basis.

For each ProxyUser accessing each domain for each product type, a summary is created for each hour which summarises all the activity within that hour.

LogSummary objects are never deleted and are used to informe the ResidentialLedger and ProxyUser traffic limits.

<pre class="language-json"><code class="lang-json">{
    "customer_id": 1932,
<strong>    "log_summary_bytes": 10000,
</strong>    "log_summary_creation_datetime": "2023-04-01T14:00:00Z",
    "log_summary_domain": "another-example.com",
    "log_summary_error": 5,
    "log_summary_id": "456e7890-e89b-12d3-a456-426614174000",
    "log_summary_last_update_datetime": "2023-04-02T14:00:00Z",
    "log_summary_network": "residential",
    "log_summary_period": "2023-10-01T00:00:00Z",
    "log_summary_requests": 100,
    "log_summary_successful": 95,
    "proxy_user_id": "proxyuser_002"
}
</code></pre>

</details>

<details>

<summary>APIRequest</summary>

This object represents a single request to our API Each request. APIRequest objects may be deleted after 7 days.

Some important requests such as object edit, cancellations and account changes are retained forever for audit security.&#x20;

</details>

#### Proxy Network Log Attribution / Creation Flow

This example shows a  Log Attribution / Creation Flow for Residential Proxy Network request. Not that for Datacenter and Static Residential Proxy requests the ResidentialLedger actions are not applicable.

<figure><img src="/files/yfurFxEO0WgeuHiSiTun" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://internal.developer.documentation.private.user.pingproxies.com/logs-and-analytics/logging-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.