Edgio
Edgio Console

Azure Blob Storage Log Delivery

RTLD may automatically deliver compressed log data to an Azure Blob Storage container by submitting HTTPS PUT requests to it. Each request creates a block blob within the container. This block blob contains a compressed JSON or CSV document that uniquely identifies a set of log data and describes one or more log entries.
Key information:
  • The set of available log fields varies by RTLD module: RTLD CDN | RTLD WAF | RTLD Rate Limiting | RTLD Bot | RTLD Cloud Functions
  • RTLD applies gzip compression to log data. Azure Blob Storage stores compressed log data as an object with a gz file extension.
    Learn more.
  • Setting up log delivery to Azure Blob Storage requires:
    • An existing Azure Blob Storage account.
      Get started.
    • A container to which log data will be uploaded.
    • A base URL that points to your container.
      Blob Container URL: https://Storage Account.blob.core.windows.net/<CONTAINER>
      Sample Blob Container URL: https://myaccount.blob.core.windows.net/mycontainer
    • Either a SAS token or an access key through which our service will authorize requests to upload content to your Azure Blob Storage account.
      If you plan on providing a SAS token, make sure that the token has permission to write to the blob/container. Additionally, it should start with sv= and it should not include a ?.
      Sample SAS token:
      sv=2018-03-28&sr=c&si=myblobReadWritekey1\_123456789012345678&sig=a1bCDefghijklMnOpqrsTuv2wXYzABc3d34efGHIjkL%5M
  • You may define a prefix when setting up a log delivery profile. This prefix defines a virtual log file storage location and/or a prefix that will be pre-pended to the name of each object added to your bucket. Use the following guidelines when setting this prefix:
    • A prefix should not start with a forward slash.
    • A forward slash within the specified prefix is interpreted as a delimiter for a virtual directory.
    • A trailing forward slash means that the specified value only defines a virtual directory path within your bucket where logs will be stored. If the specified value ends in a character other than a forward slash, then the characters specified after the forward slash will be prepended to the file name for each log file uploaded to your destination.
    Sample prefix: logs/CDN/siteA_
    The above prefix will store log files in the following virtual directory: /logs/CDN
    The file name for each log file uploaded to your destination will start with siteA_.
    Sample log file name: siteA_wpc_0001_123_20220111_50550000F98AB95B_1.json
To prepare for log delivery
  1. Create or identify an Azure storage account and a container to which log data will be posted.
    View Microsoft Azure documentation on how to create a storage account.
  2. Identify or configure how requests submitted will be submitted by RTLD will be authorized.
    RTLD supports authorization through a SAS token or an access key.
    If you plan on providing a SAS token, make sure that the token has permission to write to the blob/container. Additionally, it should start with sv= and it should not include a ?.
  3. Upon completing the above steps, you should create a log delivery profile for Azure Blob Storage.
To set up a log delivery profile
  1. From the Real-Time Log Delivery page, click + New Log Delivery Profile and then select the desired type of log field.
    1. Open the desired property.
      1. Select either your private space or a team space.
      2. Click on the desired property.
    2. From the left pane, click on the desired environment.
    3. From the left pane, click Realtime Log Delivery.
    4. Click + New Log Delivery Profile and then select either CDN, WAF, Rate Limiting, Bot, or Cloud Functions.
  2. From the Profile Name option, assign a name to this log delivery profile.
  3. From the Log Delivery Method option, select Azure Blob Storage.
  4. Define how RTLD will communicate with Azure Blob Storage.
    1. Set the Blob Container URL option to a URL that points to the container to which log data will be posted.
    2. Optional. Set the Prefix option to a value that defines a virtual log file storage location and/or a prefix that will be added to each log file added to your container.
      Learn more about prefixes.
    3. From the Access Type option, select whether log data uploads will be authorized via a SAS token or an access key and then paste it in the field below it.
      If you plan on providing a SAS token, make sure that the token has permission to write to the blob/container. Additionally, it should start with sv= and it should not include a ?.
  5. From the Log Format option, select whether to format log data using our standard JSON format, as a JSON array, as JSON lines, or as a CSV (RTLD CDN only).
    Learn more about these formats: RTLD CDN | RTLD WAF | RTLD Rate Limiting | RTLD Bot | RTLD Cloud Functions
  6. From the Downsample the Logs option, determine whether to reduce the amount of log data that will be delivered. For example, you may choose to only deliver 1% of your log data.
    • All Log Data: Verify that the Downsample the Logs option is cleared.
    • Downsampled Log Data: Downsample logs to 0.1%, 1%, 25%, 50%, or 75% of total log data by marking the Downsample the Logs option and then selecting the desired rate from the Downsampling Rate option.
      Use this capability to reduce the amount of data that needs to be processed or stored within your web server(s).
      RTLD CDN Only: Downsampling log data also reduces usage charges for this service.
  7. Determine whether log data will be filtered.
  8. By default, all log fields are enabled on a new log delivery profile. From within the Fields section, clear each field for which log data should not be reported.
  9. Click Create Log Delivery Profile.