Skip to content
Engineering deep-divesAll articles

SigNoz vs Datadog in 2026: OTel, ClickHouse & APM TCO

Engineering and 36-month TCO teardown of SigNoz vs Datadog and Grafana Cloud in 2026: OpenTelemetry Collector tail-sampling, unified ClickHouse telemetry, p99 host high-water-mark billing, PG17 FORCE RLS alert planes, and 150-host math.

Artem Zaitsev
Artem ZaitsevCTO · Idealogic
Author: Artem ZaitsevPublished: Updated: Reading time: 20 minHow we write →
On this page
Idealogic 2026 engineering comparison of SigNoz vs Datadog and Grafana Cloud covering OpenTelemetry tail-sampling, ClickHouse columnar telemetry, host and custom metric billing, and 36-month TCO

Somewhere past fifty Kubernetes nodes, most platform teams start asking the SigNoz vs Datadog question, usually with Grafana Cloud pricing, OpenTelemetry tail-sampling and ClickHouse BYOC observability close behind. Datadog is easy on a dozen nodes. The bill is what changes. Stacked per-host SKUs, $5.00 per 100 custom metric series, split log ingestion and indexing fees, and p99 high-water-mark billing on autoscaling bursts compound, and by year three the invoice can rival the compute it watches.

Keep stack layers distinct: ClickHouse vs TimescaleDB benchmarks customer-facing OLAP engines, and Langfuse vs LangSmith evaluates gen_ai.* prompt and trajectory evals for agentic AI in production. This guide covers the layer underneath: infrastructure metrics, distributed APM and structured logs, the telemetry that keeps microservices, queues and databases inside their SLAs.

At Idealogic, our custom software development, SaaS development, software development consulting, and dedicated development team squads architect telemetry backbones across fintech, healthtech, and logistics and supply chain. This 2026 teardown compares SigNoz, Datadog, Grafana Cloud and an owned OpenTelemetry + ClickHouse stack, walks through an OTel Collector Gateway (tail_sampling plus PCI DSS v4.0.1 PII scrubbing) with a PostgreSQL 17 or 18 FORCE RLS SLO plane, and models 36-month TCO at 150 Kubernetes hosts, 6,000 GB/mo of logs, 3,000 GB/mo of traces and 50,000 custom metric series.

What are SigNoz and Datadog? SigNoz is the open-source Datadog alternative: an OpenTelemetry-native observability tool with an MIT-licensed core (enterprise modules sit under a separate licence) that stores traces, logs and metrics in ClickHouse. Datadog is a proprietary SaaS observability suite billed per host, per GB and per custom metric. Grafana Cloud sits in between as the managed version of the AGPLv3 Grafana, Loki, Tempo and Mimir stack.

The short version

  • Datadog leads on turnkey breadth and loses on compound SKU and p99 host math: Datadog pricing stacks Infrastructure Pro ($15/host/mo) or Enterprise ($23/host/mo) and APM Enterprise ($40/host/mo), all billed annually (list prices checked November 2026), plus Custom Metrics ($5.00 / 100 series) and split Log Ingestion ($0.10/GB) + 15-day Indexing ($1.70/M events), amplified by hourly p99 high-water-mark host metering.
  • SigNoz, the open-source alternative to Datadog, wins on OpenTelemetry portability, unified ClickHouse queries and no host or seat fees. It's built on OpenTelemetry (MIT core plus Enterprise modules) and ClickHouse MergeTree, and SigNoz pricing charges zero per-host and zero per-seat fees ($49/mo Teams base credit, $0.30/GB logs and traces, $0.10/M metric samples, plus Enterprise/BYOC tiers).
  • Grafana Cloud is strongest for Prometheus mixins across three split backends. It pairs industry-standard dashboards with Mimir, Loki, and Tempo, requiring SREs to juggle PromQL, LogQL, and TraceQL plus per-user Enterprise IRM/SAML packages.
  • At 150 K8s hosts (9 TB/mo logs+traces, 50k series, 45 engineers), Owned OTel + BYOC wins TCO: Over 36 months, Owned OTel Gateway + Self-Hosted SigNoz / ClickHouse EKS ($144,900 CEE) saves $455,400 vs Datadog Enterprise ($600,300), $198,000 vs Grafana Cloud Pro ($342,900), and $63,000 vs SigNoz Cloud Enterprise ($207,900).

