Skip to main content


Splunk Lantern

Monitoring key telecommunications service metrics

Scenario: Communication service providers (CSPs) and Telcos host a large variety of services, such as voice and VoIP services, and traditional operations support system (OSS) and business support system (BSS) solutions.  They face challenges delivering reliable services to their customers in areas outside of the traditional business centers and corporate locations. Providing operational excellence across the business is key to supporting customers while maintaining corporate initiatives and objectives. In your CSP, you need to deploy a scalable data analytics architecture across the breadth of operations. 


To succeed in implementing this use case, you need the following dependencies, resources, and information.

  • People: Network engineer, NOC analyst, Business analyst
  • Technologies: Splunk Enterprise or Splunk Cloud Platform
  • Data: Telephony data for call detail records
  • CSV or KV lookup file that maps call dispositions to descriptions
  • CSV or KV lookup file that maps country codes in your CDR logs to country names

Your sourcetypes may not have the same fields as the ones demonstrated in the sample searches. Adjust field names as needed to match your environment.

How to use Splunk software for this use case

Depending on what information you have available, you might find it useful to identify some or all of the following: 


The insights provided from these searches reach multiple areas of your business. The searches related to failed calls and provide insights for monitoring, alerting, and troubleshooting. Searches related to call duration and volume can help with setting rates, targeting marketing campaigns, and forecasting capacity and service needs.

Additional resources

The searches in this guide are also included in the  Splunk Essentials for Telecommunications the app, which provides more information about how to implement them successfully in your telecom services maturity journey. In addition, this Splunk resource might help you understand and implement this use case:

  • Was this article helpful?