Vakt360
NorskSign inStart free
Framework setup

Error monitoring for Go

Set up Sentry-compatible error monitoring in your Go 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 Go Sentry SDK, with nothing Vakt360-specific to learn.

    bash
    go get github.com/getsentry/sentry-go

  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.

    go
    package main

import (
	"errors"
	"time"

	"github.com/getsentry/sentry-go"
)

func main() {
	err := sentry.Init(sentry.ClientOptions{
		Dsn:              "https://<your-key>@ingest.vakt360.com/<project>",
		TracesSampleRate: 1.0,
	})
	if err != nil {
		panic(err)
	}
	defer sentry.Flush(2 * time.Second)
}

  4. Send a test error

    sentry.Flush gives the event time to send before the program exits. It should appear in your Vakt360 issues within a few seconds, grouped and ready to triage.

    go
    sentry.CaptureException(errors.New("Vakt360 test error"))

  5. 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.

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.

Monitor a cron job →

A cron job that silently stops running is the outage you find out about last. Check-ins tell Vakt360 when a job starts and finishes, so a missed run is flagged immediately.

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