We've been making changes to how we organize and display our docs. Our work isn't done but we'd love your feedback.
Getting started
Basics
Domains & Origins
Performance

Configuration
Basics
Conditions
Dictionaries
Domains & Origins
Request settings
Cache settings
Headers
Responses
Performance
Custom VCL
Image optimization
Video

Security
Access Control Lists
Monitoring and testing
Securing communications
TLS
Web Application Firewall

Integrations
Logging endpoints
Non-Fastly services

Diagnostics
Streaming logs
Debugging techniques
Common errors

Account info
Account management
Billing
User access and control

Reference

    Log streaming: Log Shuttle

      Last updated June 03, 2019

    Fastly's Real-Time Log Streaming feature can send log files to Log Shuttle. Log Shuttle is an open source application designed to provide simpler encrypted and authenticated log delivery.

    Adding Log Shuttle as a logging endpoint

    Follow these instructions to add Log Shuttle as a logging endpoint:

    1. Review the information in our Setting Up Remote Log Streaming guide.
    2. Click the Log Shuttle logo. The Create a Log Shuttle endpoint page appears.

      the create a Log Shuttle endpoint page

    3. Fill out the Create a Log Shuttle endpoint fields as follows:
      • In the Name field, type a human-readable name for the endpoint.
      • In the Log format field, optionally type an Apache-style string or VCL variables to use for log formatting. The Apache Common Log format string appears in this field by default.
      • In the Token field, type the data authentication token. This is required for some endpoints like Heroku's Log Integration.
      • In the URL field, type the URL to which log data will be sent (e.g., https://logs.example.com/).
    4. Click the Advanced options link of the Create a Log Shuttle endpoint page. The Advanced options appear.

      the advanced options on the create a new Log Shuttle endpoint page

    5. 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.
    6. Click the Create button to create the new logging endpoint.
    7. Click the Activate button to deploy your configuration changes.
    Back to Top