Prerequisites
- Golf Gateway deployed and running
- OpenTelemetry Collector or compatible backend (Grafana, Datadog, etc.)
Configure OTLP export
- YAML
- Admin Portal
gRPC (Recommended):HTTP/Protobuf:
Export signals
| Signal | YAML Field | Description |
|---|---|---|
| Logs | export_logs: true | Audit log entries |
| Metrics | export_metrics: true | Performance metrics |
| Traces | export_traces: true | Request traces |
Resource attributes
Golf Gateway includes these resource attributes:| Attribute | Value |
|---|---|
service.name | From service_name field |
service.version | Gateway version |
golf.gateway.id | Gateway ID (if managed) |
golf.gateway.name | Gateway name |
Semantic conventions
Log records follow OpenTelemetry semantic conventions:| Attribute | Description |
|---|---|
event.name | Event type |
http.request.method | HTTP method |
url.path | Request path |
mcp.method | MCP method |
mcp.tool.name | Tool name |
Common OTLP backends
Consult your observability platform’s documentation for OTLP endpoint configuration:| Platform | Documentation |
|---|---|
| Grafana Cloud | Send data via OTLP |
| Datadog | OpenTelemetry in Datadog |
| New Relic | OpenTelemetry setup |
| Honeycomb | OpenTelemetry overview |
Verify export is working
- Check health endpoint includes OTEL status
- View logs in your OTLP backend
- Search for
service.name: golf-gateway
Troubleshooting
- Connection timeout: Verify endpoint is reachable
- 401/403 errors: Check authentication headers
- No data appearing: Verify
export_logs: truein your YAML config
Related guides
- Export Logs to Elasticsearch - ES export
- Export Logs to Azure Sentinel - Sentinel export