Telemetry Export Profile Reference

This page provides the field-level reference for Telemetry Export Profiles: the configurable fields per export protocol, the profile limit per Controller, supported log source types, export format specifications, and error and status codes. For the setup procedure, see Configure Telemetry Export Profiles .

Profile Limits

Limit	Value
Maximum Telemetry Export Profiles per Controller	10. A profile creation request is rejected once the total number of profiles for the Controller would exceed 10.
Maximum log source types per profile	Up to 2. DCF Logs and Gateway Metrics are the only two source types defined in the profile schema for this release (see Supported Log Source Types).

Supported Protocol Types

Protocol	Transport	Notes
OTLP over gRPC	gRPC over HTTP/2	Supports both server-only TLS and mutual TLS. CoPilot surfaces these as two separate connection methods: gRPC with Server TLS and gRPC with Mutual TLS.
OTLP over HTTP	HTTP with TLS	CoPilot surfaces this as the HTTP with TLS connection method.

The profile schema defines exactly two OTLP transport protocols, gRPC and HTTP. No syslog protocol exists in this schema. Do not confuse this feature with syslog-based log forwarding described elsewhere in the product.

Fields by Protocol Type

OTLP over gRPC (Server TLS)

Field	Description	Valid Values	Default
Profile Name	Identifies the profile in CoPilot.	String	None
Log Sources	Telemetry types this profile forwards. Cannot be changed after the profile is created.	DCF Logs, Gateway Metrics (one or both)	None
Gateway Scope	Which gateways the profile applies to.	All Gateways or a selected subset	None
Destination Endpoint	OTLP receiver endpoint.	Host:port (no URL scheme)	None
CA Certificate	Certificate Authority certificate used to validate the destination.	PEM-formatted certificate	None (system trust store)
Custom Headers	Key/value headers sent with each export request, typically used for authentication tokens. Values are not visible again after the profile is saved.	Key/value pairs	None
Filters	Optional filter limiting which DCF log types or DCF actions are forwarded. Requires DCF Logs to be a selected source. Available via the API and Terraform provider only; not in the CoPilot UI for this release (Phase 1).	`dcf_log_types`, `dcf_actions` (arrays of strings)	None
Forwarding Status	Whether the profile actively forwards telemetry.	Enabled / Disabled	Enabled

OTLP over gRPC (Mutual TLS)

Same fields as OTLP over gRPC (Server TLS), plus:

Field	Description	Valid Values	Default
Client Certificate	Client certificate presented to the destination for mutual TLS.	PEM-formatted certificate	None
Client Private Key	Private key paired with the client certificate.	PEM-formatted key	None

OTLP over HTTP

Same fields as OTLP over gRPC (Server TLS), except Destination Endpoint accepts a full URL rather than a bare host:port value. No other HTTP-specific fields beyond the shared set were found in the schema.

Protocol cannot be changed after a profile is created. The Terraform provider enforces this by forcing resource replacement when the protocol field changes; changing connection method in CoPilot after creation has not been separately confirmed in-product.

Skipping certificate verification (insecure_skip_verify) defaults to disabled. CoPilot does not expose a toggle for this option; it can be enabled only through the API, typically for QA and testing purposes.

Supported Log Source Types

Log Source Type	Description
DCF Logs	Security logs generated by the Distributed Cloud Firewall.
Gateway Metrics	System and network metrics reported by Aviatrix gateways (node_exporter).

The profile schema defines only these two source types for this release. Audit logs, system/operational syslog, and Controller/CoPilot platform metrics were considered during planning but are not defined as selectable source types in the shipped schema.

Export Format Specifications

Protocol	Export Format	Notes
OTLP over gRPC	OpenTelemetry Protocol (OTLP)	Native structured export; exact message schema not yet confirmed against an in-product build.
OTLP over HTTP	OpenTelemetry Protocol (OTLP)	Native structured export; exact message schema not yet confirmed against an in-product build.

CEF and NetFlow export formats remain excluded from 10.1 scope.

Error and Status Codes

Code	Meaning	Notes
400	Invalid input.	Returned when a create or update request contains an invalid field value.
404	Profile not found.	Returned when the requested profile does not exist.
409	Duplicate profile name, or profile limit exceeded.	Returned when a profile name already exists, or when creating the profile would exceed the maximum of 10 profiles per Controller (see Profile Limits).
500	Internal error.	Returned for unexpected server-side failures.

The live CoPilot UI test on 2026-08-24 (see guides/monitoring/otel-export-profiles.mdx) confirmed the profile list’s Status column shows only Enabled/Disabled, tied to the Forwarding Status toggle. This is separate from the API-level status codes above, which are returned by create, update, and delete requests.

Concepts & Architecture

Guides

Reference

Profile Limits

Supported Protocol Types

Fields by Protocol Type

OTLP over gRPC (Server TLS)

OTLP over gRPC (Mutual TLS)

OTLP over HTTP

Supported Log Source Types

Export Format Specifications

Error and Status Codes

​Profile Limits

​Supported Protocol Types

​Fields by Protocol Type

​OTLP over gRPC (Server TLS)

​OTLP over gRPC (Mutual TLS)

​OTLP over HTTP

​Supported Log Source Types

​Export Format Specifications

​Error and Status Codes

​Related Documentation

Profile Limits

Supported Protocol Types

Fields by Protocol Type

OTLP over gRPC (Server TLS)

OTLP over gRPC (Mutual TLS)

OTLP over HTTP

Supported Log Source Types

Export Format Specifications

Error and Status Codes

Related Documentation