Processing of Open Telemetry Data in NOW for ITOM Event Management

Piyush26
Giga Contributor

‎05-07-2025 05:39 AM - edited ‎05-07-2025 05:41 AM

Hello Community,

 

I am reaching out to you to seek a suggestion on processing of Open Telemetry Data in NOW.My Org has a good implementation of ITOM Event Management and have many Monitoring/Observability solution integrated.As ServiceNow cannot process the Open Telemetry data I would like to understand what are the alternatives any one is using to accomplish the same.

Any guidance would help !

 

Thanks in advance.

 

Regards,

Piyush

Labels:
0 Helpfuls
  • 494 Views
1 REPLY 1

xsinghp
Tera Contributor

‎05-12-2025 11:04 PM

Hi Piyush,

 

The question is very generic and doesn't mention the specific requirements, but I'll try to answer. 

When ServiceNow cannot directly process OpenTelemetry data due to its limitations, organizations often look for alternative solutions to handle and analyze this data effectively. Here are some common alternatives that organizations might consider:

  1. External Data Processing Tools: Many organizations choose to use external data processing tools or platforms such as Splunk, Elastic Stack (Elasticsearch, Logstash, Kibana), Prometheus, Grafana, or Datadog to ingest, process, and analyze OpenTelemetry data. These tools offer powerful data processing and visualization capabilities that can handle the volume and variety of OpenTelemetry data.

  2. Custom Integration Solutions: Organizations may opt to develop custom integration solutions or middleware to transform OpenTelemetry data into a format that can be ingested by ServiceNow. This could involve building data pipelines, leveraging APIs, or developing connectors to bridge the gap between OpenTelemetry data and ServiceNow.

  3. Data Aggregation and Transformation Layers: Implementing a data aggregation and transformation layer between OpenTelemetry data sources and ServiceNow can help preprocess and normalize the data before forwarding it to ServiceNow. Tools like Apache Kafka, Apache NiFi, or custom ETL processes can be used for this purpose.

  4. Third-Party Integration Services: Utilizing third-party integration services or platforms that specialize in integrating diverse data sources with ServiceNow can be another option. These services provide pre-built connectors and configurations to streamline the integration of OpenTelemetry data with ServiceNow.

  5. Event Management Systems: Implementing specialized event management systems that are compatible with OpenTelemetry data formats and can integrate seamlessly with ServiceNow can also be a viable alternative to handle this type of data.

  6. Hybrid Solutions: Organizations may opt for hybrid solutions combining elements of the above alternatives to create a custom approach that best fits their requirements and constraints.

When selecting an alternative solution to handle OpenTelemetry data in the absence of direct integration with ServiceNow, it is important to consider factors such as data volume, complexity, real-time requirements, scalability, ease of maintenance, and the overall alignment with the organization's IT and data management strategy.

0 Helpfuls