Splunk Observability Cloud provides a number of capabilities that help customers isolate problems and provides multiple ways to solve those problems. For example, imagine that you have identified an error in charging customers in an online retail environment.
On the back end, Splunk APM provides a view that includes the microservices that contribute to the charge workflow. You could look more deeply into what might be in common with your erroneous transactions using Tag Spotlight. The Related Content feature helps you find the logs behind a trace, which might tell you even more about these errors. Splunk Observability Cloud surfaces logs coming from your Splunk platform, whether on-premises or in the cloud.
On the front end, you can track down this issue using Splunk Real User Monitoring to look into your user sessions. Splunk Observability Cloud brings in every single trace, so you can find a single transaction based on a session ID or other identifier. In this case, you might look for a long transaction and investigate what caused the transaction to be very slow. You can look at the transaction workflow in a map, as you can in Splunk APM, or you can look at this specific trace's waterfall.
Watch the following video to see a demo of how Splunk APM and Splunk Real User Monitoring can both be used to solve the same problem.