Vakt360
NorskSign inStart free
Framework setup

Error monitoring for Vue

Set up Sentry-compatible error monitoring in your Vue app with Vakt360. Install the SDK, point it at your DSN, and see grouped, symbolicated errors in minutes.

Framework setup · 4 min read

  1. Create a project and copy your DSN

    Sign up for Vakt360 and create a project for your app. Open the project's settings and copy its DSN. It tells the SDK where to send events, and it is safe to ship because it can only ingest, never read your account.

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

  2. Install the SDK

    Vakt360 speaks the Sentry ingest protocol, so you use the standard Vue Sentry SDK, with nothing Vakt360-specific to learn.

    bash
    npm install @sentry/vue

  3. Initialise the SDK with your DSN

    Point the dsn at the value you copied above; that single line is the only Vakt360-specific change.

    ts
    import { createApp } from "vue";
import * as Sentry from "@sentry/vue";
import App from "./App.vue";

const app = createApp(App);

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

app.mount("#app");

  4. Send a test error

    Put this in a click handler or a mounted hook to send your first event. It should appear in your Vakt360 issues within a few seconds, grouped and ready to triage.

    ts
    throw new Error("Vakt360 test error");

  5. Upload source maps for readable stack traces

    Tag each deploy with a release in your SDK config, then upload your source maps for that release from the Releases area of your project, or from your build pipeline, so minified frames resolve back to your original code. See the source-maps guide for the full flow.

  6. Turn on alerts and go further

    Add email, Slack or webhook alerts so a new issue reaches you once, not once per event. From here you can also add performance transactions, uptime and cron check-ins, and session replay, all from the same DSN.

Related guides

Migrate from Sentry →

Vakt360 speaks the Sentry ingest protocol, so moving over is a DSN swap, not a re-instrumentation. Your existing SDKs, breadcrumbs and context all keep working.

Upload source maps →

Minified production bundles turn stack traces into gibberish. Source maps let Vakt360 resolve every frame back to your original file, function and line.

Slack alerts →

Route the errors that matter to the channel your team actually watches, deduplicated so one incident is one message, not a flood of pings.

Start monitoring on the free plan

100,000 events a month, no card required. Point your existing SDK at Vakt360 and see your first event in minutes.

Start freeRead the docs