Real-time Logs Overview
Feature Overview
After your site accesses EdgeOne, you will obtain abundant pre-built reports that can help you monitor and analyze the operation of your business, including traffic analysis, cache analysis, L4 proxy, security analysis, etc. However, in data analysis, you may have more personalized data analysis demands, such as the following data analysis scenarios:
Scenario | Scenario Demands |
Deep Data Analysis | Specify 1 or more conditions, to search logs that meet the conditions. For example: Specify the client IP, to query the access statistics (access URL, number of accesses, etc.) within a specified time range. Filter by status code, time, and URL, to analyze the detailed distribution of status codes. Filter out the logs processed by observation, and summarize the request header content and other request characteristics carried, to adjust the security policy. |
Monitoring Service Metrics | Analyze the quality of EdgeOne Service and the access efficiency of users, to detect exceptions in a timely manner. The access efficiency includes the overall response time of EdgeOne, download speed, origin-pull response time, etc. |
Identifying Hotlinking | Analyze the traffic exceptions, access modes, and access frequencies, to identify client IPs with behaviors such as hotlinking. |
Unified Monitoring of Data from Multiple Cloud Vendors | Monitor the application data from multiple cloud vendors through a self-built data dashboard. |
Log Storage | Retain user-related access logs for 30 days or longer. |
For the above scenario demands, the EdgeOne real-time log service provides the ability to collect and push logs in real-time. It supports pushing your logs to Tencent Cloud Log Service (CLS) or your self-built data center, and helps you independently perform flexible search and analysis of log data. Currently, EdgeOne supports pushing logs to the following destinations:
Push to Tencent Cloud CLS: Pushes logs to the one-stop Tencent Cloud Log Service (CLS) for further log search and analysis.
Push to AWS S3-Compatible COS: Pushes logs to storage buckets compatible with the authentication method of AWS Signature V4.
Push to HTTP Server: Pushes logs to a specified backend server via HTTP POST requests.
Note:
Under normal circumstances, the latency of log shipping is within 5 minutes. To ensure real-time log shipping, EdgeOne pushes logs to a corresponding destination in batches based on a fixed number of logs or a fixed time period. The default policy is pushing 1,000 log entries per batch preferentially. When the log entries are less than 1,000, but the time interval from the last push is 5 seconds, it will also trigger a second push.
Billing and Quota Description