Compute@Edge log streaming: Cloud Files

Fastly's Real-Time Log Streaming feature for Compute@Edge services can send log file to Cloud Files. Operated by Rackspace, Cloud Files is a file storage service used by developers and IT teams.

Prerequisites

If you don't already have a Rackspace Cloud account, you'll need to register for one. Follow the instructions on Rackspace's website.

Creating a Cloud Files user and container

Start by creating a Cloud Files user with restricted permissions via Rackspace's cloud control panel.

1. Log in to Rackspace's cloud control panel.
2. From the user account menu, select User Management.
3. Click Create User and fill in all appropriate details.
4. In the Product Access section, set User Role to Custom.
5. Review the Product Access list. For all items in the Product column, set Role to No Access except the Files item.
6. Set the Files item Role to Admin. This will allow you to create the files to store the logs in, but not access any other services.

Next, find the API key for your Cloud Files account. You'll use this later to authenticate using the Cloud Files API.

1. From the user account menu, select Account Settings.
2. Show the API key in the Login details and make a note of it.

Now that you've created the Cloud Files user and found the API key, you can set up a Cloud Files container.

1. From the Storage menu, select Files.
2. Click Create Container.
3. Assign the container a meaningful name like Fastly logs - my service.
4. Choose a region to keep the files in and make sure the container is private.
5. Click Create Container.

Adding a Cloud Files logging endpoint

Once you have created the Cloud Files user and container, follow these instructions to add Cloud Files 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 Rackspace Cloud Files Create endpoint button. The Create a Cloud Files endpoint page appears.
3. Fill out the Create a Cloud Files 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 Bucket name field, enter the name of the Cloud Files container in which to store the logs.
   • In the User field, enter the username of the Cloud Files user you created above.
   • In the Access key field, enter the API key of your Cloud Files account.
   • 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 Cloud Files endpoint page and decide which of the optional fields to change, if any.
5. Fill out the Advanced options of the Create a Cloud Files 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.
   • From the Region menu, select the region to stream logs to.
   • 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.