Introduction to Call Graph Profiling in Splunk APM
Learn what you can do with Call Graph Profiling in Splunk APM.
Alpha features described in this document are provided by Splunk to you "as is" without any warranties, maintenance and support, or service-level commitments. Splunk makes this alpha feature available in its sole discretion and may discontinue it at any time. These documents are not yet publicly available and we ask that you keep such information confidential. Use of alpha features is subject to the Splunk Pre-Release Agreement for Hosted Services.
Service map
- Business workflows
Call Graph Profiling
Call Graph Profiling collects stack traces to deliver deep trace code-level insights, which provide visibility into application interactions and performance across your system. As part of Splunk APM, Call Graph Profiling provides context to call stacks produced by instrumented applications.
After you get call graph data into Splunk Observability Cloud, you can explore the data directly from APM and visualize the performance of methods using call graphs.
A call graph is a visual representation of the method call hierarchy within a trace. A call graph displays general information about a call stack, such as total execution duration, time stamp that the execution started, exit calls, and method execution durations. Using Call Graph Profiling, you can locate, diagnose, and debug performance issues with your service.
What you can do with Call Graph Profiling
Learn what you can do with Call Graph Profiling in Splunk APM.
You can use Call Graph Profiling for Splunk APM to:
Visualize method execution. Get a detailed view of the sequence and hierarchy of method calls within your application, helping you understand the execution flow and dependencies.
Analyze performance bottlenecks. Identify slow or inefficient code paths by examining the time spent in each method call.
Optimize application performance. Use insights from the call graph to refactor code, improve efficiency, and reduce latency in your applications.
Call Graph Profiling for Splunk APM can identify issues such as:
High-latency methods. Detect methods that are taking longer than expected to execute and slowing down your application.
Inefficient code paths. Identify redundant or unnecessary method calls that can be optimized or eliminated.
Latency-intensive operations. Spot methods that cause excessive latency and impact system performance.
Lines of code that are causing errors and exceptions.
Supported languages for Call Graph Profiling
Learn what languages are supported for Call Graph Profiling in Splunk APM.
Language | Available instrumentation | Documentation |
---|---|---|
Java | Splunk Distribution of OpenTelemetry Java version 2.15.0 or higher |
Get started with Call Graph Profiling
Learn how to get started with Call Graph Profiling in Splunk APM.
To get started, instrument your application or service for Splunk APM and activate Call Graph Profiling. For instructions, see Get data into Splunk APM Call Graph Profiling.