OTLP sink
Export network requests, runtime logs, and build logs to an OTLP/HTTP Protobuf destination.
Manufact can send network requests, runtime logs, and build logs to any destination that accepts OTLP/HTTP Protobuf logs.
Add a sink
- Open your organization's Integrations page.
- Select Add OTLP sink.
- Enter the destination URL and authentication headers.
- Choose the servers and signals to export.
- Select Verify and create.
Manufact sends a verification record before saving the connection. If the destination rejects the request or cannot be reached safely, the sink is not created.
Routes start when you attach them, so earlier logs are not backfilled. Manufact exports request metadata and correlation fields, but not captured request or response payloads.
Network requests
MCP requests exports recorded gateway requests with a recognized MCP method, including failed requests and HTTP 401 responses. Existing sinks keep this behavior.
Enable Include other HTTP requests under MCP requests to also export OAuth discovery and other recorded requests with an absent or unknown MCP method. This setting is off by default and can be configured separately for each server in a sink. It applies to all HTTP status codes, including 401s.
Changing this setting keeps the current export cursor. Requests before that cursor are not backfilled; requests still waiting for export use the new setting.
The API signal and exported signal_type retain the key mcp_requests, with event name com.manufact.mcp_requests. These are OTLP log records, not new trace spans. Filter them using mcp.signal.type, mcp.data.http_method, mcp.data.path, and mcp.data.status_code. Non-MCP requests have an absent or unknown MCP method.
Initial HTTP 401 authentication challenges can be expected; distinguish those from genuine authentication failures when configuring alerts. Requests blocked by Cloudflare before reaching the gateway are not included.
Axiom example
Create an Axiom API token with ingest access to your dataset, then configure the sink with:
| Field | Value |
|---|---|
| Endpoint | https://api.axiom.co/v1/logs |
| Header | Authorization: Bearer <AXIOM_API_TOKEN> |
| Header | X-Axiom-Dataset: <DATASET_NAME> |
| Compression | Gzip |
Select MCP requests, Runtime logs, and Build logs as needed. Enable Include other HTTP requests for broader request coverage.
Protect the API token
Keep the Axiom token in the secret header field. Do not put it in the endpoint URL or resource attributes.