Octri

monitoring sourcemaps

Uploads source maps for a release, so stack traces from minified JavaScript and Dart show your original code. list shows what's been uploaded. See source maps for build setup and the order of steps in a deploy.

Signed in, the connection comes from your selected project. In CI, pass --url, --token and --environment, or set their environment variables, and no sign-in is needed. monitoring config prints the three values.

bash
octri monitoring sourcemaps [list | upload [paths…]]

octri monitoring sourcemaps upload [paths…]

Scans the paths for *.map files and uploads them for the release.

Arguments

[paths…]pathdefault: the current folder

Folders or files to scan, recursively.

Flags

--url <url>string

The monitoring service's address. Falls back to MONITORING_URL, then to your signed-in project.

--token <token>string

The project's ingest token. Falls back to MONITORING_TOKEN, then to your signed-in project.

--environment <env>string

The monitoring environment. Falls back to MONITORING_ENVIRONMENT, then to your signed-in project.

--release <release>stringdefault: the current git commit

The release the files belong to. Falls back to MONITORING_RELEASE. It must match the release your deployed SDK reports.

--dry-runboolean

Lists what would be uploaded and sends nothing.

octri monitoring sourcemaps list

Lists what's been uploaded.

Flags

--release <release>string

Only one release.

Examples

Upload in CI

bash
octri monitoring sourcemaps upload ./dist --release "$GIT_SHA"