Already running a Cloudflare Worker? Choose Logpush instead
When another Worker is already on your site, the setup guide now offers Cloudflare Logpush as a way to connect without adding a second Worker, and explains what that involves before you choose.
Sites that already run a Cloudflare Worker used to reach a stop in the setup guide: adding a second Worker to the same hostname needs someone who knows the first one, so the guide offered a developer review or support and nothing else. It now also offers Cloudflare Logpush, which sends Cloudflare's own request logs to Salience with no new Worker or routes.
The offer appears wherever the Worker route stops: when you answer that another Worker is (or may be) on the site, and when the automatic compatibility check finds an existing Worker route, a route with no Worker, or a Workers Custom Domain. Before you choose, it tells you what choosing does: your existing Workers stay untouched, Cloudflare must offer the HTTP requests Logpush dataset for your zone and bills Logpush by usage, a destination URL is prepared for the same site on the next step, and you then create the Logpush job in Cloudflare. Only Use Logpush instead changes anything. Your site, its domain and your account stay as they are. See Cloudflare Logpush in the help.