Refactor monitoring services into separate packages
Separated and isolated the responsibilities of monitoring tools. Reorganized the code by introducing a core package that contains common code related to monitoring and moved all the service operations like error capturing and identification of users into their respective packages. This ensures each tool is independent and easy to maintain.
This commit is contained in:
39
packages/monitoring/api/README.md
Normal file
39
packages/monitoring/api/README.md
Normal file
@@ -0,0 +1,39 @@
|
||||
# Monitoring / @kit/monitoring
|
||||
|
||||
Please set the following environment variable to your preferred monitoring provider:
|
||||
|
||||
```
|
||||
NEXT_PUBLIC_MONITORING_PROVIDER=
|
||||
MONITORING_INSTRUMENTATION_ENABLED=true
|
||||
```
|
||||
|
||||
## Available Providers
|
||||
|
||||
To use a specific provider, set the `NEXT_PUBLIC_MONITORING_PROVIDER` environment variable to one of the following values:
|
||||
|
||||
1. Baselime: `baselime`
|
||||
2. Sentry: `sentry`
|
||||
|
||||
## Baselime
|
||||
|
||||
To use Baselime, set the `NEXT_PUBLIC_MONITORING_PROVIDER` environment variable to `baselime`.
|
||||
|
||||
```
|
||||
NEXT_PUBLIC_MONITORING_PROVIDER=baselime
|
||||
```
|
||||
|
||||
## Sentry
|
||||
|
||||
To use Sentry, set the `NEXT_PUBLIC_MONITORING_PROVIDER` environment variable to `sentry`.
|
||||
|
||||
```
|
||||
NEXT_PUBLIC_MONITORING_PROVIDER=sentry
|
||||
```
|
||||
|
||||
## Instrumentation
|
||||
|
||||
To enable instrumentation, set the `MONITORING_INSTRUMENTATION_ENABLED` environment variable to `true`.
|
||||
|
||||
```
|
||||
MONITORING_INSTRUMENTATION_ENABLED=true
|
||||
```
|
||||
Reference in New Issue
Block a user