Scenarios for troubleshooting errors and monitoring application performance using Splunk APM 🔗

Buttercup Games, a fictitious game company, recently refactored its e-commerce site to go cloud native. The site uses microservices for the application architecture and containers for the underlying infrastructure. The company uses Splunk APM for finding root causes of errors, monitoring system performance, and tracking business KPIs.

Troubleshooting scenarios

Site reliability engineers, service owners, engineering executives, and performance engineers at Buttercup Games use Splunk APM for the following troubleshooting scenarios:

Monitoring scenarios

Site reliability engineers, service owners, engineering executives, and performance engineers at Buttercup Games use Splunk APM for the following monitoring scenarios:

To learn the specific steps for setting up and using APM features, see Set up Splunk APM.

This page was last updated on Feb 29, 2024.

Was this topic useful?

Did you know that you can edit this page? Learn how!

Was this documentation topic helpful?

Enter your email address if you would like someone from the documentation team to reply to your question or suggestion.

Please provide your comments here. Ask a question or make a suggestion.

Comment should have a minimum of 5 characters and a maximum of 1,000 characters.

Feedback submitted, thank you! We resolve documentation feedback based on the severity of the issue reported, as well as an assessment of the potential number of customers who might be affected.

If you have a question about using Splunk software, we encourage you to check Splunk Answers or Splunk community Slack to see if similar questions have been answered, or to post your question for others to answer. If you have an active support entitlement and believe that your situation is caused by a product defect, file a support case in the Support portal https://login.splunk.com/page/sso_redirect?type=portal.

We are currently moving to a new documentation site. Expect a delay in responding to your feedback and applying any updates based on your feedback. Thank you for your patience and understanding while we work to bring you an improved documentation experience!