@octri/monitoring-cli

@octri/monitoring-cli

Deprecated. Use @octri/cli and run octri monitoring.

The source-map uploader and the Octri CLI are one binary now. This package still publishes so pipelines pinned to npx @octri/monitoring-cli keep running, but it contains no implementation: it prints a deprecation notice on stderr and forwards its arguments into the octri router, so the two can never drift.

Migrating

Replace the binary name and prefix the command with monitoring. Every flag, environment variable and exit code is unchanged.

# before
npx @octri/monitoring-cli sourcemaps upload ./dist --release "$GIT_SHA"
npx @octri/monitoring-cli sources    upload ./src  --release "$GIT_SHA"

# after
npx @octri/cli monitoring sourcemaps upload ./dist --release "$GIT_SHA"
npx @octri/cli monitoring sources    upload ./src  --release "$GIT_SHA"

Installed globally, that is octri monitoring sourcemaps upload ./dist.

MONITORING_URL, MONITORING_TOKEN, MONITORING_ENVIRONMENT and MONITORING_RELEASE all still work, and MONITORING_INGEST_TOKEN is still read as a fallback for the token.

What you get by moving

The merged CLI signs in, so on a developer machine it can resolve the monitoring connection itself. No flags, no secrets:

octri auth login
octri monitoring sourcemaps upload ./dist

It also reads the other side of the upload. octri monitoring issues lists the production errors your SDKs reported, and octri monitoring issue <id> prints the stack, marking which frames resolved against the maps you uploaded.

octri monitoring config prints the three values a CI job needs.

Programmatic use

The exports are re-exported from @octri/cli, so existing imports still compile. Import from @octri/cli in new code.

import { uploadSourceMaps } from "@octri/cli";

See octri.dev and the CLI docs.