Configure telemetry on policies to export metrics and traces from the Actions API. You can enable request-level and plugin-level traces, attach extra metadata, and send data to multiple exporters such as Kafka and TrustLens.Documentation Index
Fetch the complete documentation index at: https://docs.neuraltrust.ai/llms.txt
Use this file to discover all available pages before exploring further.
Telemetry Settings
| Parameter | Type | Description | Required | Default |
|---|---|---|---|---|
enable_request_traces | boolean | Export traces at the request level | No | false |
enable_plugin_traces | boolean | Export traces at the plugin/action level | No | false |
extra_params | object | Key-value metadata to include with telemetry | No | {} |
exporters | array | List of exporters with name and provider-specific settings | No | [] |
header_mapping | object | Map internal telemetry fields to incoming HTTP headers | No | {} |
Example: policy with telemetry
Tips
- Start with request traces, then add plugin traces for deeper diagnostics
- Use header mapping to propagate correlation IDs from your clients
- Include stable fields in extra_params (e.g., app_id, tenant) to segment telemetry
- Send data to multiple exporters if you use more than one backend (e.g., Kafka + TrustLens)