Splunk IT Service Intelligence

Name: Splunk IT Service Intelligence
Brand: Splunk
Rating: 4.8 (112 reviews)

Leader

The cybersecurity and observability leader

Est 2003|Valuation $26.4B|Raised $1.7B

LinkedIn 799K|Website|Web traffic 1.0M|FTEs 9,231|HQ San Francisco, California, US

MarketsIncident Management & On-Call Infrastructure Monitoring Observability Platform

Splunk IT Service Intelligence screenshot

01Competitive Landscape

Narrative analysis

- Splunk ITSI vs Dynatrace: Splunk emphasizes ingestion and analysis of diverse data sources; Dynatrace is often selected for agent-based auto-instrumentation and automatic dependency mapping. - Splunk ITSI vs Datadog: Datadog is frequently selected for usability and broad SaaS integrations; however, Datadog users also report concerns about cost growth at scale. ITSI is often chosen where an existing Splunk deployment and cross-domain correlation requirements exist. - Splunk ITSI vs Moogsoft: Moogsoft focuses on event correlation and incident collaboration. ITSI competes by leveraging the broader Splunk platform and search capabilities.

Market adoption trends (supported observations)

Splunk positions ITSI within its broader observability narrative. Splunk is included in industry analyst coverage for observability platforms; vendor announcements reference such recognitions.

	Splunk ITSI	Dynatrace	Datadog
Starting Price	Quote-based; depends on Splunk platform licensing and ITSI add-on (no consistent public list price)	Public pricing options; consumption-oriented models (capability-dependent)	Public pricing list; common entry involves per-host infrastructure pricing with add-ons
Typical Use Case	Enterprises with an existing Splunk investment that require service-centric correlation across diverse data sources	Organizations needing deep APM, automatic topology discovery, and agent-based instrumentation	Cloud-native teams seeking rapid SaaS onboarding, broad integrations, and developer-focused UX
Key Strength	Cross-domain correlation using Splunk data platform and configurable service modeling/glass tables	Automatic instrumentation and dependency mapping geared toward APM use cases	Wide product breadth, fast onboarding, and extensive SaaS integrations
Key Weakness	Implementation complexity; pricing perception tied to platform licensing; dependency on data hygiene	Can be costly at scale and requires learning the platform; proprietary telemetry model	Costs can increase with add-ons and data volumes; pricing complexity for some use cases

01Competitive Landscape

Narrative analysis

Splunk ITSI vs Dynatrace: Splunk emphasizes ingestion and analysis of diverse data sources; Dynatrace is often selected for agent-based auto-instrumentation and automatic dependency mapping.
Splunk ITSI vs Datadog: Datadog is frequently selected for usability and broad SaaS integrations; however, Datadog users also report concerns about cost growth at scale. ITSI is often chosen where an existing Splunk deployment and cross-domain correlation requirements exist.
Splunk ITSI vs Moogsoft: Moogsoft focuses on event correlation and incident collaboration. ITSI competes by leveraging the broader Splunk platform and search capabilities.

Market adoption trends (supported observations)

Splunk positions ITSI within its broader observability narrative. Splunk is included in industry analyst coverage for observability platforms; vendor announcements reference such recognitions.

	Splunk ITSI	Dynatrace	Datadog
Starting Price	Quote-based; depends on Splunk platform licensing and ITSI add-on (no consistent public list price)	Public pricing options; consumption-oriented models (capability-dependent)	Public pricing list; common entry involves per-host infrastructure pricing with add-ons
Typical Use Case	Enterprises with an existing Splunk investment that require service-centric correlation across diverse data sources	Organizations needing deep APM, automatic topology discovery, and agent-based instrumentation	Cloud-native teams seeking rapid SaaS onboarding, broad integrations, and developer-focused UX
Key Strength	Cross-domain correlation using Splunk data platform and configurable service modeling/glass tables	Automatic instrumentation and dependency mapping geared toward APM use cases	Wide product breadth, fast onboarding, and extensive SaaS integrations
Key Weakness	Implementation complexity; pricing perception tied to platform licensing; dependency on data hygiene	Can be costly at scale and requires learning the platform; proprietary telemetry model	Costs can increase with add-ons and data volumes; pricing complexity for some use cases