.NET

Install dotnet add package Blipit

Add the Blipit package (0.2.0 or newer) and call Init once at startup with your project's public key and project id. It runs on Blipit's own core. Unhandled exceptions and faulted tasks nobody awaited are reported on their own, and ASP.NET Core needs no extra package.

Paste it into Claude Code, Cursor or any AI coding assistant. It carries the steps and the code. In app.blipit.io, API keys, the same prompt comes with your key filled in.
Video: Install Blipit in any stack, from 1:07

1Install

sh
dotnet add package Blipit

2Initialise at startup

Keep the returned handle alive for the life of the process. Both values are on the project's Keys page.

Program.cs
using Blipit;

using var blipit = Blipit.Blipit.Init(new BlipitOptions
{
    Key = "<public key>",
    Project = "<project id>",
    Environment = "production",
    Release = "myapp@1.4.2",
});

3Get your keys

Sign in at app.blipit.io and open API keys in the sidebar, then your project. Every project has two keys. The public key starts with blipit_pk_: it goes in browser and app code, can only send events, and is safe for anyone to see. The secret key starts with blipit_sk_: it stays on your server or in Odoo, never in a browser, because it can also read and change issues. The secret key is shown only once, right after it is created, so copy it then; if you lose it, press Create a new secret key, and the old one stops working at once. Some SDKs also need the project id, shown on the same page.

API keys in app.blipit.io: the public key (blipit_pk_) for browser code and the secret key (blipit_sk_) for servers and Odoo.
API keys in app.blipit.io: the public key (blipit_pk_) for browser code and the secret key (blipit_sk_) for servers and Odoo.
A new secret key is shown once. Copy it now: it is stored hashed and cannot be shown again.
A new secret key is shown once. Copy it now: it is stored hashed and cannot be shown again.

4Keep the key in configuration

This SDK sends with the public key and the project id. Keep them in user secrets while developing and in environment variables in production (Blipit__Key and Blipit__Project), then read them from configuration.

sh
dotnet user-secrets set "Blipit:Key" "blipit_pk_your_public_key"
dotnet user-secrets set "Blipit:Project" "12"
Program.cs
using var blipit = Blipit.Blipit.Init(new BlipitOptions
{
    Key = builder.Configuration["Blipit:Key"],
    Project = builder.Configuration["Blipit:Project"],
});

5Keep keys out of git

Keep keys in environment variables or your host's secret settings, never in code you commit, and add your .env files to .gitignore. A public key in a web page is normal. If a secret key ever ends up in git, a public page, a screenshot or a chat, open API keys, press Create a new secret key, and paste the new key wherever the old one was used: the old key stops working straight away.

.gitignore
.env
.env.local
.env.*.local

6ASP.NET Core and logging

Nothing else to add: call Init at the top of Program.cs. Exceptions from endpoints, controllers and middleware are reported with the request, also when UseExceptionHandler handles them, and with TracesSampleRate set each sampled request is timed on Pulse by its route. BlipitLoggerProvider turns Information and above into breadcrumbs and Error and above into events.

Program.cs
var builder = WebApplication.CreateBuilder(args);
using var blipit = Blipit.Blipit.Init(new BlipitOptions
{
    Key = builder.Configuration["Blipit:Key"],
    Project = builder.Configuration["Blipit:Project"],
    TracesSampleRate = 0.2,
});
builder.Logging.AddProvider(new BlipitLoggerProvider());

7Manual capture and login attempts

Login attempts need the secret key: on the server, init with the secret key instead of the public one, or ingest refuses them with 403 security_needs_secret_key. Scale plan.

csharp
Blipit.Blipit.CaptureException(ex);
Blipit.Blipit.CaptureMessage("cache miss rate above 50%", BlipitLevel.Warning);
Blipit.Blipit.SetUser(id: "42", email: "ana@example.com");
Blipit.Blipit.CaptureSecurity("login_failed", email, "bad_password", null, ip, userAgent, null);

8Check it works

Open Issues in app.blipit.io. The first event appears within a few seconds, grouped into an issue, and the people in charge get an email.

csharp
Blipit.Blipit.CaptureMessage("Hello from .NET");

Good to know

  • Targets netstandard2.0 and net8.0.
  • TracesSampleRate = 0.2 in the options sends requests to the Pulse page; await Blipit.Blipit.Trace("charge card", () => gateway.ChargeAsync(order)) adds a timed step inside a request.
  • Upgrading from 0.1: remove the extra ASP.NET Core package and the builder.WebHost line that 0.1 needed, because Init covers ASP.NET Core. Blipit.Dsn, Blipit.Apply, BlipitOptions.Configure and PackageName are removed, CaptureMessage and AddBreadcrumb take BlipitLevel, and the capture calls return the event id as a string.
  • Keeping Blipit up to date: the Keeping Blipit up to date guide (docs.blipit.io/updates) explains the update banner, the emails for important releases, the notice in your development console and the update command for this platform.
  • One project per app and platform: each project picks its platform when it is created (Android, iOS, React Native, Flutter, Web, Backend or Odoo), and Blipit refuses data from any other platform with a clear error, so an iOS app and an Android app need two projects with two keys. Releases, versions, crash rates and store builds differ per platform, so mixing them in one project makes all of them wrong. A Web project also takes the server side of the same web app (the Next.js server or Node), and a React Native or Flutter project also takes its own native Android and iOS crash reports.

Stuck? Email support@blipit.io. Keys and the project id for each project are under API keys in app.blipit.io.