2026 observability internals & billing mechanics: SigNoz vs Datadog vs Grafana Cloud

Evaluating signoz vs datadog (or datadog vs signoz) comes down to four structural boundaries: agent instrumentation lock-in, host high-water-mark billing, storage correlation, and metric cardinality math.

Four structural telemetry, storage, and FinOps boundaries separating SigNoz, Datadog, and Grafana Cloud in 2026

1. Datadog: Proprietary agent polish vs five compounding billing meters

With 1,000+ built-in integrations, eBPF Universal Service Monitoring, Continuous Profiler and Cloud SIEM, Datadog covers more ground out of the box than either rival. The catch shows up in observability vs monitoring at Kubernetes scale, where five billing meters stack on top of each other:

  1. Stacked Host SKUs ($15/$23 Infra + $40 APM Ent.): Pairing Infrastructure Enterprise ($23/host/mo, 200 custom metrics, 10 containers; vs Pro at $15/host/mo, 100 custom metrics, 5 containers) with APM Enterprise ($40/host/mo) sets your baseline at $63/host/mo before logs or metric overages.
  2. Container Pools & Hourly p99 High-Water-Mark Taxes: Under Datadog container billing, extra containers above your host allotment (5 on Pro, 10 on Ent.) add per-container fees, while host counts are metered hourly at a monthly p99 high-water mark: Datadog excludes the highest 1% of hourly readings (about 7 hours in a 720-hour month) and bills the maximum of the remaining 99%. If Karpenter bursts your 150-node cluster to about 177 nodes for two hours each weekday (40 hours/mo) during checkout or data pipeline peaks, that burst outlasts the 7-hour allowance, so all 27 extra nodes are billed for the month across Infra and APM.
  3. Split Log Ingestion + Retention Indexing: Datadog charges $0.10/GB to ingest logs, plus $1.70 per million events indexed at 15-day retention, forcing fragile exclusion filters that drop debug context right before outages.
  4. Custom Metric Cardinality ($5.00 per 100 series): Every 100 custom series above your host pool (100/host Pro, 200/host Ent.) costs $5.00/mo. Adding tenant_id or endpoint labels to histograms multiplies series overnight.
  5. Agent and DogStatsD gravity. Datadog accepts OTLP directly and ships its own collector distribution, but live processes, USM and profiler flamegraphs work best with dd-trace and proprietary monitors, and that's where vendor lock-in builds up.

2. SigNoz: the open-source Datadog alternative built on OpenTelemetry and ClickHouse

SigNoz (SigNoz/signoz) is engineered natively around OpenTelemetry semantic conventions and ClickHouse columnar storage:

  1. 100% Vendor-Neutral OTel: Services instrument once with upstream OpenTelemetry SDKs and Kubernetes collectors, exporting OTLP/gRPC (:4317) or OTLP/HTTP (:4318) into the OpenTelemetry Collector.
  2. Unified ClickHouse Correlation: Instead of running Elasticsearch for logs, Cassandra for traces and Prometheus TSDB for metrics, SigNoz writes all three signals into ClickHouse MergeTree tables. ZSTD compression often reaches 5x to 10x or more on repetitive logs, though you should measure it on your own data. Materialized hot columns (service.name, http.response.status_code or the legacy http.status_code from older SDKs, tenant.id) let you jump from a slow p99 Flamegraph span to its container logs in milliseconds.
  3. Usage-Only Pricing ($0 Host, $0 Seat, $0 Series Tax): SigNoz Cloud Teams ($49/mo base credit) bills $0.30/GB for logs and traces (15-day search included, no separate indexing fee) and $0.10/M metric samples regardless of series cardinality, with 1-month metrics retention and no host or seat fees. Enterprise starts at $4,000/mo with usage included and adds SAML, Dedicated and BYOC options.

