It's a SaaS (web app) for logging, error tracking, app health and performance.

a new issues pops up when:

• the app throws an error

terminology

• issue: a type of error that is thrown
• Event: an instance of an issue

sourcemaps

uploading your app's source maps helps you pinpoint exactly where in your code an error was thrown.
You need to upload your sourcemaps continuously to keep it updated.

set up uploading source maps with npx @sentry/wizard@latest -i sourcemaps --saas --org flatiron-software-corporation --project snapshot-jira
this adds the senty:sourcemaps command to upload sourcemaps manually
and optionally helps you edit to automatically upload source maps after building for production

Do you want to automatically run the sentry:sourcemaps script after each production build? │ No
● make sure to run this script after building your application but before deploying!

◆ Added auth token to .sentryclirc for you to test uploading source maps locally.

Are you using a CI/CD tool to build and deploy your application? │ Yes
◇ Add a step to your CI pipeline that runs the sentry:sourcemaps script right after building your application.
◇ Add the Sentry authentication token as an environment variable to your CI setup:
SENTRY_AUTH_TOKEN=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
▲ DO NOT commit this auth token to your repository!