The documentation in this section describes a product that is in closed beta, so it is subject to change before the final release. For more information, see Beta Features.
The Application Performance Monitor (APM) is a solution that helps you to analyze performance issues and runtime behavior.
This is the reference guide for Mansystems APM 2 for Mendix. It has the following chapters:
The sections below provide a short explanation of APM along with its features and possible uses.
2 Definition of APM
Mansystems APM is based on Wikipedia’s definition of Application Performance Management, with emphasis on these points:
- APM is the “monitoring and management of performance and availability of software applications”
- APM strives “to detect and diagnose complex application performance problems to maintain an expected level of service”
- APM is “the translation of IT metrics into business meaning (i.e., value)”
Of course, you need the basic infrastructure probes to measure hardware parts like the CPU, memory, and disk as well as components like the database and the web server. However, for higher quality support, you should also look at the application and how it is performing, especially linking this to the user’s business perspective.
We all know that software contains bugs, and of course we all test before we bring something into production. For users, an error is a sign that the application is not functioning. If the error appears unexpectedly, the user loses trust in the system. The standard reaction of Support is usually to ask questions (including whether the customer can reproduce the issue), to ask that logging be turned on, and to ask for a database dump so that they can investigate the issue in a safe environment.
The APM tools provide valuable information for analyzing the behavior and performance of an application in production. This allows for direct analysis without asking the customer to wait, reproduce, or deliver technical information. The same information is available during development as well to prevent issues before they appear in production.
3 Performance Statistics to See Performance Issues in Advance
Performance in applications is difficult to test during the initial/developing stage. The data set is too small and the exact usage by users (for example, their search behavior) is unknown. Even after applying all performance best practices while building a Mendix application, issues will still appear in production. Usually they appear over time as the data set grows, so the question is how can you see them coming.
Mendix APM collects statistical data about microflows, client API requests, and user click paths. These statistics are stored hourly and can be used to see trends before users sound the alarm. It is strongly advised for support to frequently check the longest and most frequently running microflows to see if they can be improved. These statistics can be drilled down into to investigate a performance issue. They show individual actions, loop iterations, and exactly where the obstacles are.
In development, it is advised to add checking in APM to the generic definition of done.
4 The Performance Recorder to Collect Individual Traces
When Support or DevOps wants to investigate a performance issue, they can use the APM Performance Recorder. It shows individual actions, loop iterations, and exactly where the obstacles are.
5 Your Flight Data Recorder
The runtime agent’s Trap feature is always listening on all levels of logging, up to the TRACE level. It is possible to configure the amount of seconds of logging it has to keep in memory. If an error occurs, the logging in memory and the error is stored in the APM manager database, which can provide information regarding what the runtime was proccessing at the time of the error.
The logs are used to collect Mendix Runtime log messages and store them in the APM manager database.
This gives remote access to log information, makes it available to consultants, and allows for easy searching and analyzing.