3. Grafana Cloud Pro / Advanced (LGTM) trade-offs

Grafana Cloud (Loki, Grafana, Tempo, Mimir) shines for teams invested in Prometheus mixins, trading single-engine simplicity for three separate query engines (PromQL, label-only LogQL chunk scans, and TraceQL), active-series metering and per-active-user Enterprise SAML/IRM pricing. Grafana bills on 95th-percentile active series and monthly active users, so the Grafana figures below are our assumed list-price model; check Grafana Cloud billing against your own usage.

Architectural dimensionSigNoz (Cloud / BYOC / OSS)Datadog (Pro / Enterprise)Grafana Cloud (Pro / Enterprise)
Core license & SDKMIT core + Enterprise modules, native OTelProprietary SaaS; OTLP accepted, deeper features favour dd-traceAGPLv3 (LGTM) + Cloud Ent.
Storage backendUnified ClickHouse (all 3 signals)Proprietary SaaS storage3 split stores (Mimir/Loki/Tempo)
Host & container tax$0/host & $0/container$15/$23 Infra + $40 APM/host (p99)$0/host raw; billed via active series
User seat fees$0/seat (unlimited engineers)$0 APM; per-seat pricing on some productsFrom roughly $8 to $55+/user/mo (assumed, Pro vs Ent.)
Log billing$0.30/GB flat (ingest + 15d search)$0.10/GB ingest + $1.70/M indexedFrom roughly $0.50/GB ingested (Loki, assumed)
Custom metrics$0.10 / 1M samples ($0 series tax)$5.00 / 100 custom seriesRoughly $6.50 to $8.00 / 1k active series (assumed)
VPC / BYOC controlSelf-hosted MIT core on K8s or BYOCHosted SaaS regions, no general customer-VPC deploymentSelf-hosted AGPLv3 LGTM or Cloud

Production blueprint: OpenTelemetry tail-sampling gateway, PCI DSS scrubbing and a multi-tenant SLO plane

Teams that move multi-tenant SaaS architecture and how to build a SaaS platforms off Datadog without a gateway tend to hit two failures. The first is sampling: head sampling misses rare downstream errors, while keeping 100% of traces floods storage, and unredacted card numbers or JWTs in spans put you in breach of PCI DSS v4.0.1. The second is noisy-neighbor alert storms that leak one tenant's metadata to another.

We fix the first with a two-layer OpenTelemetry Collector topology. Lightweight node collectors tag spans with Kubernetes metadata and pass them to a stateful gateway tier, which redacts PII with the transform processor and then applies the tail sampling processor. In our model this cuts network egress and ClickHouse trace storage by about 65% and still keeps every error, slow and VIP trace the policies match. Your ratio will depend on error rate and traffic mix. The sampling policy waits 10 seconds for a trace to finish, then keeps every trace with an error, every trace slower than 500 ms, every trace on the VIP payout, checkout and settlement routes, and a 5% baseline of everything else.

The tail sampling processor is still beta for traces and holds spans in memory for the full decision window. Size gateway replicas for that wait and test pod restarts before you rely on it.

For the second failure we put Google SRE multi-window SLO burn-rate alerting behind a PostgreSQL 17 or 18 control plane with Row-Level Security, so each tenant's SLO policies and incidents stay isolated across multi-tenant SaaS boundaries. The fast-burn rule is 14.4x over both one hour and five minutes, which spends 2% of a 30-day error budget in an hour. These are the design decisions that carry the blueprint:

