← All updates

Updated

Cloudflare zones, Tunnels and DNS edges in the context graph

More of Cloudflare in the context graph

Polylane syncs much more of your Cloudflare account into the context graph and links DNS records to the resources they serve, for teams that front their services with Cloudflare.

What changed

Polylane now syncs much more of your Cloudflare account into the context graph: zones, load balancers with their pools and monitors, health checks, Access applications, Tunnels, Spectrum apps, Stream live inputs, Images, Turnstile widgets, waiting rooms, certificate packs, Logpush jobs, and Workers routes and custom domains.

DNS across providers

A Cloudflare DNS record that points at a Vercel project, a Fly.io app, a Render service, an AWS load balancer or a CloudFront distribution becomes an edge in the context graph, so a hostname leads to the resource that serves it.

Quieter in Slack threads

Once Polylane is part of a Slack thread, it replies only to messages meant for it: questions, requests, answers to its own questions and corrections. Messages between teammates and acknowledgements such as "thanks" get no reply.

Why it matters

A request to your product often passes through Cloudflare before it reaches the service that answers it. With zones, load balancers, Tunnels and DNS in the context graph, an investigation can follow a hostname to the resource behind it, even when that resource runs on another provider.

How to use it

  1. Connect your Cloudflare account under Settings > Clouds, or re-sync an account you already connected with Sync with Cloud on its page.
  2. Open the context graph and search for a hostname or zone to see what it points at.
  3. Ask a thread, for example "What serves api.example.com, and what else sits behind the same load balancer?".

Related

Improvements
  • AWS CloudFront distributions join the context graph
  • Workspaces Custom model endpoints list the models they serve, so you pick one from a list
  • Workspaces OAuth client secrets can be rotated without recreating the client
Fixes
  • Slack Links, channel names and user group mentions in Slack messages are read correctly