Logging For Private Cloud Files Containers

Filed in Product & Development by Megan Meza | October 2, 2012 1:45 pm

Cloud Files[1] now offers Access Log Delivery, a feature that allows users to enable logging for non-CDN enabled containers. As you may know, logging for CDN-enabled containers already exists today.

Common use cases include:
Resellers – Many Cloud Files customers separate their customers into containers within Cloud Files. By giving them logs for each of their containers, we give resellers more options for billing their customers.

User Monitoring – Customers sharing an account with multiple users can track which users are accessing their data, which are uploading the most content, etc.  This gives IT departments more information for better serving their customers and possibly identifying problem users.

Access Tracking – Applications built on Cloud Files have a variety of use cases that can benefit from this feature. Logs can be used to track high usage times, user activity, monitor the system and more.

Log Data Examples:
If you enable access log delivery for non-CDN enabled containers, there is a variety of data available. Here are a couple of examples:

Log lines will appear like this: - - [27/08/2012:16:50:22 +0000] "PUT /v1/
     HTTP/1.0" 401 0 "-" "python-requests/0.13.8
     CPython/2.7.3 Linux/3.2.0-29-generic"

How It Works:
Access Log Delivery (logging for non-CDN content) works similar to logging for CDN.  Customers can choose to have their logs enabled via the API or next generation Cloud Control Panel. Once logging is enabled, Cloud Files will create a container on the customer’s behalf called “.ACCESS_LOGS” and deliver logs to that container. Logs will be processed every two hours, but may take up to 24 hours to deliver based on the activity of Cloud Files at that time. Customers are charged standard Cloud Files prices for the storage of logs.

Enabling a container for log delivery is simple. When using the Cloud Files API, simply set metadata on the container, using “X-Container-Meta-Access-Log-Delivery” set to “true.”  If a customer needs to disable logs for any reason, they can simply set the value to “false” or remove the metadata altogether.

Our next generation Cloud Control Panel also supports enabling logs.  Once in the Files section of the control panel, click the gear next to a private container and select “Modify Logging…”

Customers will be asked to quickly confirm their choice. If a container is already logging-enabled, customers can also disable their logs using this process. Once logs are enabled, the first delivery will likely take 24 hours.

If you have any questions about this feature, other Cloud Files features or Rackspace in general, please feel free to comment on this post, contact our Fanatical Support team, or email me directly at megan.wohlford@rackspace.com[2].

  1. Cloud Files: http://www.rackspace.com/cloud/public/files/
  2. megan.wohlford@rackspace.com: mailto:megan.wohlford@rackspace.com

Source URL: https://blog.rackspace.com/logging-for-private-cloud-files-containers/