LinkMeshPlan a central observability platform across on-premises and Azure: ownership, Collector blueprints, change control and measurable pilot acceptance criteria.
Roman Hüsler6 min read
LinkMeshServices drift on attribute names until your queries quietly miss data. How to normalize OpenTelemetry semantic conventions at the collector, fleet-wide.
Roman Hüsler10 min read
LinkMeshMost sizing guides get CPU right and memory wrong. A ratio-based method for sizing an OpenTelemetry gateway, and why scaling out won't fix memory.
Roman Hüsler13 min read
LinkMeshA Splunk-to-Sentinel move only pays off if data volume changes on the way. What a lift-and-shift costs, and where the pipeline layer belongs.
Roman Hüsler7 min read
LinkMeshA reference architecture for telemetry under revDSG and FINMA: classify at the edge, a Swiss gateway tier, split destinations, a control plane you host.
Philippe Braxmeier7 min read
LinkMeshThe Collector stopped being a protocol shim and became the enforcement point for cost, privacy and routing. What that shift changes about operating it.
Philippe Braxmeier5 min read
LinkMeshAttribute-based routing in the OpenTelemetry Collector — a priority-ordered, first-match-wins cascade you build with a picker instead of raw OTTL.
Roman Hüsler9 min read
LinkMeshKeep credentials out of committed Collector config: env vars, file substitution, Kubernetes Secrets, Vault — and how to rotate without downtime.
Roman Hüsler10 min read
LinkMeshEvery other data domain grew a middle tier. Observability never did — because agents shipped with backends. What that historical accident still costs.
Philippe Braxmeier6 min read
LinkMeshObservability explores telemetry; AIOps applies ML to detect, correlate and automate. Where the line sits, and why your pipeline decides both.
Philippe Braxmeier12 min read
LinkMeshEvery backend cost lever acts on data you already transmitted. Where the spend is really decided, and why commitment tiers make it permanent.
Philippe Braxmeier6 min read
LinkMeshThe 10 storage metrics worth tracking — capacity, performance, health — and how to collect them from servers and arrays with one OTel Collector.
Roman Hüsler6 min read
LinkMeshSplunk, Sentinel, Grafana and Dynatrace in one estate is normal, not a mistake. Collect once and fan out, instead of one agent per backend.
Roman Hüsler6 min read
LinkMeshDual-ship telemetry to two backends to validate a migration — without double-counting hosts, doubling metrics or duplicating every log line.
Roman Hüsler8 min read
LinkMeshSeven Cribl alternatives compared for 2026 — self-hosted, OpenTelemetry-native and SaaS — with an honest look at when Cribl is still the right call.
Philippe Braxmeier10 min read
LinkMeshIsolation, tenant identification and per-tenant routing for a shared OpenTelemetry Collector fleet — dedicated vs shared pipelines, quotas, RBAC.
Roman Hüsler11 min read
LinkMeshA single Collector is a single point of failure. HA across agent and gateway tiers: load-balanced pools, sending queues, and persistent queues.
Roman Hüsler8 min read
LinkMeshA practical playbook to cut observability spend: measure per-route volume, filter noise at the edge, sample, and route before the invoice lands.
Philippe Braxmeier7 min read
LinkMeshOTLP, the Collector and OpAMP make collection portable and give you a real exit path. What OpenTelemetry decouples — and what it doesn't.
Philippe Braxmeier11 min read
LinkMeshFive ways to deploy an OpenTelemetry Collector — agent-per-host, DaemonSet, sidecar, gateway, hybrid — compared, plus the no-collector option.
Roman Hüsler11 min read
LinkMeshThe reference architecture for OpenTelemetry at scale: agent collectors, a central gateway tier, and OpAMP as the control plane that configures it.
Philippe Braxmeier11 min read
LinkMeshA telemetry pipeline sits between your systems and your backends — where you control cost, routing and PII. What it is and how to run your own.
Philippe Braxmeier10 min read