detecting java processes

Crash analysis for processes is now available!

Processes crash for a multitude of reasons and it’s often difficult to understand the root causes that contribute to such crashes. This is why Dynatrace is proud to announce the availability of crash analysis for processes. As before, when a monitored process crashes, you’ll see a Process crash entry in the Events section of each affected Process and Host page. The example process below has some availability problems (shown in red on the timeline). By selecting… 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

Customizing Dynatrace process detection

Ruxit automatically detects process types like Tomcat, JBoss, Apache web server, MongoDB, and many others. For each process type Ruxit looks for specific patterns to identify processes that should logically be grouped together into “process groups” for monitoring purposes. A “process group” is a set of processes that perform the same function across multiple hosts. It also ensures that Ruxit can present continuous charts and information for a particular Application server… read more