@veryfront/ext-observability-sentry-node 0.1.1185 → 0.1.1186
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -5,11 +5,18 @@ First-party Sentry application error reporter for Veryfront runtimes.
|
|
|
5
5
|
Enable the adapter explicitly and provide its credential:
|
|
6
6
|
|
|
7
7
|
```sh
|
|
8
|
+
SENTRY_ENABLED=true
|
|
8
9
|
VERYFRONT_ERROR_REPORTER=sentry
|
|
9
10
|
SENTRY_DSN=https://public@example.ingest.sentry.io/1
|
|
10
11
|
```
|
|
11
12
|
|
|
12
|
-
`
|
|
13
|
+
`SENTRY_ENABLED=false` always disables reporting, even when the adapter and a
|
|
14
|
+
valid DSN are present. During the compatibility rollout, an unset flag keeps
|
|
15
|
+
the existing adapter-selection behavior. `SENTRY_DSN` selects the event
|
|
16
|
+
destination and may use a public HTTPS custom Sentry hostname; `SENTRY_URL` is
|
|
17
|
+
release-tooling configuration and is not read by the runtime adapter.
|
|
18
|
+
|
|
19
|
+
`SENTRY_DSN` alone does not activate the framework adapter. Official compiled Veryfront
|
|
13
20
|
binaries include the dormant adapter; npm consumers install
|
|
14
21
|
`@veryfront/ext-observability-sentry` separately. The adapter captures
|
|
15
22
|
unexpected application failures, tags them by service and boundary, and keeps
|