Docs

Get started

Vakt360 speaks the Sentry ingest protocol, so the SDKs you already ship keep working. Point them at your Vakt360 DSN and your errors start flowing in, grouped, symbolicated and alertable.

Quickstart

If your app already uses a Sentry SDK, going live with Vakt360 is a one-line change: swap the DSN. Nothing else in your setup needs to change.

JavaScript

Sentry.init({
  dsn: "https://<your-key>@ingest.vakt360.com/<project>",
  tracesSampleRate: 1.0,
});

Trigger a test error and it will appear in your dashboard within seconds, grouped into an issue.

Your DSN

A DSN (Data Source Name) tells the SDK where to send events. Create a project in the dashboard and copy its DSN from the project's settings. It looks like this:

DSN

https://<your-key>@ingest.vakt360.com/<project>

The DSN is scoped to ingest only. It cannot read your account or change settings, so it is safe to ship in client-side code. You can rotate a project's key at any time.

Install the SDK

Use the official Sentry SDK for your language. A couple of examples:

Node.js

# install
npm install @sentry/node

// initialise, as early as possible
import * as Sentry from "@sentry/node";
Sentry.init({ dsn: "https://<your-key>@ingest.vakt360.com/<project>" });

Python

# install
pip install sentry-sdk

# initialise
import sentry_sdk
sentry_sdk.init(dsn="https://<your-key>@ingest.vakt360.com/<project>")

The same one-line swap works for the JavaScript, Python, Ruby, Go, Java, PHP, .NET, Rust, React Native, iOS and Android SDKs, and any other Sentry SDK.

Releases & source maps

Tag each deploy with a release so Vakt360 can tell you which version introduced an issue and when it was resolved. Set the release in your SDK config, then upload source maps for that release so minified stack traces resolve to your original function names and line numbers.

JavaScript

Sentry.init({
  dsn: "https://<your-key>@ingest.vakt360.com/<project>",
  release: "2.14.0",
});

Upload maps from the Releases area of your project, or from your build pipeline. For native mobile, upload a ProGuard/R8 mapping (Android) or dSYM (iOS) from the project's settings.

Core concepts

Issues. Thousands of events collapse into a handful of issues by stack-trace fingerprint, so you fix the bug, not the flood.
AI. Get a root-cause analysis on any issue, and link a GitHub repo so Vakt360 can open a draft pull request with the fix, watch CI, and confirm the error is resolved. Use your own model or the built-in one.
Alerts. Get email, Slack, PagerDuty and webhook alerts on new issues, regressions and spikes. Alerts are deduped so you are never buried.
Releases. Every event is tied to a release, so you can see what a deploy introduced or fixed.
Uptime & cron. Watch the endpoints and scheduled jobs behind the errors, in the same place.
Team & roles. Invite your team with owner, admin, member, billing and read-only roles, with two-factor (enforceable across the workspace) and a tamper-evident audit trail built in.

Data & privacy

Your events are hosted and processed in the European Union, and sensitive values (authorization headers, cookies, tokens and card-like numbers) are scrubbed on our servers before an event is stored. See the security page for the full approach, and the privacy policy for what we collect.

API reference

Building an integration or automating your workspace? The full REST API, with request and response schemas, is documented in the interactive API reference.

Open the API reference

Get help

Stuck on something? Email support@vakt360.com and we will help you get set up.