Menu

Lumen help

Adding a log-streaming endpoint definition to a configuration

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.

Note: 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.

  1. From the main menu, select My Services > Caching. 
My Service - Caching
  1. From the lists, select the access group and SCID (service component ID) you want to work with. 
My Services - Caching (with SCID selected)
  1. From the list, select the configuration. 

To add a log-streaming endpoint definition to a configuration:

  1. From an open configuration, click Edit Configuration.
my services caching edit configuration
  1. In the Service-Wide Definition section, click Log Streaming Endpoints.

    Media portal lists the log-streaming endpoint definitions for the configuration (if any).
my services caching add configuration log streaming endpoints new definition
  1. Click New Definition.
my services caching add configuration geo regions new definition with definition name and two countries added
  1. Type a name for the definition. (You can leave the auto-generated name or type a name more meaningful to you.)
  1. Fill in the information for the definition:

    1. From the Log Format list, select the format you want the log to use: JSON_Newline or JSON_Array.

    2. If you want to check whether the presented certificate CN (common name) matches the hostname, select the Validate Certificate checkbox.

    3. From the Protocol list, select the protocol you want to use to deliver the logs.

    4. In the Host field, type the hostname of the remote server.

    5. In the Port field, type the port the remote server is listening on.

    6. In the Max Bites per Message field, type the maximum number of bytes of log data that will be sent in each post.

    7. In the Path field, type the path where the logs will be placed on the remote server.

    8. 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).

    9. In the Connections field, select the number of connections.

    10. To create custom headers to be added to the requests, click Add, then type the name and value for the request header.

    11. To add additional headers, repeat step j.
  1. If you need to edit or add other definitions, continue editing the configuration without saving. (Saving the configuration creates a new version.) When you're done editing the configuration, continue with step 7.
  1. Click Save (above the Service-Wide Definition section). You can also click Save As to save the configuration under a new name.
  1. If needed, make any notes to describe the changes you made.
  1. Click Save again.

    Media portal saves the configuration with the new definition.