How Splunk can help: Understanding the business impact of changes
Pushing a change to an application is often the top cause of an incident, and while avoiding incidents is ideal, it is not a realistic goal. Splunk Observability Cloud provides a number of capabilities to help you understand the impact of application changes so you can respond appropriately.
- Splunk Real User Monitoring provides a summary of your applications and metrics for the various pages your users interact with. These key metrics are compared with past metrics, so if things get worse, you can easily identify the situation and dig into it.
- To enable you to troubleshoot without reproducing issues, Splunk Observability Cloud captures every single trace, which means you can search and find any transaction you need to. Session search allows you to find the transactions. You can search for sessions by the ID or by filtering for a specific subset of transactions, like by browser, country, and more. Clicking into a session gives a full list of everything the user interacted with during their session and provides links correlated to information in Splunk Application Performance Monitoring.
- Distributed tracing helps you understand where in a microservices architecture you have latency or errors. It also helps you understand when certain workflows or data influence latency or errors.
- AlwaysOn Profiling tells you how CPU time and memory are performing. While distributed tracing focuses on transactions, AlwaysOn Profiling is able to get granular to the line of code. This profiling can be run in monoliths or microservices, and can be run all the time.
- By tracing data, you can normalize SQL and NoSQL queries to understand how long queries are taking and reveal where optimization is necessary.
Watch the following video to see a demo of how AlwaysOn Profiling and Database Query Performance in Splunk Application Performance Monitoring can be used to solve an adservice latency problem.