monitoring sources
Uploads source files for a release, for languages whose stack traces carry file and line but not the code: Go, Rust, Java, Kotlin and Swift. list shows what's been uploaded. See source files, including what not to upload.
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.
octri monitoring sources [list | upload [paths…]]octri monitoring sources upload [paths…]
Scans the paths for source files and uploads them for the release. Everything under the paths goes, so scope them deliberately.
Arguments
[paths…]pathFolders or files to scan, recursively.
Flags
--url <url>stringThe monitoring service's address. Falls back to MONITORING_URL, then to your signed-in project.
--token <token>stringThe project's ingest token. Falls back to MONITORING_TOKEN, then to your signed-in project.
--environment <env>stringThe monitoring environment. Falls back to MONITORING_ENVIRONMENT, then to your signed-in project.
--release <release>stringThe release the files belong to. Falls back to MONITORING_RELEASE. It must match the release your deployed SDK reports.
--dry-runbooleanLists what would be uploaded and sends nothing. Run it first.
octri monitoring sources list
Lists what's been uploaded.
Flags
--release <release>stringOnly one release.
Examples
Check what would be uploaded
octri monitoring sources upload ./src --dry-runRelated
octri monitoring sourcemaps: Upload JavaScript and Dart source maps so stack traces are readable.- Source files