Compute@Edge log streaming: OpenStack

Fastly's Real-Time Log Streaming feature for Compute@Edge services 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 guide to setting up remote log streaming for Compute@Edge. Additionally, our developer documentation provides more information about logging with Compute@Edge code written in Rust, AssemblyScript, and JavaScript.
2. Click the OpenStack Create endpoint button. The Create an OpenStack endpoint page appears.
3. Fill out the Create an OpenStack endpoint fields as follows:
   • In the Name field, enter the endpoint name you specified in your Compute@Edge code. For example, in our Rust code example, the name is my_endpoint_name.
   • 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, enter the URL used for OpenStack authentication (e.g., https://auth.api.rackspacecloud.com/v1.0).
   • In the Bucket name field, enter the name of the OpenStack bucket in which to store the logs.
   • In the User field, enter your OpenStack username.
   • In the Access Key field, enter your OpenStack access key.
   • In the Period field, optionally enter an interval (in seconds) to control how frequently your log files are rotated. Rotation entails the finalization of one file object and the start of a new one, never removing any previously created file object. 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.
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. Read 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 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.