Understanding the Log object and its role in the Ping Proxies API
The Log object represents an individual proxy request in the Ping Proxies system. It contains detailed information about proxy usage, including client information, geographic data, request details, and timestamps. Logs provide granular visibility into how your proxies are being utilized and are crucial for troubleshooting, usage analysis, and security monitoring.
Attribute | Type | Description |
---|---|---|
log_id | string | Unique identifier for the log entry |
proxy_user_id | string | ID of the proxy user that made the request |
service_id | string | ID of the service associated with the proxy |
log_network | string | Network type (datacenter, isp, residential) |
log_protocol | string | Protocol used (http, socks) |
log_hostname | string | The target domain of the request |
log_client_ip_address | string | IP address of the client that made the request |
log_total_bytes | integer | Total data transferred in bytes |
log_request_datetime | datetime | When the request was made |
log_authentication_type | integer | Authentication method used |
log_session_id | string | Session identifier for tracking related requests |
country_id | string | Country code where the request was processed |
city_alias | string | City identifier where the request was processed |
asn_id | integer | ASN (Autonomous System Number) identifier |
Raw logs are stored for a limited time period:
log_summary
objects when createdlog_summary
objectsThe Log object is connected to several other objects in the Ping Proxies system.
Endpoint | Description |
---|---|
GET /public/user/log/search | Search logs with various filters |
GET /public/user/log/retrieve/{log_id} | Retrieve a specific log entry |
GET /public/user/analytics/graph | Graph data derived from logs |
residential_ledger
log_summary
objects which retain aggregated data for 90+ days