Introduction to Splunk APM 🔗
What is Splunk APM? 🔗
Collect traces and spans to monitor your distributed applications with Splunk Application Performance Monitoring (APM). A trace is a collection of actions, or spans, that occur to complete a transaction. Splunk APM collects and analyzes every span and trace from each of the services that you have connected to Splunk Observability Cloud to give you full-fidelity access to all of your application data.
For an interactive walkthrough of Splunk APM, see APM Scenarios.
Get your data into Splunk APM 🔗
To start using APM, see Set up Splunk APM.
If you have already instrumented your applications but are not seeing your data coming into APM as you expect, see Troubleshoot your instrumentation.
For information about Splunk APM use cases, see Scenarios for troubleshooting errors and monitoring application performance using Splunk APM.
To see an example of using Splunk Observability Cloud components together, see Scenario: Kai troubleshoots an issue from the browser to the back end using Splunk Observability Cloud.
What can you do with Splunk APM? 🔗
The following table provides an overview of what you can do with Splunk APM:
Do this |
With this tool |
Link to documentation |
|---|---|---|
Start to gain insights from your data in minutes using default landing page and service dashboards. |
Landing page |
|
View all of your services and their dependency relationships in the service map. |
Service map |
|
Get a top-down view of your services that provides the request and error rate or latency by each of your indexed span tags in Tag Spotlight. For instance, you can see at a glance how your services are performing by |
Tag Spotlight |
|
Index additional span tags to break down and analyze application performance along any dimension, so that you can customize views like Tag Spotlight to your particular needs. |
Span tags |
|
Use built-in dashboards to assess service, endpoint, and Business Workflow system health at a glance. |
Built-in dashboards |
|
Search all traces from all of your systems, with no sampling, so you can be confident the specific trace you need to resolve an edge cases is retained. |
Trace Analyzer |
|
Use detectors to alert with custom alert, request, and duration (RED) metrics to monitor error rate and latency across all of your services. |
Detectors and alerts |
|
Correlate traces that make up end-to-end transactions in your system to monitor the workflows you care about most |
Business Workflows |
|
Jump between components of Splunk Observability Cloud by selecting related data |
Related Content |
|
Dynamically link Splunk APM properties to relevant resources |
Global data links |
Use Data Links to connect APM properties to relevant resources |