Alpic Docs

Verifies an OTLP endpoint with a test payload, then saves it for logs, metrics, or traces. A paid plan is required.

Usage

alpic telemetry destinations create \
  --signal traces \
  --endpoint https://otlp.example.com/v1/traces

The default protocol is http/protobuf.

Extended Usage

Add visible and secret headers by repeating the relevant flag:

alpic telemetry destinations create \
  --environment-id <environmentId> \
  --signal logs \
  --endpoint https://otlp.example.com/v1/logs \
  --header X-Tenant=acme \
  --secret-header "Authorization=Bearer token"

Only export traces created by intentional MCP requests:

alpic telemetry destinations create \
  --signal traces \
  --endpoint https://otlp.example.com/v1/traces \
  --intentional-only

Options

Flag	Description	Default
`--environment-id`	Select an environment by ID
`--environment-name`	Select an environment by name
`--project-id`	Provide the project context by ID
`--project-name`	Provide the project context by name
`--signal`	Signal to export: `logs`, `metrics`, `traces`	Required
`--endpoint`	Complete OTLP signal endpoint	Required
`--protocol`	`http/protobuf` or `http/json`	`http/protobuf`
`--header`	Visible header in `NAME=VALUE` form. Repeatable.
`--secret-header`	Secret header in `NAME=VALUE` form. Repeatable.
`--intentional-only`	Export only intentional request traces	`false`
`--json`	Print the unmodified API response as JSON	`false`
`--non-interactive`	Skip interactive prompts

When the current directory is linked to an environment, the environment and project flags can be omitted.

Secret header values cannot be read back after creation.

Getting started

Authentication

Deployment

Devtools

Logs

User insights

Distribution

Git

Playground

Teams

Projects

Environments

Environment variables

Telemetry

telemetry destinations create

Usage

Extended Usage

Options

​Usage

​Extended Usage

​Options

Usage

Extended Usage

Options