Application Response Time Measurement Tools provided by MyARM support C/C++, Java, C# and Python programming languages. We provide different editions addressing different environments and needs.

Our Community Edition is available free of charge and provides a full-fledged ARM 4.0 agent implementation.

The following table gives an overview of the available editions and their support for programming languages and analysis tools. By clicking on an edition name additional information regarding the components contained in the edition and their features will be displayed.

Overview

  • Editions
  • Community
  • C/C++
  • Java
  • C#
  • Standard
  • Enterprise
  • Download
    DocumentsHTML, PDFHTML, PDFHTML, PDFHTML, PDFHTML, PDFHTML, PDF
    Base pricefree1200 €1200 €1200 €1500 €1800 €
    Purchase-PurchasePurchasePurchasePurchasePurchase
    Operating SystemWindows, LinuxWindows, LinuxWindows, LinuxWindows, LinuxWindows, LinuxWindows, Linux
    ARM 4.0 Language Bindings
    ARM 4.0 C++++
    ARM 4.0 Java++++
    ARM 4.0 C#+++
    ARM 4.0 Python++
    ARM 4.0 Language Frameworks
    ARM 4.0 C++++++
    ARM 4.0 QArm4++++
    ARM 4.0 shell++
    Analysis tools
    Command line tools+++++
    Manager (*)(*) The manager uses WebKit for rendering web 2.0 content and launches appropriate stand-alone web-server in background. Its available on Windows and Linux OS.(GUI)++++++
    Web applications (*)

    (*) Following Web applications are available:

    myarmbrowser
    Browser to analyse single measurements and transaction chains
    myarmrtsbrowser (Add-on RTS)
    Browser to analyse transaction statistics using different time intervals (hour, day, month, year)
    myarmrtsmonitor (Add-on RTS)
    monitor current transaction statistics using different time interval (current hour(s) or day)
    myarmadmin (Add-on RTS, RTC or RTN)
    administration of various global configurations (RTS, RTC, RTN)
    (WUI)
    browserbrowser, rtsbrowser, rtsmonitor, adminbrowser, rtsbrowser, rtsmonitor, adminbrowser, rtsbrowser, rtsmonitor, adminbrowser, rtsbrowser, rtsmonitor, adminbrowser, rtsbrowser, rtsmonitor, admin
    Supported databases
    SQLite3® (*)(*) SQLite3® is included.++++++
    MySQL® (*)
    (*) The following versions of MySQL® are supported:
    • MySQL 5.0
    • MySQL 5.1
    • MySQL 5.5
    +++++
    MariaDB® (*)
    (*) The following versions of MariaDB® are supported:
    • MariaDB 5.5
    • MariaDB 10.0
    +++++
    Deployment features
    myarmdaemon (*)
    (*) myarmdaemon is used in conjunction with the archive-, TCP- and/or file datasink :
    archive
    tcp
    The TCP datasink connects to a myarmdaemon using a TCP/IP socket and forwards measured ARM data to the that daemon. The myarmdaemon reads the data in and forwards the to its configured data sink
    file
    The file datasink writes measured ARM data to files on the local hard drive. The myarmdaemon reads these ARM data files and forwards it to its configured datasink
    tcparchive, file, tcparchive, file, tcparchive, file, tcparchive, file, tcparchive, file, tcp
    File storage (*)
    (*) is used for temporarily store ARM data into local hard drive if the data sink (myarmdaemon or database) is currently not available (disconnected). After a reconnect all temporarily stored ARM data will be forwarded to its destination
    +++++
    Event flow auto response (*)
    (*) With ARM 4.1 event flows are introduced. Event flows can start and end at different hosts thus to calculate the real response time synchronized clocks are needed. To avoid this need MyARM is able to automatically send a response if the end of the flow is stopped to the start from the event flow.

    This feature is currently only available for the C/C++ agent.
    +++
    Add-ons
    Multiple database connections (*)(*) Multiple database connections support for high ARM transaction measurement loads using MySQL or MariaDB databases+++++
    RTS: Real time statistics (*)(*) Real time statistics (RTS) Add-on calculates and records the statistics in a database.+++++
    RTC: Runtime configuration (*)(*) Runtime configuration (RTC) is used to adopt the behaviour of a running ARM instrumented application. For example transaction measurements can be enabled or disabled.+++++
    RTN: Runtime notifications (*)(*) Runtime notifications (RTN) are created according to predefined RTS or transaction measurement conditions. If a condition occurs a runtime event is created and stored in database.

    The myarmdaemon reads these runtime events and creates notifications (executing a script) for it.
    +++++
    FCGI: FastCGI (*)(*) All web applications can be deployed by a standalone HTTP server or to be integrated into an existing server landscape using FastCGI.+++++
    ARCH: ∞ Archiv (*)(*) Unlimited archive. By default 1 million measurements per day are licensed and stored.+++++
    CSVE: CSV-Export (*)(*) CSV export TCP/IP interface to export ARM transaction measurements exactly once (e.g. Apache Spark).+++++
    (*) Move mouse over cell for a brief description

    The diagram on the shows which components can be used in the Enterprise edition. Move the mouse over or tip the particular host to get a brief description.

    1. Language bindings for C/C++ and C#: A C/C++ application as well a C# application are using the ARM 4.0 interfaces to measure transactions
    2. The MyARM agent implementation supports following components:
      1. TCP/IP Dataink to send all ARM dat to the myarmdaemon
      2. Event flow auto reply handler and Apache handler
    1. Language bindings for Java and Python#: A Java application as well a Python application are using the ARM 4.0 interfaces to measure transactions
    2. The MyARM agent implementation supports following components:
      1. TCP/IP Dataink to send all ARM dat to the myarmdaemon
      2. Event flow auto reply handler
    1. All MyARM web application can be used from a stanadrd Web-Browser
    2. The myarmmanager provides an easy to use graphical user interface to access all MyARM web applications
    1. myarmdaemon collects ARM data from other hosts and stores it into a database
    2. SQLite3® database support
    3. myarmbrowser HTTP server for individual case analysis started by the myarmdaemon
    Community Edition Komponenten

    Legend

    Legend

    The diagram on the shows which components can be used in the C/C++ edition. Move the mouse over or tip the particular host to get a brief description.

    1. Language bindings for C/C++: A C application is using the ARM 4.0 interfaces to measure transactions
    2. The MyARM agent implementation supports following components:
      1. File data sink
      2. Runtime configuration component to manager recieved configuration during runtime
      3. Various handler to adopt the behaviour of the agent using runtime configurations
    3. myarmdaemon
      1. reads files written by the file data sink
      2. forwards this data using the TCP/IP Datensenke to another myarmdaemon
      3. receives runtime configurations send from another myarmdaemon over a TCP/IP connection and stores the runtime configuration into the local file system
    1. Language bindings for C/C++: A C++ application is using the ARM 4.0 interfaces to measure transactions
    2. The MyARM agent implementation supports following components:
      1. TCP/IP data sink
      2. Runtime configuration component to manage recieved configuration during runtime
      3. Various handler to adopt the behaviour of the agent using runtime configurations
      4. Filestorage component to write/read ARM data to/from a temporary file if the datasink is currently not able to store the data (TCP/IP connection down). When the TCP/IP connection is up again all stored ARM data will be send
    1. All MyARM web application can be used from a stanadrd Web-Browser
    2. MyARM applications
      1. The myarmmanager provides an easy to use graphical user interface to access all MyARM web applications
      2. Command line tools such as myarmquery are able to connect to a database directly (except SQLite3® Databases)
    1. myarmdaemon collects and aggregates ARM data received from other hosts and provides interfaces for the web applications
      1. receives runtime configurations from the myarmadmin web application over a TCP/IP connection, stores this runtime configuration on local filesystem and distributes the data to connected myarmdaemon processes over a TCP/IP connection
      2. aggregates received ARM data into statistics in (nearly) realtime
      3. depending on configuration writes ARM data
        1. into a database
        2. or into the filesystem based MyARM archive
      4. MyARM archive TCP/IP interface for archive queries
    2. MySQL®, MariaDB and SQLite3® database support
    3. Multiple database connections for high transaction loads (Add-on)
    4. MyARM archive SQLite3® database to store ARM metadata (e.g. application- and transaction names)
    5. filesystem based MyARM archive to store ARM measurement data efficiently and a high performance, scalable interface to query the archive using the myarmbrowser web application
    6. CSV export TCP/IP interface to export ARM transaction measurements exactly once (e.g. Apache Spark)
    7. MyARM HTTP servers started by the myarmdaemon
      1. myarmbrowser for individual case analysis
      2. myarmrtsbrowser and myarmrtsmonitor for statistical analysis and 24 hours monitoring
      3. myarmadmin to configure the MyARM system globally
    C/C++ Edition components

    Legend

    Legend

    The diagram on the shows which components can be used in the Java edition. Move the mouse over or tip the particular host to get a brief description.

    1. Language bindings for Java: A Java application is using the ARM 4.0 interfaces to measure transactions
    2. The MyARM agent implementation supports following components:
      1. File data sink
      2. Runtime configuration component to manager recieved configuration during runtime
      3. Various handler to adopt the behaviour of the agent using runtime configurations
    3. myarmdaemon
      1. reads files written by the file data sink
      2. forwards this data using the TCP/IP Datensenke to another myarmdaemon
      3. receives runtime configurations send from another myarmdaemon over a TCP/IP connection and stores the runtime configuration into the local file system
    1. Language bindings for Java: A Java application is using the ARM 4.0 interfaces to measure transactions
    2. The MyARM agent implementation supports following components:
      1. TCP/IP data sink
      2. Runtime configuration component to manage recieved configuration during runtime
      3. Various handler to adopt the behaviour of the agent using runtime configurations
      4. Filestorage component to write/read ARM data to/from a temporary file if the datasink is currently not able to store the data (TCP/IP connection down). When the TCP/IP connection is up again all stored ARM data will be send
    1. All MyARM web application can be used from a stanadrd Web-Browser
    2. MyARM applications
      1. The myarmmanager provides an easy to use graphical user interface to access all MyARM web applications
      2. Command line tools such as myarmquery are able to connect to a database directly (except SQLite3® Databases)
    1. myarmdaemon collects and aggregates ARM data received from other hosts and provides interfaces for the web applications
      1. receives runtime configurations from the myarmadmin web application over a TCP/IP connection, stores this runtime configuration on local filesystem and distributes the data to connected myarmdaemon processes over a TCP/IP connection
      2. aggregates received ARM data into statistics in (nearly) realtime
      3. depending on configuration writes ARM data
        1. into a database
        2. or into the filesystem based MyARM archive
      4. MyARM archive TCP/IP interface for archive queries
    2. MySQL®, MariaDB and SQLite3® database support
    3. Multiple database connections for high transaction loads (Add-on)
    4. MyARM archive SQLite3® database to store ARM metadata (e.g. application- and transaction names)
    5. filesystem based MyARM archive to store ARM measurement data efficiently and a high performance, scalable interface to query the archive using the myarmbrowser web application
    6. CSV export TCP/IP interface to export ARM transaction measurements exactly once (e.g. Apache Spark)
    7. MyARM HTTP servers started by the myarmdaemon
      1. myarmbrowser for individual case analysis
      2. myarmrtsbrowser and myarmrtsmonitor for statistical analysis and 24 hours monitoring
      3. myarmadmin to configure the MyARM system globally
    Java Edition components

    Legend

    Legend

    The diagram on the shows which components can be used in the C# edition. Move the mouse over or tip the particular host to get a brief description.

    1. Language bindings for C#: A C# application is using the ARM 4.0 interfaces to measure transactions
    2. The MyARM agent implementation supports following components:
      1. File data sink
      2. Runtime configuration component to manager recieved configuration during runtime
      3. Various handler to adopt the behaviour of the agent using runtime configurations
    3. myarmdaemon
      1. reads files written by the file data sink
      2. forwards this data using the TCP/IP Datensenke to another myarmdaemon
      3. receives runtime configurations send from another myarmdaemon over a TCP/IP connection and stores the runtime configuration into the local file system
    1. Language bindings for C#: A C# application is using the ARM 4.0 interfaces to measure transactions
    2. The MyARM agent implementation supports following components:
      1. TCP/IP data sink
      2. Runtime configuration component to manage recieved configuration during runtime
      3. Various handler to adopt the behaviour of the agent using runtime configurations
      4. Filestorage component to write/read ARM data to/from a temporary file if the datasink is currently not able to store the data (TCP/IP connection down). When the TCP/IP connection is up again all stored ARM data will be send
    1. All MyARM web application can be used from a stanadrd Web-Browser
    2. MyARM applications
      1. The myarmmanager provides an easy to use graphical user interface to access all MyARM web applications
      2. Command line tools such as myarmquery are able to connect to a database directly (except SQLite3® Databases)
    1. myarmdaemon collects and aggregates ARM data received from other hosts and provides interfaces for the web applications
      1. receives runtime configurations from the myarmadmin web application over a TCP/IP connection, stores this runtime configuration on local filesystem and distributes the data to connected myarmdaemon processes over a TCP/IP connection
      2. aggregates received ARM data into statistics in (nearly) realtime
      3. depending on configuration writes ARM data
        1. into a database
        2. or into the filesystem based MyARM archive
      4. MyARM archive TCP/IP interface for archive queries
    2. MySQL®, MariaDB and SQLite3® database support
    3. Multiple database connections for high transaction loads (Add-on)
    4. MyARM archive SQLite3® database to store ARM metadata (e.g. application- and transaction names)
    5. filesystem based MyARM archive to store ARM measurement data efficiently and a high performance, scalable interface to query the archive using the myarmbrowser web application
    6. CSV export TCP/IP interface to export ARM transaction measurements exactly once (e.g. Apache Spark)
    7. MyARM HTTP servers started by the myarmdaemon
      1. myarmbrowser for individual case analysis
      2. myarmrtsbrowser and myarmrtsmonitor for statistical analysis and 24 hours monitoring
      3. myarmadmin to configure the MyARM system globally
    C# Edition components

    Legend

    Legend

    The diagram on the shows which components can be used in the Standard edition. Move the mouse over or tip the particular host to get a brief description.

    1. Language bindings for C/C++: A C/C++ application is using the ARM 4.0 interfaces to measure transactions
    2. The MyARM agent implementation supports following components:
      1. File data sink
      2. Runtime configuration component to manager recieved configuration during runtime
      3. Various handler to adopt the behaviour of the agent using runtime configurations
    3. myarmdaemon
      1. reads files written by the file data sink
      2. forwards this data using the TCP/IP Datensenke to another myarmdaemon
      3. receives runtime configurations send from another myarmdaemon over a TCP/IP connection and stores the runtime configuration into the local file system
    1. Language bindings for Java: A Java application is using the ARM 4.0 interfaces to measure transactions
    2. The MyARM agent implementation supports following components:
      1. TCP/IP data sink
      2. Runtime configuration component to manage recieved configuration during runtime
      3. Various handler to adopt the behaviour of the agent using runtime configurations
      4. Filestorage component to write/read ARM data to/from a temporary file if the datasink is currently not able to store the data (TCP/IP connection down). When the TCP/IP connection is up again all stored ARM data will be send
    1. All MyARM web application can be used from a stanadrd Web-Browser
    2. MyARM applications
      1. The myarmmanager provides an easy to use graphical user interface to access all MyARM web applications
      2. Command line tools such as myarmquery are able to connect to a database directly (except SQLite3® Databases)
    1. myarmdaemon collects and aggregates ARM data received from other hosts and provides interfaces for the web applications
      1. receives runtime configurations from the myarmadmin web application over a TCP/IP connection, stores this runtime configuration on local filesystem and distributes the data to connected myarmdaemon processes over a TCP/IP connection
      2. aggregates received ARM data into statistics in (nearly) realtime
      3. depending on configuration writes ARM data
        1. into a database
        2. or into the filesystem based MyARM archive
      4. MyARM archive TCP/IP interface for archive queries
    2. MySQL®, MariaDB and SQLite3® database support
    3. Multiple database connections for high transaction loads (Add-on)
    4. MyARM archive SQLite3® database to store ARM metadata (e.g. application- and transaction names)
    5. filesystem based MyARM archive to store ARM measurement data efficiently and a high performance, scalable interface to query the archive using the myarmbrowser web application
    6. CSV export TCP/IP interface to export ARM transaction measurements exactly once (e.g. Apache Spark)
    7. MyARM HTTP servers started by the myarmdaemon
      1. myarmbrowser for individual case analysis
      2. myarmrtsbrowser and myarmrtsmonitor for statistical analysis and 24 hours monitoring
      3. myarmadmin to configure the MyARM system globally
    Standard Edition components

    Legend

    Legend

    The diagram on the shows which components can be used in the Enterprise edition. Move the mouse over or tip the particular host to get a brief description.

    1. Language bindings for C/C++ and C#: A C/C++ application as well a C# application are using the ARM 4.0 interfaces to measure transactions
    2. The MyARM agent implementation supports following components:
      1. File data sink
      2. Runtime configuration component to manager recieved configuration during runtime
      3. Various handler to adopt the behaviour of the agent using runtime configurations
    3. myarmdaemon
      1. reads files written by the file data sink
      2. forwards this data using the TCP/IP Datensenke to another myarmdaemon
      3. receives runtime configurations send from another myarmdaemon over a TCP/IP connection and stores the runtime configuration into the local file system
    1. Language bindings for Java and Python#: A Java application as well a Python application are using the ARM 4.0 interfaces to measure transactions
    2. The MyARM agent implementation supports following components:
      1. TCP/IP data sink
      2. Runtime configuration component to manage recieved configuration during runtime
      3. Various handler to adopt the behaviour of the agent using runtime configurations
      4. Filestorage component to write/read ARM data to/from a temporary file if the datasink is currently not able to store the data (TCP/IP connection down). When the TCP/IP connection is up again all stored ARM data will be send
    1. All MyARM web application can be used from a stanadrd Web-Browser
    2. MyARM applications
      1. The myarmmanager provides an easy to use graphical user interface to access all MyARM web applications
      2. Command line tools such as myarmquery are able to connect to a database directly (except SQLite3® Databases)
    1. myarmdaemon collects and aggregates ARM data received from other hosts and provides interfaces for the web applications
      1. receives runtime configurations from the myarmadmin web application over a TCP/IP connection, stores this runtime configuration on local filesystem and distributes the data to connected myarmdaemon processes over a TCP/IP connection
      2. aggregates received ARM data into statistics in (nearly) realtime
      3. depending on configuration writes ARM data
        1. into a database
        2. or into the filesystem based MyARM archive
      4. MyARM archive TCP/IP interface for archive queries
    2. MySQL®, MariaDB and SQLite3® database support
    3. Multiple database connections for high transaction loads (Add-on)
    4. MyARM archive SQLite3® database to store ARM metadata (e.g. application- and transaction names)
    5. filesystem based MyARM archive to store ARM measurement data efficiently and a high performance, scalable interface to query the archive using the myarmbrowser web application
    6. CSV export TCP/IP interface to export ARM transaction measurements exactly once (e.g. Apache Spark)
    7. MyARM HTTP servers started by the myarmdaemon
      1. myarmbrowser for individual case analysis
      2. myarmrtsbrowser and myarmrtsmonitor for statistical analysis and 24 hours monitoring
      3. myarmadmin to configure the MyARM system globally
    Enterprise Edition components

    Legend

    Legend