Log provider
Point P0 at the logs that hold your gateway's MCP and A2A activity, so the P0 console can show every tool call the gateway handled.
The Log provider component tells P0 where a gateway's activity logs are stored. The gateway writes a log entry for every MCP tool call and A2A agent call it handles. Once a gateway is linked to a log provider, P0 reads those entries back and shows them on the Event log tab of the Agentic Access page.
The Log provider component is in preview. A log provider is optional. A gateway without one still enforces policy and still writes its logs, but P0 doesn't read them, and the Event log says no log provider is configured.
Types of log provider
Preview
The VictoriaLogs instance that the batteries-included chart deploys in your cluster. The chart turns it on by default.
Nothing. P0 queries the logs through the gateway's management API, using the access it already has.
Preview
A Google Cloud project, written by the chart's OpenTelemetry collector.
A project the collector can write to, and read access to that project for P0's platform service account.
Choose VictoriaLogs unless you already keep your logs in Google Cloud. It works on any cluster and needs no cloud credentials.
Add a log provider
Navigate to Integrations on p0.app and select Agentic gateway, then choose the Log provider component.
Click Add log provider.
Enter a Log provider identifier, a name for this provider within P0.
Set the Provider, then finish the provider-specific setup on its page: VictoriaLogs or Google Cloud Logging.
Link a gateway to a log provider
A log provider can be shared by several gateways. Adding one doesn't link it to any of them, so link each gateway yourself:
On the Agentic gateway integration page, choose the Gateway component and open the gateway.
Set Log provider to the provider you added.
Save the gateway.
Activity starts showing up in the Event log after the gateway's next logged call. Entries the gateway wrote before you linked it also appear, as long as the store still has them.
How P0 reads activity
P0 reads only the gateway's activity entries: inbound MCP tool calls and A2A agent calls. It doesn't read the gateway's operational logs, which are stored alongside them. Your gateway doesn't forward calls to P0, and P0 doesn't keep a copy of them: the logs stay in your own store, subject to your own retention policy.
Link all of an organization's gateways to the same kind of provider. The Event log reads from one kind of provider at a time. If some gateways use VictoriaLogs and others use Google Cloud Logging, P0 reads only the VictoriaLogs gateways, and the other gateways' activity doesn't appear.
Troubleshooting
The Event log says no log provider is configured
No gateway in your organization is linked to a log provider. Add one, then link your gateways to it.
A gateway is linked, but its activity doesn't appear
Check that the gateways all use the same kind of provider, as described in How P0 reads activity. Then follow the troubleshooting steps on the VictoriaLogs or Google Cloud Logging page.
Next steps
Review the activity a log provider enables on the Event log tab.
Configure the MCP servers or A2A bridge whose calls this activity covers.
Last updated