Moving from Sentry
Argus works with Sentry's library. You can keep it and change one line, or switch to the Argus SDK when you want more. You can do this one app at a time.
2 min read
Keep Sentry's library
Change the DSN (your app's key) to the one Argus gives you, then redeploy. Nothing else in your code changes.
js
Sentry.init({
dsn: 'https://<public key>@argus-in.naijacloud.com/<project id>',
})Errors, traces, releases and readable stack traces work the same as they do today.
What you gain with the Argus SDK
| Sentry's library | Argus SDK | |
|---|---|---|
| Errors | Yes | Yes |
| Traces | Yes | Yes |
| Logs | No | Yes |
| Metrics | No | Yes |
| Cron check-ins | No | Yes |
| Feature flags | No | Yes |
Switch to the Argus SDK to get logs, metrics, cron check-ins and flags too.
Switch one app at a time
- Install the Argus SDK
Use the page for your language, for example Node.js.
- Replace Sentry.init with init
Keep the same DSN. Calls like
captureExceptionkeep the same names. - Remove Sentry's library
Deploy, check that the source in Argus → Sources says "Sent with the Argus SDK", then uninstall the old package.
Other apps keep working
Apps still on Sentry's library keep sending to Argus while you switch the rest.