Obsfly

Comparison · vs SolarWinds DPA

SolarWinds DPA — sin el UX de 2010.

Misma profundidad de wait time en SQL Server, más una interfaz moderna, bandas de pronóstico aprendidas y despliegue SaaS o BYOC.

01.  Why teams move

What teams say in the first call.

  • DPA's UI is a Java-era artifact — slow page loads, dated tables, no mobile.
  • Per-instance licensing on Standard/Custom Edition gets expensive past ~30 instances.
  • Anomaly detection is threshold-based; no forecast bands.
  • No BYOC or sovereign deployment options.
  • Cross-DB unified pane is limited — Postgres/MySQL/Mongo each feel like separate products.

02.  Honest take

What SolarWinds DPA is genuinely good at.

We’re not interested in trash-talk. Here’s where SolarWinds DPA is the right call — useful even if you end up choosing Obsfly, because keeping SolarWinds DPA for some workloads can make sense.

  • + The historical wait-event analysis tradition — DPA invented this category.
  • + Strong Oracle and SQL Server depth for mature enterprise stacks.
  • + Mature alert routing and stable for shops that have run it for a decade.
  • + Acquired VividCortex (now folded in) brings solid query-digest tracking.

03.  Side by side

Obsfly vs SolarWinds DPA, line by line.

 
Obsfly
SolarWinds DPA
Wait-event analysis
1Hz sampling, multi-DB flame graphs
10s default, classic per-DB views
Pricing model
Flat per-DB / month, free tier 3 DBs
Per-instance perpetual + maintenance, OR subscription
Cross-DB unified pane
9 DBs, one UI
Per-DB views with limited cross-context
BYOC / Sovereign
Both supported (control / data plane split)
On-prem only; no managed-control-plane hybrid
Forecast bands
Default on every metric
Threshold-only
Modern UI
Next.js 15, sub-second loads, mobile-ready
Java applet legacy, slow on dense screens
AI / LLM-grounded suggestions
Built in
No
Cloud-native deploy
Helm + Terraform modules
Manual install, JVM tuning

04.  The math

Pricing snapshot.

Public list pricing where known; “contact sales” where not. Real bills are usually within 20% of these figures.

30 instances
~$1,170 / mo
~$60k–$90k perpetual + maintenance
100 instances
~$3,900 / mo
~$200k–$300k perpetual + maintenance
BYOC platform
$5k / mo flat
On-prem-only model handles this differently

05.  Switching

How teams actually switch.

Wait-event semantics preserved

Obsfly rolls Postgres / MySQL / Oracle / SQL Server wait events into the same class taxonomy DPA pioneered — operators don't relearn.

Run side-by-side

Both can scrape the same DB. Run a 30-day pilot to compare resolution and alert quality directly.

Export your DPA threshold set

Send us your DPA alert config; we rebuild as Obsfly alert rules grounded in forecast bands instead.

06.  FAQ

Common questions.

Does Obsfly support Oracle and SQL Server like DPA does?+

Yes. Oracle via v$ views (no Tuning/Diagnostics packs required) and SQL Server via Query Store + DMVs. See /oracle-monitoring and /sql-server-monitoring.

What about wait-event categories I rely on in DPA?+

Same taxonomy. We ship wait classes (CPU, IO, Lock, Network, Concurrency) per DB with the same definitions DPA uses, plus per-signature flame graphs.

We have DPA on-prem. Can we go BYOC?+

Yes — BYOC is the natural transition. Data plane runs in your VPC like DPA does, but the control plane (UI, alerting, AI) is Obsfly-managed. SOC2 path included.

· · ·

See it on your stack.

20-min comparison demo. Bring real queries from your SolarWinds DPA setup; we'll reproduce them in Obsfly live.

SolarWinds DPA Alternative — modern DBM with BYOC and AI · Obsfly