Michael Kopp

Those who know me know that I'm passionate about 3 things: rock climbing, physics, and performance. I've worked in performance monitoring and optimizations in enterprise environments for the better part of the last 10 years. Now as a Product Manager I am doing my best to build those experiences into Dynatrace.

Michael Kopp's articles

Databases finally have a place of their own

Because databases are often at the heart of applications, we’ve decided to give databases a dedicated section within Ruxit. You may have noticed a change to the Services page. As you can see below, the Services page no longer includes databases. This allows us to make the Services and Databases pages more specific to their respective use cases. As a first step in this direction notice that the filter bar and context actions have… read more

Service backtrace now includes referrers

Recently we introduced service backtrace functionality to enable you to see which request or browser click led to a specific service request or database statement. We then extended this functionality to include backtraces for SQL statements. Now we’ve extended the visibility even further by introducing HTTP referrers to Backtrace view. You’ll now find information about referring pages for all Web requests that contribute to a backtrace. read more

Enhanced database alerting and visibility

We’ve introduced a major enhancement to Ruxit database baselining, alerting, and visibility. Many of our customers are interested in understanding the performance of specific SQL statements. They want to know which browser click results in which specific SQL statement or what the impact of a slowdown or error with a specific SQL statement is. Ruxit now offers exactly this functionality. Performance and failure analysis of database statements When… read more

Enhanced detection for Tomcat, JBoss, and Glassfish

Some time ago we introduced the ability to detect Java process groups by defining Java system properties for individual Java processes. This option was previously only available for generic Java processes. Tomcat, JBoss, and other application servers were excluded because they have additional semantics (for example application server-specific cluster detection). We’ve now extended this feature to include Tomcat, JBoss, and Glassfish application server processes. To enable detection of these… read more

Analyze CPU consumption of background threads

Dynatrace is proud to announce a brand new feature: Background activity analysis. Just select Background activity from the navigation menu to access it. Most applications consist of one or more services and process requests. This is where the bulk of CPU is typically consumed by a process. However most applications also have background threads. Background threads perform work that isn’t related to any individual request. Dynatrace analyzes not only… read more

Service-level backtrace shows sequence of service calls

Ever wonder which services send requests to one of your back-end services? More than just knowing which service directly calls one of your services, what about the sequence of service calls that leads up to each request, all the way back up to the browser click that triggered the sequence of calls? Dynatrace service backtrace can provide you with exactly this information. Say for example that you’re analyzing a SQL… read more

Monitored-service merging: 1+1=1

Ruxit identifies services in your environment based on the deployment units that it detects. Deployment units vary based on service type. For example, in the case of Apache web services, Ruxit looks for virtual hosts. In the case of Java web applications, Ruxit looks for web applications and context roots. While this approach certainly does represent your deployed services, in some cases it may be too granular a… read more

Know when database statements are executed

Have you ever wondered which SQL statement is responsible for a detected response-time or load spike on your database? Ruxit can now tell you exactly which database statements are executed when in your environment. You’ll now find this information included in the Database statements list at the bottom of each database-service Details page and each database-operation Details pages. Adjust the analysis time frame Adjusting the analysis time frame results in an… read more

Root-cause analysis of ‘Suspension’ impacts

If you’ve used Ruxit to analyze the response times of web requests in your environment you may have noticed that some services list a hotspot called Suspension. Suspension time represents the amount of time that requests are suspended by the JVM, CLR, or V8 JavaScript engine during garbage collection activities. Ruxit tracks this and tells you how big an impact suspension has on your requests. To view the impact, click Suspension (see… read more

View top requests during analysis time frame

Have you ever wondered which requests your service processed during a specific time frame? For example, to better understand the reason behind a spike in response time? Ruxit now automatically shows you the Top web requests that a service processed during the selected analysis time frame. With this approach you can identify any unexpected requests and see if a specific request received more load than usual. To view list of requests processed… read more