DecisionWhere it livesWhat it buys you
Trace-affine routingNode collectorsk8sattributes adds pod and namespace metadata, and the loadbalancing exporter keys on trace ID, so every span of one transaction reaches the same gateway replica
PII redaction before exportGateway, inside your VPCOTTL statements drop authorization and cookie headers, mask 13 to 19 digit card numbers in URLs and log bodies, and replace Bearer tokens, then the gateway exports over mTLS behind a memory limiter
Error-first samplingGatewayKeeps all ERROR traces, all traces slower than 500 ms and all payout, checkout and settlement routes, and samples healthy traffic at 5%
Tenant isolationPostgreSQL, enforced by the databaseFORCE RLS on the policy and incident tables, a dispatcher role without BYPASSRLS, and a tenant setting bound per transaction so a PgBouncer transaction pooler cannot carry one tenant's context into another's session
Two-window paging ruleDispatcher servicePages only when both the 1h and 5m burn rates reach 14.4x, skips windows with too little traffic, and clears within five minutes of a rollback
Deduplication and evidenceDatabase plus dispatcherLocks the SLO row, suppresses repeat pages inside a cooldown (30 minutes by default) and stores an exemplar trace ID that links the incident to its SigNoz flamegraph

Auditors for SOC 2 Type II and PCI DSS v4.0.1 ask about exactly this kind of tenant-isolation control. The design helps, but it won't pass an audit for you.

Datadog renewal crossing $12k/mo or Kubernetes bursts inflating p99 host bills?
Share your Datadog SKU invoice, host count, monthly log/trace GB, and custom series. Our SRE architects will model SigNoz Cloud vs Owned EKS BYOC.
Audit your observability TCO

SigNoz vs Datadog TCO at 150 Kubernetes hosts: the 36-month model

The short answer: at 150 Kubernetes hosts and 9 TB/mo of logs and traces, our 36-month model puts Datadog Enterprise at $600,300, SigNoz Cloud at $207,900 and an owned OTel plus ClickHouse stack at $144,900.

Model a regulated B2B SaaS cluster over 36 months: 150 Kubernetes hosts (<= 10 containers/host, weekday autoscaling bursts), 6,000 GB/mo logs (1,500M indexed events/mo at 15-day retention, assuming roughly 4 KB per event), 3,000 GB/mo trace spans, 50,000 active custom metric series (2,500M samples/mo), 45 engineers, Okta SAML SSO, and SOC 2 Type II + PCI DSS v4.0.1.

