Scenario: You are a site reliability engineer working in a cloud-native environment that runs several microservices to support an online store. Through alerts received from Splunk APM or customer complaints, you've identified a problem with your online checkout process. You need to troubleshoot and fix the problem to ensure that the bottom line does not suffer, and report on the impact afterwards.
To succeed in implementing this use case, you need the following dependencies, resources, and information.
- People: Site reliability engineer, DevOps engineer
- Technologies: Splunk Observability Cloud
- Feature: API integration, Splunk Real User Monitoring, Splunk Log Observer
How to use Splunk software for this use case
Depending on your environment, you might find it useful to do some or all of the following:
- Troubleshooting a high error rate alert on a checkout endpoint from APM
- Troubleshooting customer complaints of checkout latency issues
You might also be interested to:
Latency and errors in eCommerce environments can result in customers abandoning their planned purchases, with financial impact to your organization. Quickly identifying and fixing these issues results in fewer dollars lost and less frustrated customers.
The content in this guide comes from a .conf2020 talk, Logging for Observability, one of the thousands of Splunk resources available to help users succeed. In addition, these Splunk resources might help you understand and implement this use case: