Compute@Edge log streaming: Heroku's Logplex

As part of our Real-Time Log Streaming feature for Compute@Edge services, if you use our Heroku add-on, you can send log files directly to Heroku's Logplex system. Logplex is Heroku's distributed syslog router that collates and distributes log entries from a variety of sources into a single channel.

NOTE

Fastly does not provide direct support for third-party services. See Fastly's Terms of Service for more information.

Prerequisites

Before continuing, you will need the token from your Heroku Logplex account. If you don't have a Heroku Logplex account, now is the time to set one up by signing up for Heroku.

Once enabled, your Fastly logs will be available in exactly the same way as your regular app and hosted service logs. You can view them using the Heroku command line log viewer or send them to a logging add-on.

Adding Heroku Logplex as a logging endpoint

Follow these instructions to add Heroku Logplex as a logging endpoint for Fastly Compute@Edge services:

  1. Review the information in our Setting up remote log streaming for Compute@Edge guide. Additionally, our developer documentation provides more information about logging with Compute@Edge code written in Rust, AssemblyScript, and JavaScript.
  2. Click the Heroku Logplex Create endpoint button. The Create a Heroku Logplex endpoint page appears.
  3. Fill out the Create a Heroku Logplex endpoint fields as follows:
    • In the Name field, enter the name you specified in your Compute@Edge code. For example, in our Rust code example, the name is my_endpoint_name.
    • In the Token field, enter your Heroku Logplex token.
    • In the URL field, enter https://1.us.logplex.io/logs unless otherwise instructed by our support staff.
  4. Click the Create button to create the new logging endpoint.
  5. Click the Activate button to deploy your configuration changes.
Was this guide helpful?

Do not use this form to send sensitive information. If you need assistance, contact support@fastly.com.