Labor compares Idealogic's $75/hr Senior CEE vs $165/hr US agency rates (2.2x). The $165 figure is a typical US agency rate in our experience, not an official statistic; for labour-cost context see the Eurostat hourly labour cost table (lc_lci_lev) and O*NET Software Developers (15-1252.00). Infrastructure uses us-east-1 list prices for Amazon EKS ($0.10/hr), AWS EBS gp3 ($0.08/GB-mo), and Amazon S3 ($0.023 Standard, $0.0125/GB-mo Standard-IA) pricing:

  1. Option A: Datadog Enterprise (150 Hosts + APM Ent. + 15-Day Indexed Logs + p99 Burst):
    • Setup & FinOps (120h setup = $9,000 CEE / $19,800 US + 15h/mo x 36 = 540h tag/exclusion governance = $40,500 CEE / $89,100 US -> 660h = $49,500 CEE / $108,900 US).
    • 36-mo Datadog SaaS ($15,300/mo x 36 = $550,800): Infra Ent. (150 x $23 = $3,450/mo, 30k pooled custom series) + APM Ent. (150 x $40 = $6,000/mo, annual list price) + Custom Metrics 20,000 overage (200 x $5 = $1,000/mo) + Log Ingestion (6,000 x $0.10 = $600/mo) + 15-day Indexed Logs (1,500M x $1.70/M = $2,550/mo) = $13,600/mo baseline + p99 autoscaling burst (27 extra nodes x $63 = about $1,700/mo) = $15,300/mo -> $600,300 CEE ($659,700 US).
  2. Option B: Grafana Cloud Pro / Advanced (Loki + Tempo + Mimir + 45-User Enterprise IRM/SAML):
    • Setup & PromQL/LogQL/Tempo Ops (180h setup = $13,500 CEE / $29,700 US + 20h/mo x 36 = 720h ops = $54,000 CEE / $118,800 US -> 900h = $67,500 CEE / $148,500 US).
    • 36-mo Grafana Cloud ($7,650/mo x 36 = $275,400, assumed list-price model): $3,000/mo logs + $1,500/mo traces + $400/mo 50k Prometheus series + $2,750/mo Enterprise IRM/SAML for 45 monthly active users (our assumption) -> $342,900 CEE ($423,900 US).
  3. Option C: SigNoz Cloud Enterprise ($0 Host Tax, $0 Seat Tax, Unified Managed ClickHouse):
    • Setup & OTel Collector Ops (120h setup = $9,000 CEE / $19,800 US + 15h/mo x 36 = 540h ops = $40,500 CEE / $89,100 US -> 660h = $49,500 CEE / $108,900 US).
    • 36-mo SigNoz Cloud ($4,400/mo x 36 = $158,400): Logs (6,000 GB x $0.30 = $1,800/mo) + Traces (3,000 GB x $0.30 = $900/mo) + Metrics (2,500M x $0.10/M = $250/mo) + Enterprise plan uplift ($1,450/mo, our assumption: SigNoz lists Enterprise from $4,000/mo with usage included, so we model $4,400/mo all-in; $0 host fees, $0 seat fees) -> $207,900 CEE ($267,300 US).
  4. Option D: Owned OpenTelemetry Gateway + Self-Hosted SigNoz / ClickHouse EKS BYOC (MIT core):
    • Turnkey Build (600h @ $75/hr CEE = $45,000; $165/hr US = $99,000): HA OTel tail_sampling + PII redaction gateway (65% trace reduction assumed), self-hosted SigNoz (MIT core) + Altinity ClickHouse Operator on EKS (NVMe hot + S3-IA cold), and PG17 FORCE RLS SLO plane.
    • 36-mo AWS EKS + ClickHouse + S3-IA ($1,650/mo x 36 = $59,400): Right-sized after 65% trace tail-sampling reduction (1,050 GB/mo persisted spans + ZSTD-compressed logs (about 10x assumed) on r8gd NVMe/gp3 + $0.0125/GB-mo S3-IA + RDS PG17) + 15h/mo (540h) SRE ($40,500 CEE / $89,100 US) -> $144,900 CEE ($247,500 US).
Worked 36-month observability TCO ($k, CEE labor included) at 150 K8s hosts, 6 TB/mo logs, 3 TB/mo traces & 50k custom series: Owned OTel + ClickHouse BYOC saves $455.4k vs Datadog Enterprise and $63.0k vs SigNoz Cloud
36-month line item (150 hosts, 9 TB/mo)Option A: Datadog Ent.Option B: Grafana CloudOption C: SigNoz CloudOption D: Owned OTel+BYOCEconomic driver
1. Setup / build ($75/hr CEE)$9,000 (120h; $19.8k US)$13,500 (180h; $29.7k US)$9,000 (120h; $19.8k US)$45,000 (600h; $99.0k US)OTel gateway + ClickHouse EKS
2. 36-mo SaaS / AWS Infra$550,800 ($15,300/mo)$275,400 ($7,650/mo)$158,400 ($4,400/mo)$59,400 ($1,650/mo)65% tail-sampling + $0 host/seat
3. 36-mo FinOps / SRE ($75/hr)$40,500 (15h/mo; 540h)$54,000 (20h/mo; 720h)$40,500 (15h/mo; 540h)$40,500 (15h/mo; 540h)Operator GitOps vs exclusion churn
Total 36-Month TCO (CEE)$600,300$342,900$207,900$144,900 (CapEx incl.)Saves $63.0k to $455.4k
Total 36-Month TCO (US $165/hr)$659,700$423,900$267,300$247,500 (CapEx incl.)Wins by $19.8k to $412.2k US
Year-2+ Run-Rate (CEE)$197,100/yr$109,800/yr$66,300/yr$33,300/yrSaves $33.0k to $163.8k/yr
Lock-In & ResidencyProprietary + p99 host wall3-store SaaS (LGTM)Managed OTel + ClickHouseMIT core + VPC BYOCZero vendor lock-in

