Connect Cloudflare Observability to Warp
Give Warp governed access to Cloudflare Observability through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Cloudflare Observability to Warp in four steps
Admins approve the server once. Everyone in Warp then gets it through the same governed connection.
- 1
Approve Cloudflare Observability in Runlayer
Add Cloudflare Observability from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Warp to Runlayer
Users add the Runlayer Plugin to Warp by following Runlayer’s setup guide. Warp reaches Cloudflare Observability’s tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Warp setup guide - 3
Sign in to Cloudflare Observability
Sign in the way Cloudflare Observability requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Cloudflare Observability from Warp
Cloudflare Observability’s approved tools appear in Warp. Every call is checked against policy and recorded.
Tools
Cloudflare Observability tools in Warp
Cloudflare Observability reports its tools when your organization connects it, so the list depends on your deployment.
Control
What Runlayer can see and stop in Warp
Some controls apply to every client at the gateway. Others depend on what Warp exposes to Runlayer.
Gateway policy (available)
Every Cloudflare Observability call from Warp passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Warp as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Warp yet, so control happens at the gateway.
Frequently asked questions
Connect more