| Aspect | Observe | Splunk Observability / Splunk Platform | Datadog |
|--------|--------|----------------------------------------|---------|
| Starting Price | Logs from $0.49/GiB; Traces from $0.59/GiB; Metrics from $0.008/DPM (vendor-published starting points) | Splunk publishes observability pricing pages but exact starting costs vary by package; Splunk pricing is often multi-dimensional (platform, workload, entity/host, ingest depending on product) | Public list pricing exists for many Datadog modules, but effective cost often depends on hosts, ingested log volume, indexed vs archived logs, and add-on modules |
| Best For | Teams prioritizing committed-volume predictability and large-scale telemetry analysis; orgs willing to invest in learning/querying | Enterprises that want a broad platform and (often) security + observability adjacency; complex governance needs | Teams wanting broad integrations, mature SaaS UX, and a large ecosystem; strong for cloud-native environments |
| Key Strength | Transparent ingest-based starting prices; “no overages”; positive notes on UI speed and cost reduction after switching (per Gartner snippets) | Large enterprise presence; broad portfolio; mature ecosystem | Breadth of integrations and unified modules; strong market mindshare |
| Key Weakness | Reported UI/navigation friction, search usefulness issues, learning curve, and integration complexity (Gartner dislikes) | Common market criticism includes complexity and cost at scale; configuration overhead (varies by implementation) | Often criticized for cost growth at high telemetry volumes; pricing complexity across modules (common market theme) |
- Direct competitors and their key differentiators
- Splunk
- Often positioned for large enterprises and broader operational + security use cases.
- Observe directly markets “Observe vs Splunk” pages emphasizing cost and retention flexibility.
- Datadog
- Typically leads on integration breadth and packaged experiences.
- Peer comparison pages exist (e.g., PeerSpot “Datadog vs Observe”), though these are not primary evidence for product quality.
- New Relic
- Strong APM heritage and broad observability positioning.
- Grafana/Prometheus/Loki
- Strong open-source ecosystem and flexibility; can be lower software cost but higher operational burden.
- Elastic (ELK)
- Popular for logs/search; can be self-managed or cloud-managed; cost/performance tradeoffs depend heavily on indexing and retention.
- Honeycomb
- Strong event-based observability narrative and developer-centric workflows.
- Feature comparison: where does Observe excel vs lag behind?
- Likely excels (based on accessible evidence):
- UI speed and dashboard load performance (Gartner likes)
- OTEL support is explicitly praised (Gartner likes)
- Cost reduction after switching (qualitative Gartner snippet)
- Potential lag / risk areas (based on Gartner dislikes):
- UI navigability and multi-account switching
- Search usefulness
- Learning curve for advanced configuration and query building
- Integration complexity for certain tools/APIs
- Pricing comparison: value proposition vs alternatives
- Observe publishes unit-based starting prices and emphasizes “no overages,” which contrasts with many vendor pricing models that buyers perceive as opaque.
- However, committed volume still requires forecasting and negotiation, and does not automatically ensure the lowest cost for spiky or unpredictable workloads.
- Customer testimonials comparing this product to competitors
- Direct “we chose Observe over Datadog/Splunk because…” comparative quotes were not accessible in full detail in this run.
- A vendor-authored resource “Comparing Splunk vs Observe…” argues Splunk retention is often limited for cost reasons and that Observe users “typically implement a 13-month data retention” (vendor framing; not independently validated).
- Market share and adoption trends
- Not reliably quantifiable from the collected sources.
- Funding rounds and planned acquisition by Snowflake indicate strategic interest and likely growth, but do not provide market share.
- When customers choose competitors instead (and why)
- Based on complaint themes and competitor strengths:
- Choose Datadog when integration breadth and out-of-the-box experiences are prioritized.
- Choose Splunk when security/enterprise platform consolidation is a priority.
- Choose Grafana/OSS stacks when avoiding vendor lock-in or minimizing SaaS spend is primary (accepting higher ops overhead).