ServiceNow Cloud Observability (formerly LightStep)
Container monitoring tools
Application performance monitoring (APM) tools
Cloud infrastructure monitoring software
Database monitoring tools
Enterprise monitoring software
Log monitoring software
Observability solution suites software
DevOps software
Containerization software
Monitoring software
- Features
- Ease of use
- Ease of management
- Quality of support
- Affordability
- Market presence
Take the quiz to check if ServiceNow Cloud Observability (formerly LightStep) and its alternatives fit your requirements.
Contact the product provider
Free Trial
Free version unavailable
Small
Medium
Large
- Education and training
- Accommodation and food services
- Media and communications
What is ServiceNow Cloud Observability (formerly LightStep)
ServiceNow Cloud Observability (formerly LightStep) is an observability platform focused on distributed tracing and service performance analysis for cloud-native and microservices-based applications. It helps SRE, DevOps, and engineering teams detect, triage, and reduce the time to resolve incidents by correlating traces with metrics and logs and by analyzing service dependencies. The product is built around OpenTelemetry-based instrumentation and supports high-cardinality telemetry typical of modern distributed systems. It also integrates with ServiceNow workflows to connect technical signals to incident and operations processes.
Strong distributed tracing focus
The product is designed around end-to-end distributed tracing for microservices, which supports root-cause analysis across complex request paths. It provides service dependency views and trace-driven investigation workflows that help teams understand where latency and errors originate. This emphasis can be particularly useful for organizations that already instrument services with OpenTelemetry and need trace-centric troubleshooting.
OpenTelemetry-first instrumentation
Cloud Observability aligns closely with OpenTelemetry for collecting and exporting telemetry data. This reduces reliance on proprietary agents and can simplify standardization across teams and environments. It also supports modern cloud-native architectures where teams want consistent instrumentation across languages and platforms.
ServiceNow workflow integration
As part of the ServiceNow portfolio, the product can integrate observability signals with IT operations and incident workflows. This can help connect alerts and investigations to ticketing, on-call processes, and operational reporting. For organizations already using ServiceNow, this can reduce tool switching between monitoring and ITSM/ITOM processes.
Best fit for trace-led use
Teams primarily seeking broad infrastructure monitoring, deep host-level analytics, or extensive out-of-the-box cloud integrations may find the product less centered on those needs than trace-first platforms. Some organizations may still require additional tools for comprehensive infrastructure, network, or database-specific monitoring coverage. Fit is strongest when distributed tracing and service-level troubleshooting are the primary requirements.
Requires instrumentation maturity
To get full value, teams typically need consistent instrumentation and good telemetry hygiene across services. Implementing and maintaining OpenTelemetry collectors, sampling strategies, and semantic conventions can require engineering effort. Organizations with limited observability engineering capacity may experience longer time-to-value.
Cost and data governance complexity
Observability platforms can become expensive as telemetry volume and cardinality grow, especially in high-traffic microservices environments. Managing retention, sampling, and access controls becomes important to keep costs and compliance risks under control. Buyers often need careful sizing and governance planning before scaling usage broadly.
Plan & Pricing
Pricing model: Subscription-unit (usage-based) and Active service bundle (legacy)
Subscription-unit plan (current for contracts starting on or after May 4, 2023):
- You purchase a monthly number of subscription units and apply them to telemetry. ServiceNow does not publish a unit price on the public pricing page; you must contact ServiceNow for a custom quote.
Telemetry quantities that map to 1 subscription unit (official docs):
- Log data ingest: 20 GB = 1 subscription unit
- Log data hot retention: 40 GB-days = 1 subscription unit
- Log data cold retention: 200 GB-days = 1 subscription unit
- Trace data ingest: 10 GB = 1 subscription unit
- Trace data retention: 32 GB-days = 1 subscription unit
- Metrics: 25 Active Time Series (ATS) = 1 subscription unit
Active service bundle plan (legacy / other customers):
- Based on an allotted Active Service Bundle per contract; billed for ATS (Active Time Series), Logs (GB), Span Data (GB), and Streams. Overages apply when you exceed contracted limits.
Trial / free-tier notes (from official docs):
- Trial access to logs is provided for non-logging customers: send up to 1 GB of logs per organization per day with 3-day retention (trial logs stored in a shared pool and not guaranteed query performance). To get full logging access or other entitlements, contact Customer Success or Sales.
Other official notes:
- ServiceNow’s public pricing page for Cloud Observability requires contacting a ServiceNow representative to get a custom quote (no public per-unit or per-tier prices displayed).
- Cloud Observability End-of-Life / support notice: product is supported through March 1, 2026 or your subscription term end date (whichever is later).
Seller details
ServiceNow, Inc.
Santa Clara, CA, USA
2004
Public
https://www.servicenow.com/
https://x.com/servicenow
https://www.linkedin.com/company/servicenow/
