Use log-streaming endpoint definitions to specify when, where, and how you want log streaming information posted to your endpoint. Logs are batched in a JSON-formatted payload and posted to your endpoint in near real time (<5 minutes). You can add a log-streaming endpoint definition only if you've purchased Log Streaming. If you feel you should have access to this feature and don't, open a ticket with CDN Operations.
Please note that If you have large traffic volumes, be sure your endpoint can handle a large amount of log information. If your endpoint can't handle the volume, you may lose log data because the Lumen log-processing system only queues logs for a short period of time if your endpoint is unavailable or unable to keep up.
From the “Log Format” list, select the format you want the log to use: “JSON_Newline” or “JSON_Array”. If you want to check whether the presented certificate CN (common name) matches the hostname, select the “Validate Certificate” checkbox. From the “Protocol” list, select the protocol you want to use to deliver the logs. In the “Host” and “Port” field, type the hostname and port of the remote server respectively. In the “Max Bites per Message” field, type the maximum number of bytes of log data that will be sent in each post. In the “Path” field, type the path where the logs will be placed on the remote server. In the “Max Post Interval” field, type the maximum time the system will hold logs until they are sent to the remote server (if the log hasn't yet reached the number of bytes you specified above). In the “Connections” field, select the number of connections. To create custom headers to be added to the requests, click “Add”, then type the name and value for the request header. You can add multiple headers by clicking “Add” again.