Log streaming: OpenStack

      Last updated November 06, 2019

    Fastly's Real-Time Log Streaming feature can send log files to OpenStack. OpenStack is an open-source platform for cloud-computing that many companies deploy as an infrastructure-as-a-service.

    Adding OpenStack as a logging endpoint

    Follow these instructions to add OpenStack as a logging endpoint:

    1. Review the information in our Setting Up Remote Log Streaming guide.
    2. Click the OpenStack Create endpoint button. The Create an OpenStack endpoint page appears.

      New OpenStack Endpoint page

    3. Fill out the Create an OpenStack endpoint fields as follows:
      • In the Name field, enter a human-readable name for the endpoint.
      • In the Log format field, optionally enter an Apache-style string or VCL variables to use for log formatting. The Apache Common Log format string appears in this field by default. Our discussion of format strings provides more information.
      • In the Timestamp format field, optionally enter a timestamp format for log files. The default is an strftime compatible string. Our guide on changing where log files are written provides more information.
      • In the Auth URL field, type the URL used for OpenStack authentication (e.g., https://auth.api.rackspacecloud.com/v1.0).
      • In the Bucket name field, type the name of the OpenStack bucket in which to store the logs.
      • In the User field, type your OpenStack username.
      • In the Access Key field, type your OpenStack access key.
      • In the Period field, optionally enter an interval (in seconds) to control how frequently your log files are rotated. This value defaults to 3600 seconds.
    4. Click the Advanced options link of the Create a new OpenStack endpoint page and decide which of the optional fields to change, if any.

      the advanced options on the create an OpenStack endpoint page

    5. Fill out the Advanced options of the Create an OpenStack endpoint page as follows:
      • In the Path field, optionally enter the path within the bucket to store the files. The path ends with a trailing slash. If this field is left empty, the files will be saved in the bucket's root path. Our guide on changing where log files are written provides more information.
      • In the PGP public key field, optionally enter a PGP public key that Fastly will use to encrypt your log files before writing them to disk. You will only be able to read the contents by decrypting them with your private key. The PGP key should be in PEM (Privacy-Enhanced Mail) format. See our guide on log encryption for more information.
      • In the Select a log line format area, select the log line format for your log messages. Our guide on changing log line formats provides more information.
      • In the Placement area, select where the logging call should be placed in the generated VCL. Valid values are Format Version Default, None, and waf_debug (waf_debug_log). Selecting None creates a logging object that can only be used in custom VCL. See our guide on WAF logging for more information about waf_debug_log.
      • In the Compression field, optionally select the compression format you want applied to the log files. Our guide on changing log compression options provides more information.
    6. Click the Create button to create the new logging endpoint.
    7. Click the Activate button to deploy your configuration changes.
    Back to Top