Assumptions behind these numbers: list prices checked in November 2026 with annual billing where the vendor offers it, Datadog log events of roughly 4 KB, a burst of 27 extra nodes for 40 hours a month, a 65% tail-sampling reduction and about 10x ZSTD compression on logs. The Grafana Cloud and SigNoz Enterprise lines are modelled, not quoted. Swap in your own invoice before you act on any of it.

Sensitivity check: Sub-30 host SaaS cutoff & CapEx payback

  • Under 30 hosts (<1.5 TB/mo logs+traces): Skip self-hosting; run SigNoz Cloud Teams ($49/mo base, $0.30/GB, $0 host/seat fees) behind an OTel PII scrubber (~$350 to $600/mo). Adding 65% OTel tail_sampling in front of SigNoz Cloud Ent. also trims Option C by another $585/mo ($21,060 over 36 months).
  • Payback at 150 hosts ($75/hr CEE): Option D OpEx is $2,775/mo ($1,650 AWS + $1,125 SRE) vs $16,425/mo (Datadog), $9,150/mo (Grafana), and $5,525/mo (SigNoz Cloud). Extra $36,000 CapEx pays back in 2.64 months vs Datadog ($36,000 / $13,650/mo) and 13.09 months vs SigNoz Cloud ($36,000 / $2,750/mo).

SigNoz vs Datadog migration costs: senior CEE vs US rates

Our custom software development, SaaS development, and dedicated development team squads deliver Datadog-to-OTel migrations at $75/hr senior CEE vs $165/hr US agency rates (2.2x):

Engagement tierTimelineHoursSenior CEE ($75/hr)US Agency ($165/hr)Deliverables
OTel Gateway Sprint2 to 3 wks150 to 240h$11,250 to $18,000$24,750 to $39,600OTel tail_sampling, PCI redaction & metric trim
SigNoz Cloud Migration4 to 6 wks240 to 360h$18,000 to $27,000$39,600 to $59,400dd-trace -> OTel SDKs, Terraform alerts & SAML
Owned OTel + EKS BYOC (600h)8 to 11 wks500 to 700h$37,500 to $52,500 ($45.0k)$82,500 to $115,500 ($99.0k)OTel Gateway, ClickHouse NVMe+S3-IA & PG17 SLO
Multi-Region OTel Mesh12 to 16 wks800 to 1,080h$60,000 to $81,000$132,000 to $178,200Multi-region Kafka OTel buffers, SIEM S3 & DR
Dedicated SRE PodOngoing240h/mo (2)From $18,000/moFrom $39,600/moKubernetes, OpenTelemetry & ClickHouse SRE pod

Inside the worked 600-hour ($45,000 CEE vs $99,000 US) owned OpenTelemetry stack

Worked model: 600-hour ($45,000 at $75/hr CEE vs $99,000 at $165/hr US) owned OpenTelemetry Gateway + MIT-core SigNoz / ClickHouse EKS BYOC observability stack
  • 1. OTel Tail-Sampling (25% / 150h / $11,250 CEE vs $24,750 US): Node DaemonSets, traceID-routed stateful OTel Gateway, tail_sampling (100% error/>500ms/VIP, 5% baseline), and PCI DSS v4.0.1 PII scrubbing.
  • 2. ClickHouse & S3-IA (25% / 150h / $11,250 CEE vs $24,750 US): Altinity ClickHouse Operator on EKS r8gd NVMe nodes, 15-day hot to 90-day S3-IA TTL tiering, ZSTD codecs, and S3 Gateway Endpoints.
  • 3. PG17 Alert Plane (20% / 120h / $9,000 CEE vs $19,800 US): PG17 FORCE RLS multi-tenant SLO burn-rate tables (14.4x multi-window), cooldown deduping, and encrypted PagerDuty/Slack routing.
  • 4. RED Maps & Hooks (20% / 120h / $9,000 CEE vs $19,800 US): dd-trace to OpenTelemetry migration, materialized RED service maps, Okta SAML SSO, and GitOps dashboards.
  • 5. Replay & Cutover (10% / 60h / $4,500 CEE vs $9,900 US): 14-day dual-export shadow parity against Datadog, k6 backpressure chaos QA, and clean Datadog agent teardown.

