Lightstep, now known as ServiceNow Cloud Observability, is undergoing a significant digital transformation by strategically integrating its advanced observability capabilities into ServiceNow’s comprehensive digital workflow platform. This integration focuses on combining logs, metrics, and traces within a unified query language (UQL) to provide end-to-end visibility and streamline IT operations. Their approach emphasizes OpenTelemetry standards for consistent data ingestion and programmatic management of observability configurations.
This transformation creates critical dependencies on integrated data pipelines and standardized telemetry, while also introducing challenges related to platform migration and workflow consolidation. The sunsetting of the standalone Lightstep Cloud Observability product by March 2026 necessitates that existing customers migrate their observability data and incident management workflows. This page analyzes these initiatives, the inherent challenges, and the resulting sales opportunities for solution providers.
Lightstep Snapshot
Headquarters: San Francisco, California, United States
Number of employees: 51–200 employees
Public or private: Private (Subsidiary of Public Company)
Business model: B2B
Website: http://www.lightstep.com
Lightstep ICP and Buying Roles
Who Lightstep sells to
- Lightstep sells to enterprises managing complex, distributed microservices architectures.
- These companies rely on cloud-native applications for critical business operations.
Who drives buying decisions
-
VP of Engineering → Oversees application reliability and performance for cloud-native services.
-
Head of SRE (Site Reliability Engineering) → Manages system uptime, incident response, and observability toolchains.
-
Director of DevOps → Implements and maintains CI/CD pipelines and monitors application health.
-
Cloud Platform Architect → Designs and optimizes the cloud infrastructure and observability stack.
Key Digital Transformation Initiatives at Lightstep (At a Glance)
- Strategic Shift to Integrated Service Resilience: Re-orienting core observability into ServiceNow's IT Operations Management workflows.
- Unified Query Language for Cross-Platform Visibility: Implementing UQL for programmatic querying of telemetry data within ServiceNow.
- OpenTelemetry for Standardized Data Ingestion: Leveraging OpenTelemetry and the Collector for consistent telemetry data collection.
- Embedded Incident Response Workflows: Integrating incident response and alert correlation directly within the ServiceNow platform.
Where Lightstep’s Digital Transformation Creates Sales Opportunities
| Vendor Type | Where to Sell (DT Initiative + Challenge) | Buyer / Owner | Solution Approach |
|---|---|---|---|
| Observability Migration Tools | Strategic Shift to Integrated Service Resilience: historical trace data fails to transfer to new platforms. | Head of SRE, VP of Engineering | Migrate historical observability data to a new system while maintaining data integrity. |
| Strategic Shift to Integrated Service Resilience: existing dashboards and alerts do not port to alternative observability solutions. | Director of DevOps, Cloud Platform Architect | Convert existing observability configurations into a new platform's format. | |
| Strategic Shift to Integrated Service Resilience: custom reporting metrics are incompatible with replacement systems. | VP of Engineering, Data Platform Lead | Standardize and transform custom metrics for compatibility with alternative observability platforms. | |
| OpenTelemetry Governance Platforms | OpenTelemetry for Standardized Data Ingestion: instrumentation configuration drifts across development teams. | Head of SRE, Director of DevOps | Enforce consistent OpenTelemetry instrumentation standards across all services. |
| OpenTelemetry for Standardized Data Ingestion: telemetry data attributes do not align with internal tagging policies. | Cloud Platform Architect, VP of Engineering | Validate OpenTelemetry attribute consistency before data ingestion. | |
| OpenTelemetry for Standardized Data Ingestion: Collector configurations do not propagate across diverse cloud environments. | Director of DevOps, Infrastructure Engineer | Automate OpenTelemetry Collector deployment and configuration management. | |
| Incident Management Workflow Platforms | Embedded Incident Response Workflows: alert routing rules conflict between ServiceNow and legacy incident tools. | Head of SRE, Incident Response Manager | Consolidate and standardize alert routing logic across incident management systems. |
| Embedded Incident Response Workflows: on-call schedules do not synchronize across existing and new systems. | Head of SRE, Operations Manager | Integrate on-call schedules and escalation policies between platforms. | |
| Embedded Incident Response Workflows: incident context is lost when transitioning between tools. | Director of DevOps, VP of Engineering | Maintain complete incident context and data continuity across different platforms. | |
| Observability-as-Code Platforms | Implementing Observability-as-Code: UQL definitions for dashboards do not version control correctly in Git repositories. | Cloud Platform Architect, Director of DevOps | Manage observability definitions as code with version control and deployment pipelines. |
| Implementing Observability-as-Code: alert definitions generate syntax errors when deployed through CI/CD pipelines. | Director of DevOps, Site Reliability Engineer | Validate observability-as-code syntax and deployment integrity before production releases. | |
| Data Quality & Schema Enforcement | Unified Query Language for Cross-Platform Visibility: inconsistent schema definitions block UQL querying across data sources. | Data Architect, Head of Data Engineering | Enforce consistent data schemas for logs, metrics, and traces. |
| Unified Query Language for Cross-Platform Visibility: missing or incorrect data fields appear in UQL-generated reports. | VP of Engineering, Data Analyst | Detect and correct data discrepancies before UQL consolidates information. | |
| Unified Query Language for Cross-Platform Visibility: performance anomalies fail to correlate due to disparate data timestamps. | Head of SRE, Data Engineer | Standardize time synchronization across all telemetry data streams. |
Identify when companies like Lightstep are in-market for your solutions.
Spot buying signals, find the right prospects, enrich your data, and reach out with relevant messaging at the right time.
What makes Lightstep’s digital transformation unique
Lightstep's transformation stands out because it is driven by a strategic acquisition, leading to the sunsetting of its core product and a deep integration into a broader IT service management platform. This means the focus shifts from being a standalone observability leader to becoming a specialized component within ServiceNow's incident response and operations management capabilities. This approach heavily depends on unifying different data types (logs, metrics, traces) using OpenTelemetry standards and a proprietary Unified Query Language, enabling observability to be managed programmatically as code. The unique challenge lies in migrating existing Lightstep customers while evolving its technology within a new enterprise ecosystem.
Lightstep’s Digital Transformation: Operational Breakdown
DT Initiative 1: Strategic Shift to Integrated Service Resilience
What the company is doing
Lightstep's core observability features are being re-oriented to feed into ServiceNow's IT Operations Management and Incident Management workflows. This involves moving away from offering a standalone observability platform to a more integrated solution within the broader ServiceNow ecosystem. ServiceNow is prioritizing service resilience and MTTR reduction using Lightstep's capabilities.
Who owns this
- VP of Product Management
- Head of Engineering, ServiceNow ITOM
- Chief Technology Officer
Where It Fails
- Historical observability data from the standalone Lightstep product fails to transfer to replacement platforms.
- Existing dashboard and alert configurations do not port directly to alternative observability solutions.
- Custom reporting metrics from legacy Lightstep implementations are incompatible with new system requirements.
- Service level objective (SLO) definitions require manual re-creation on new platforms.
Talk track
Noticed Lightstep (ServiceNow Cloud Observability) is shifting its focus to integrated service resilience within the ServiceNow platform. Been looking at how other enterprise teams are migrating their observability data and configurations proactively instead of waiting for end-of-life dates, can share what’s working if useful.
DT Initiative 2: Unified Query Language for Cross-Platform Visibility
What the company is doing
Lightstep (ServiceNow Cloud Observability) developed a Unified Query Language (UQL) to allow users to query and correlate various telemetry data, including logs, metrics, and traces, through a single interface. This language facilitates deeper consistency, maintainability, and reproducibility across cloud-native architectures. It aims to simplify data analysis and enable observability-as-code within the ServiceNow environment.
Who owns this
- Head of Product Engineering
- VP of Engineering
- Data Platform Lead
Where It Fails
- Inconsistent schema definitions block UQL querying across different telemetry data sources.
- Missing or incorrect data fields appear in UQL-generated reports, impacting analysis accuracy.
- Performance anomalies fail to correlate across systems due to disparate data timestamps in UQL queries.
- UQL queries encounter errors when integrating data from external metrics providers like Datadog or Grafana.
Talk track
Saw Lightstep (ServiceNow Cloud Observability) is leveraging its Unified Query Language for cross-platform visibility. Been looking at how some data engineering teams are standardizing telemetry schema definitions upfront instead of troubleshooting query errors later, happy to share what we’re seeing.
DT Initiative 3: OpenTelemetry for Standardized Data Ingestion
What the company is doing
Lightstep (ServiceNow Cloud Observability) heavily relies on OpenTelemetry standards and the OpenTelemetry Collector for consistent and open telemetry data collection. This initiative ensures that diverse distributed systems can send their logs, metrics, and traces into the platform in a standardized format. It simplifies instrumentation and prepares data for unified analysis.
Who owns this
- Cloud Platform Architect
- Director of DevOps
- Head of Site Reliability Engineering
Where It Fails
- OpenTelemetry instrumentation configuration drifts across different development teams and microservices.
- Telemetry data attributes do not align with internal tagging and categorization policies.
- OpenTelemetry Collector configurations fail to propagate consistently across diverse cloud environments.
- Missing access tokens or expired credentials cause OpenTelemetry Collector data ingestion to stop.
Talk track
Looks like Lightstep (ServiceNow Cloud Observability) is standardizing data ingestion with OpenTelemetry. Been seeing teams enforce consistent instrumentation configurations across all microservices instead of debugging data gaps post-deployment, can share what’s working if useful.
DT Initiative 4: Embedded Incident Response Workflows
What the company is doing
ServiceNow is integrating incident response, on-call management, and alert correlation directly within its platform, utilizing Lightstep's observability insights. This aims to reduce context switching for SREs and streamline the incident resolution process by connecting real-time performance data with actionable response workflows. Lightstep Incident Response is a key part of this strategy.
Who owns this
- Head of Site Reliability Engineering
- Incident Response Manager
- VP of IT Operations
Where It Fails
- Alert routing rules conflict between ServiceNow's incident platform and legacy incident management tools.
- On-call schedules do not synchronize accurately across existing team management systems and ServiceNow.
- Critical incident context is lost when transferring issues between observability and incident response tools.
- Automated escalations fail to trigger due to misconfigured alert conditions within the integrated platform.
Talk track
Seems like Lightstep (ServiceNow Cloud Observability) is embedding incident response directly into its platform. Been looking at how some SRE teams are consolidating alert routing and on-call schedules across all their tools instead of managing fragmented systems, happy to share what we’re seeing.
Who Should Target Lightstep Right Now
This account is relevant for:
- Observability migration and data portability solution providers
- OpenTelemetry governance and management platforms
- Incident management and on-call automation tools
- Observability-as-Code and configuration management platforms
- Data quality and schema enforcement solutions for telemetry
- Cloud cost management platforms focused on observability data
Not a fit for:
- Basic infrastructure monitoring tools without distributed tracing
- Standalone log management tools without metrics or traces
- Generic IT service management solutions without observability integration
- Traditional application performance monitoring (APM) suites
- Tools that do not support OpenTelemetry standards
When Lightstep Is Worth Prioritizing
Prioritize if:
- You sell observability migration tools that support exporting and transforming historical telemetry data.
- You sell solutions for converting existing observability dashboards and alert configurations between platforms.
- You sell OpenTelemetry governance platforms that enforce consistent instrumentation and data attribute standards.
- You sell incident management solutions that integrate seamlessly with ServiceNow for alert routing and on-call scheduling.
- You sell observability-as-code platforms that manage UQL definitions for dashboards and alerts in version control.
- You sell data quality and schema enforcement tools for telemetry data used in unified querying.
Deprioritize if:
- Your solution does not address the challenges of migrating observability data or configurations off an existing platform.
- Your product is limited to basic monitoring functionality without deep integration into incident response workflows.
- Your offering does not support OpenTelemetry standards for data ingestion and instrumentation.
- Your solution requires significant manual effort for dashboard or alert re-creation.
Who Can Sell to Lightstep Right Now
Observability Migration and Data Portability Tools
OpenReplay - This company offers a developer-friendly session replay platform that captures logs, errors, and performance metrics.
Why they are relevant: Lightstep's end-of-life creates a need to migrate historical observability data while maintaining data integrity. OpenReplay can assist in capturing and replaying session-specific telemetry, ensuring critical debugging context is preserved as customers transition from the Lightstep platform.
Chronosphere - This company provides a cloud-native observability platform focused on managing metrics, traces, and logs at scale.
Why they are relevant: Existing Lightstep customers face challenges porting their custom reporting metrics and configurations to new systems. Chronosphere can offer a migration path by ingesting, transforming, and centralizing various telemetry types, ensuring continuity of service health monitoring beyond Lightstep's end-of-life.
OpenTelemetry Governance and Management Platforms
Splunk Observability Cloud - This company offers a comprehensive observability suite with full OpenTelemetry support for data ingestion and analysis.
Why they are relevant: Lightstep's reliance on OpenTelemetry means customers need tools to manage instrumentation configuration drift across microservices. Splunk Observability Cloud can provide governance for OpenTelemetry deployments, enforcing consistent standards and preventing data collection gaps during migration.
Honeycomb - This company provides a distributed tracing and observability platform that natively supports OpenTelemetry.
Why they are relevant: Telemetry data attributes often fail to align with internal tagging policies, leading to inconsistent analysis. Honeycomb's focus on structured data and query capabilities can help validate OpenTelemetry attribute consistency, ensuring data ingested from various sources meets organizational standards.
Incident Management Workflow Platforms
PagerDuty - This company offers an incident management platform that unifies alerting, on-call scheduling, and automated response.
Why they are relevant: Lightstep (ServiceNow Cloud Observability) is embedding incident response, but existing alert routing rules may conflict. PagerDuty can help consolidate and standardize alert routing logic, integrating seamlessly with ServiceNow's platform while managing on-call schedules and escalations.
VictorOps (Splunk) - This company provides an incident management platform that integrates monitoring, on-call, and incident resolution.
Why they are relevant: Critical incident context often gets lost when transitioning between observability and incident response tools. VictorOps can ensure complete incident context and data continuity, allowing SREs to maintain a single source of truth for alerts and remediation efforts.
Observability-as-Code and Configuration Management
HashiCorp Terraform - This company offers infrastructure-as-code software that allows users to define and provision infrastructure in a declarative language.
Why they are relevant: Lightstep's UQL enables observability-as-code, but UQL definitions for dashboards may not version control correctly. Terraform can manage observability configurations, including dashboards and alerts, as code, integrating them into existing CI/CD pipelines for consistent deployment.
Final Take
Lightstep (ServiceNow Cloud Observability) is undergoing a critical strategic shift, consolidating its robust observability features into ServiceNow’s broader platform while sunsetting the standalone product by March 2026. This creates visible breakdowns in data migration, configuration portability, and integration with existing IT workflows. This account presents a strong fit for sellers offering solutions that address observability data migration, OpenTelemetry governance, and enhanced incident management within integrated enterprise environments.
Identify buying signals from digital transformation at your target companies and find those already in-market.
Find the right contacts and use tailored messages to reach out with context.