Observability engagements

Programming consulting for teams running production software in South Africa. Every engagement type below is agreed in writing after inquiry; fees depend on scope, not a fixed catalogue price.

Technical assessments

We document how metrics, logs, and traces move from your services to storage, then score gaps against incident scenarios you name. Deliverables typically include a findings memo, prioritized instrumentation changes, and alert hygiene recommendations. Assessments suit teams preparing for a platform change or recovering from repeated false-positive pages.

Advisory sessions

Time-boxed working sessions with your engineers on topics such as OpenTelemetry rollout, cardinality control, SLO error budgets, or runbook structure. You keep the artefacts; we facilitate decisions and capture action items you can track internally.

Scoped implementation

When you want hands-on help, we implement agreed changes — for example exporter configuration, dashboard drafts, or trace propagation fixes — within a written scope. Milestones, acceptance checks, and payment timing are confirmed before work starts.

Who this is for

Organizations with internal development capacity who need specialist observability judgment, not a managed NOC replacement. We are not a fit if you require 24/7 outsourced operations or guaranteed incident resolution times without a pre-negotiated retainer.

Who this is not for

Teams seeking license resale, unlimited on-call coverage, or marketing-led “digital transformation” programmes without concrete telemetry goals.

From cable plant to span attributes

Engagements often start by reconciling what your network team documents with what collectors actually see. Mislabeled interfaces and stale topology maps show up as mystery latency in distributed traces.

Close view of network patch cables in a panel, high-tech computer component with cable connections
Overhead flat lay of notebook sketches and pens, hands writing in a spiral notebook on a desk

Workshops stay on paper before they touch production

Advisory sessions capture decision logs, sampling policies, and alert thresholds before anyone merges a pull request. That keeps diagnostics changes reviewable and reversible.

Outline your stack in an inquiry