Teams rarely overspend on observability because they log too many real incidents; they overspend because Datadog bills high-water-mark host taxes on autoscaling bursts while indexing billions of healthy spans. Putting an OpenTelemetry tail-sampling and PII-redaction gateway in front of ClickHouse keeps one hundred percent of broken traces while cutting three-year spend by seventy-five percent.

Artem Zaitsev · CTO at Idealogic

Shipped Idealogic proof and a 5-step SigNoz vs Datadog decision checklist

Two shipped projects where we built this kind of telemetry:

  • Exchange & banking SLO telemetry (Bitholder & Fese): Matching-engine and ledger trace correlation, with PAN redaction designed for PCI DSS v4.0.1 scope.
  • Logistics SLA observability (HaulBreeze): Carrier webhook and cold-chain burn-rate alerting across logistics and supply chain fleets.

When is Datadog still the right call? If you run dozens of legacy integrations across clouds, use Cloud SIEM, RUM and eBPF Universal Service Monitoring every day, and the bill is a small slice of your cloud spend, the migration labor may never pay back. Paying for breadth is a fair trade when nobody on your team wants to run collectors.

For everyone else, five checks settle SigNoz vs Datadog vs Grafana Cloud in 2026:

  1. Under 30 hosts (<1.5 TB/mo logs+traces)? Run SigNoz Cloud Teams ($0.30/GB, $0 host/seat fees) with an OTel PII scrubber.
  2. Legacy cloud sprawl needing turnkey Cloud SIEM & eBPF USM? Keep Datadog behind an upstream OTel Gateway trimming noisy logs and metrics before ingest.
  3. Deep Prometheus/Grafana culture <5 TB/mo? Use Grafana Cloud Pro with Alloy metric relabel drops.
  4. 50 to 150 hosts wanting managed ClickHouse APM without K8s storage ops? Pick SigNoz Cloud Enterprise ($207.9k 3-yr TCO vs $600.3k Datadog).
  5. 100+ autoscaling K8s hosts, 5 TB+/mo telemetry, or strict VPC residency? Deploy Owned OTel Gateway + MIT-core SigNoz / ClickHouse on EKS (NVMe + S3-IA + PG17 SLO Plane) ($144.9k 3-yr TCO). Contact our team for a 48-hour Datadog-to-OTel TCO audit.
Planning a Datadog exit to OpenTelemetry, SigNoz Cloud, or EKS ClickHouse BYOC?
Send your Datadog monthly SKU breakdown, K8s node count, and retention SLA. Our senior CEE platform architects will return a line-item 36-month migration plan in 48 hours.
Request a 48-hour Datadog exit audit

Occasional field notes on building software, no spam

Protected by Cloudflare Turnstile · Privacy · Terms

Artem Zaitsev
Artem ZaitsevCTO · Idealogic Development OÜ

CTO and Co-founder at Idealogic. Directing engineering, systems architecture, security, and full-stack delivery across web, mobile, and blockchain.

