Sazabi
Log sourcesSend to an endpoint

Netlify

Configure a Netlify log drain pointed at a Sazabi endpoint to forward build, function, edge, and traffic logs in near real time.

About

Forward your Netlify traffic, function, edge, and deploy logs into Sazabi. Configure a Netlify log drain pointed at a Sazabi endpoint and Netlify batches your logs and posts them into Sazabi in near real time.

Log Drains require a Netlify Enterprise plan. Contact Netlify sales to upgrade if needed.

Prerequisites

  • A Netlify site on the Enterprise plan.
  • Your Sazabi intake URL (shown above).

Set up in the dashboard

Open the log drain form

In your Netlify site settings, go to Logs & Metrics > Log Drains and add a new log drain. Select General HTTP endpoint as the service.

Set drain values

Paste your Sazabi intake URL (shown above) into the Full URL field. Set the log drain format to JSON.

Save and activate

Save the log drain configuration. The drain becomes active immediately.

Set up with the CLI

You can also register the Netlify log source with the Sazabi CLI (installed and authenticated — see CLI reference).

Registering the source mints the same intake URL the dashboard shows above (the public key is embedded in its hostname):

sazabi log-sources create netlify --mode connectionless

The command prints the intake URL for the new source — copy the whole URL and point your sender at it using the configuration shown above. Run sazabi log-sources get <log-source-id> at any time to reprint the endpoint, or sazabi log-sources list to see every log source in the project.

Verify

Deploy your Netlify site or make a request to it so Netlify emits fresh logs. Open the Intake page in the Sazabi dashboard and confirm records from the Netlify source appear. Records typically arrive within a minute or two of site activity.

Troubleshooting

Log drain option not visible — Log Drains appear only on Enterprise plans. If the option is missing from Logs & Metrics, your site is on a lower tier.

Logs arrive in the wrong format — Confirm you selected JSON as the drain format. Sazabi parses the JSON drain format; other formats are not supported on this endpoint.

Further reading