Skip to main content
Fastly’s HTTPS logging endpoint streams one JSON line per request from your service to Quotable. Nothing runs in your request path.

Requirements

  • A Fastly service that serves the domain the source is created for.
  • Permission to edit the service’s logging endpoints and activate a new version.
What it measures: every field. Cache status is Fastly’s request state (HIT, MISS, PASS…), not an origin cache header. Fastly’s timestamp has one-second precision, so the format includes the request start in microseconds to keep two hits on the same path in the same second apart.

Set up

1

Create the source in Quotable

In Agent Analytics, select Connect source, choose Fastly and select Generate credentials. Copy the token, the endpoint URL and the Fastly log format string.
2

Add an HTTPS logging endpoint

In Fastly, open your service, clone the active version, go to Logging and create an HTTPS endpoint:
3

Activate the version

Activate the new service version. Before it sends logs, Fastly checks that the endpoint’s host accepts logs from your service by requesting /.well-known/fastly/logging/challenge on it. Quotable answers that check for every Fastly service, so there is nothing to configure. Logs start flowing on the next requests.
4

Confirm delivery

Select Check now in Quotable.

Log format

Paste this exactly. It renders one JSON object per request and deliberately leaves out cookies, authorization headers and the query string (req.url.path has no query).
If your service sets an x-request-id header, it’s used for exact deduplication.

Rotate the token

  1. Rotate the token in Quotable. The old token stops working immediately.
  2. Update the custom header value of the endpoint and activate the version.

Disconnect

Delete the logging endpoint, activate the version, then disconnect the source in Quotable.

Troubleshooting

Next steps

Read the dashboard

What to look at once data arrives.

Troubleshooting

Fix deliveries that fail or arrive empty.
Last modified on November 18, 2026