Frequently asked questions

  • Choose SigNoz when your microservices standardize on vendor-neutral OpenTelemetry instrumentation, your Kubernetes autoscaling triggers expensive p99 host high-water-mark surcharges on Datadog, or your security team wants an MIT-licensed open-source core and BYOC ClickHouse data residency with no per-host or per-seat fees. Choose Datadog when your organization runs hundreds of legacy heterogeneous cloud integrations, relies on turnkey eBPF Universal Service Monitoring, and prioritizes out-of-the-box Cloud SIEM and RUM breadth over telemetry margin.

  • Datadog bills Infrastructure Pro ($15 per host per month), Infrastructure Enterprise ($23) and APM Enterprise ($40) at annual list prices, and it counts active hosts every hour. It drops the highest 1% of hourly readings, roughly seven hours in a 720-hour month, and bills the maximum of what is left. So if Horizontal Pod Autoscalers or Karpenter keep extra nodes running for more than about seven hours a month, during traffic peaks or batch jobs, those nodes are billed for the whole month on every attached host SKU.

  • Datadog allocates 100 custom metrics per Infrastructure Pro host and 200 per Enterprise host, charging $5.00 per 100 additional custom metric time series per month. Adding a single high-cardinality Kubernetes label such as pod_uid, tenant_id, or endpoint across microservice histograms easily spawns tens of thousands of distinct combinations. SigNoz eliminates series-cardinality surcharges on its cloud and self-hosted plans, metering $0.10 per million ingested metric samples regardless of label combinations.

  • Grafana Cloud runs three separate specialized engines underneath one UI: Mimir for Prometheus metrics, Loki for label-indexed object logs, and Tempo for trace blocks, requiring engineers to pivot across PromQL, LogQL, and TraceQL. SigNoz stores traces, structured logs, and metrics inside a single unified ClickHouse columnar cluster with materialized high-cardinality columns, allowing engineers to correlate a slow trace span directly to raw container logs and host metrics in sub-second queries.

  • Head-based sampling decides whether to keep or drop a distributed trace at the ingress root span before downstream services execute, inevitably discarding rare downstream database timeouts or payment failures unless you keep high percentages of traffic. Running an OpenTelemetry Collector Gateway tier with the tail_sampling processor buffers spans by trace_id in memory for several seconds and retains one hundred percent of error traces, one hundred percent of slow traces above 500 milliseconds, and one hundred percent of critical checkout routes while sampling healthy baseline requests at five percent.

  • Never forward raw HTTP headers, request bodies, or SQL bind parameters directly from application pods to external SaaS observability endpoints. Deploy an OpenTelemetry Collector processor pipeline inside your VPC using the transform processor (OTTL) to redact primary account numbers, Bearer JWTs, emails, and tax identifiers in flight before exporting sanitized telemetry over mTLS to ClickHouse or SigNoz.

  • Below roughly 1,500 gigabytes of monthly logs and traces, SigNoz Cloud Teams (starting at $49 per month base credit plus $0.30 per gigabyte for logs and traces and $0.10 per million metric samples) is far more economical than operating your own storage cluster. Once sustained telemetry crosses five to ten terabytes per month under strict PCI DSS v4.0.1 or HIPAA VPC residency rules, running an owned OpenTelemetry tail-sampling gateway into ClickHouse on EKS with NVMe hot disks and S3 Standard-IA cold tiers cuts three-year TCO by thirty percent versus SigNoz Cloud and over seventy-five percent versus Datadog.

  • Partnering with Idealogic's senior Central and Eastern European platform engineers at $75 per hour (versus typical US agency rates of about $165 per hour), a two to three week OpenTelemetry Collector Audit and Tail-Sampling Sprint costs $11,250 to $18,000, a managed SigNoz Cloud Enterprise migration with Terraform alert parity runs $18,000 to $27,000, and a turnkey 600-hour owned OpenTelemetry, ClickHouse EKS, S3-IA, and PostgreSQL 17 or 18 SLO control-plane build costs $45,000 ($99,000 at US rates), saving $455,400 against Datadog Enterprise over thirty-six months.

Still unanswered
Ask us directly

A senior engineer replies under 4 hours.