Item: Splunk Application Performance Monitoring (APM)
Rating: 10
Author: Verified User

Use Cases and Deployment Scope

Identify issues and deep dive when there is an issue. Also good to correlate the data between Splunk Core and Splunk 0lly. For the e2e view, it’s good to refer to the data sources onboarded and enable the correlation searches. Use Orel collectors to send metrics and traces, which could be populated to a dashboard.

Pros and Cons

Identify slowness.
Rca
Reduced MTTR.
Improve MTTI.

Documents.
Video
Custom metrics.

Return on Investment

Easy to identify issues.
Proactive monitoring.
Metrics and traces.

Usability

When there is an issue, it’s a win if one can easily identify the root cause. To do the same, it should allow the user to dig deep with multiple data points and compare the data and identify the anomaly. In this use case, it’s good to drive from Splunk 011y.

Key Insights

Do you think Splunk Application Performance Monitoring (APM) delivers good value for the price?

Yes

Are you happy with Splunk Application Performance Monitoring (APM)'s feature set?

Yes

Did Splunk Application Performance Monitoring (APM) live up to sales and marketing promises?

Yes

Did implementation of Splunk Application Performance Monitoring (APM) go as expected?

Yes

Would you buy Splunk Application Performance Monitoring (APM) again?

Yes

Other Software Used

Splunk Cloud, Splunk Enterprise, Splunk Enterprise Security (ES)

Likelihood to Recommend

Good for below cases 1. There is a front end and need to correlate data with front end data 2. multiple microservices and need to check the health of each system 3. correlate data from various sources 4. Application performance is a key to be captured 5. application performance is a key metric.

Splunk APM.

Overall Satisfaction with Splunk Application Performance Monitoring (APM)