Key Attributes
Object Relationships
The Log Summary object connects several other entities in the Byteful system:- Customer: Each log summary is associated with a specific customer account
- Proxy User: Log summaries track usage for specific proxy users
- Logs: Raw logs are aggregated into log summaries
- Residential Ledger: Both log summaries and residential ledger track data usage, but serve different purposes (analytics vs. billing)
- Mobile Ledger: Both log summaries and mobile ledger track data usage, but serve different purposes (analytics vs. billing)
Related Endpoints
Data Retention and Analytics
Log Summaries follow a tiered retention and aggregation policy:- First 90 days: Organized by
proxy_user_id,network, andhostname - After 90 days: Further consolidated to just
proxy_user_idandnetworklevel (hostname details are removed) - Long-term storage: Maintained indefinitely but with reduced granularity
- Analytics Integration: The
/analytics/graphendpoint processes data from both raw logs and log summaries, providing comprehensive analytics regardless of data age
Usage Notes
- Log Summaries are automatically generated daily for active proxy users
- They provide a more efficient way to analyze usage trends compared to raw logs
- The
log_summary_hostnamefield is only available for summaries less than 90 days old - For residential/mobile proxies, the
log_summary_bytesdirectly correlates with data consumption - Use the
/analytics/graphendpoint for visualizing log summary data over time with flexible time intervals (minute, hour, day, month) - Log Summaries and Residential/Mobile Ledgers track related data but serve different purposes:
- Log Summaries focus on usage patterns and analytics across all proxy types
- Residential/Mobile Ledgers specifically tracks data changes for billing purposes
- While not directly linked, the data from both should reconcile in aggregate

