Splunk APM Blogs

Application Performance Monitoring (APM) as a discipline and as a collection of supporting technologies has evolved rapidly since a distinct recognisable market for APM products first emerged in the 2007 - 2008 time frame. While there are many who would argue that APM has mutated into or been replaced by Observability, it makes more sense to see APM as one of many possible use cases now able to exploit the functionalities that Observability brings to the table - particularly when combined with AI.

New Splunk APM releases help you quickly identify the biggest problems impacting customer experience and service performance across your applications.

Splunk Observability is making it quicker and easier to troubleshoot latency in MySQL and NoSQL databases, with two new enhancements.

We’re excited to share new Splunk capabilities to help measure how code performance impacts your services – Splunk APM’s AlwaysOn Profiling now supports .NET and Node.js applications for CPU profiling and Java applications for memory profiling.

Splunk now offers fully integrated synthetic monitoring within Observability, helping IT and engineering teams proactively detect and resolve performance problems before they reach customers, with full visibility from the end user experience, through backend service performance

We're extremely proud that in its inaugural report, GigaOm Radar for Application Performance Monitoring (APM) Report, 2021*, Splunk was named a Leader and one of only two Fast Movers.

Splunk RUM Frontend Error Monitoring Helps engineering teams quickly scope, prioritize, and isolate their most impactful customer-facing JavaScript errors.

Splunk APM now includes AlwaysOn Profiling for Java applications, providing app developers and service owners continuous visibility of code level performance to troubleshoot production issues faster.

Splunk APM’s enhanced database visibility now helps you find slow and high execution queries causing service performance issues in SQL databases, no instrumentation required. On-call Service owners and SREs can quickly identify if a database is causing performance issues, isolate the query responsible, and pinpoint root cause within distributed systems, to troubleshoot faster.