inkvo/docs/guides

Guides

End-to-end walkthroughs for real setups — from your first OTel pipeline to tuning detection so 3am stays quiet. The docs are the reference; these are the recipes.

Getting started

Connect your first service in an afternoon

From zero to a green status strip: create a key, point your collector at Inkvo, and verify ingest.

Beginner·8 minRead →

Instrument a Node service with OpenTelemetry

Add the OTel SDK, set the right resource attributes, and tag your deploys so root-cause works.

Beginner·12 minRead →

Tuning & operations

Map prod, staging, and dev to the right tone

Make a prod outage read like war and a staging hiccup read like a heads-up — and remap canary/preview.

Intermediate·9 minRead →

Cut alert noise with feedback & weights

Use mark-as-noise and per-signal weights to converge the feed on what's actually pages-worthy.

Intermediate·11 minRead →

Run an incident from page to post-mortem

Acknowledge, roll back or fix-forward, and export a post-mortem that mostly writes itself.

Intermediate·10 minRead →

Wire Slack, PagerDuty, and GitHub together

Connect paging, chat, and deploys so an incident shows up everywhere with one click to act.

Intermediate·7 minRead →

Advanced

Build a deploy-marker step into CI

Use the deploys API to record every release so correlation can blame the right commit.

Advanced·6 minRead →

Fan out incidents with outbound webhooks

Forward incident lifecycle events to your own systems. (Webhooks are in draft — track the changelog.)

Advanced·5 minRead →

Want a guide we haven't written? Tell us what you're trying to set up.Request a guide →