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
  • Professional
  • Enterprise
  • Web
  • Download
    DocumentsHTML, PDFHTML, PDFHTML, PDFHTML, PDFHTML, PDFHTML, PDFHTML, PDFHTML, PDF
    Base pricefree1200 €1200 €1200 €1500 €1800 €2100 €6000 €
    Purchase-PurchasePurchasePurchasePurchasePurchasePurchase-
    Operating SystemWindows, LinuxWindows, Linux, Solaris, AIXWindows, Linux, Solaris, AIXWindows, LinuxWindows, Linux, Solaris, AIXWindows, LinuxWindows, Linux, Solaris, AIXLinux, Solaris (x86)
    ARM 4.0 Language Bindings
    ARM 4.0 C+++++
    ARM 4.0 Java+++++
    ARM 4.0 C#++++
    ARM 4.0 Python++++
    ARM 2.0 C++
    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)+++++++
    HTTPd Browser (WUI)+2 (*)(*) The browser web application within the Community Edition is provided by a stand-alone HTTPD-Server which supports 2 concurrent users at a time.+2 (*)(*) The browser web application within the C/C++ Edition is provided by a stand-alone HTTPD-Server which supports 2 concurrent users at a time.+2 (*)(*) The browser web application within the Java Edition is provided by a stand-alone HTTPD-Server which supports 2 concurrent users at a time.+2 (*)(*) The browser web application within the C# Edition is provided by a stand-alone HTTPD-Server which supports 2 concurrent users at a time.+2 (*)(*) The browser web application within the Standard Edition is provided by a stand-alone HTTPD-Server which supports 2 concurrent users at a time.+2 (*)(*) The browser web application within the Professional Edition is provided by a stand-alone HTTPD-Server which supports 2 concurrent users at a time.+2 (*)(*) The browser web application within the Enterprise Edition is provided by a stand-alone HTTPD-Server which supports 2 concurrent users at a time.+50 (*)(*) The browser web application within the Web Edition is provided by a stand-alone HTTPD-Server which supports 50 concurrent users at a time.
    FastCGI Browser+ (*)(*) The browser web application within the Web Edition can be used with the FastCGI interface which should be deployed within an Apache HTTPD Server using mod_fastcgi or mod_fcgi. The number of concurrent users is unlimited (e.g. only limited by the server resources).
    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
    +++++++
    Oracle® (*)
    (*) The following versions of Oracle® are supported:
    • Oracle 10g
    • Oracle 11g should work but function cannot be guaranteed
    ++
    Deployment features
    myarmdaemon (*)
    (*) myarmdaemon is used in conjunction with the TCP and/or file datasink according to its processing mode.

    The TCP datasink connects to another myarmdaemon using a TCP/IP socket and forwards measured ARM data to the that daemon.

    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

    tcpfile, tcpfile, tcpfile, tcpfile, tcpfile, tcpfile, 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++++++
    RTS: Real time statistics (*)(*) Real time statistics (RTS) Add-on calculates and records the statistics.

    The Add-on is only available in conjunction with the Web-Edition since the myarmadmin, myarmrtsbrowser and myarmrtsmonitor web applications are used to configure and present the statistics.
    +++++++(*)(*) used to create and manage real time statistics using the myarmadmin web application and to present the statistics using the myarmrtsmonitor and myarmrtsbrowser web applications
    RTC: Runtime configuration (*)(*) Runtime configuration (RTC) is used to adopt the behaviour of a running ARM instrumented application. Transaction measurements can be disabled or thresholds can be defined to drop (not written to database) the measurement.

    Runtime configuration is only available in conjunction with the Web-Edtion since the myarmadmin web application is used to create and manage the runtime configuration.
    +++++++(*)(*) used to create and manage runtime configurations using the myarmadmin web application
    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.

    This Add-on is only available in conjunction with the Web-Edition since the myarmadmin web application is used to create and manage the conditions and notification scripts.
    +++++++(*)(*) used to create and manage runtime notification conditions and scripts using the myarmadmin web application
    (*) Move mouse over cell for a brief description
    Community Edition componentsMove mouse over figure for a legendLegend

    The diagram on the right shows which components can be used in the Community edition:

    1. C/C++, Java, C# and Python programming language bindings
    2. ARM agent implementation supporting the datasinks and handlers:
      1. TCP/IP datasink sending all measured ARM data to the myarmdaemon
      2. event flow auto response and apache handler
    3. myarmdaemon collecting ARM data from other hosts and writing the ARM data to a database
    4. SQLite3® database support
    5. Stand-alone graphical user interface and web-based user interface for analysing measured ARM data
    C++ Edition componentsMove mouse over figure for a legendLegend

    The diagram on the right shows which components can be used in the C/C++ edition:

    1. C/C++ programming language bindings
    2. ARM agent implementation with following components:
      1. File, TCP/IP and database datasink
      2. Runtime configuration component which manages current runtime configuration (Add-on)
      3. Different handler which uses the runtime configuration to adopt the behaviour of the transaction measurement (disable or drop specific transactions)
      4. Filestorage component to write ARM data to a temporary file if the datasink is not available; this component will read in and forward the data to the datasink if it becomes available
    3. myarmdaemon
      1. to read ARM data from files written by the File datasink and
      2. forwarding it to a myarmdaemon using the TCP/IP datasink
      3. runtime configurations received via a TCP/IP connection from a MyARM web application and stores it on local hard drive
    4. myarmdaemon collecting and aggregating ARM data
      1. storing the ARM data to a database
      2. runtime configurations received via a TCP/IP connection from another myarmdaemon and stores it on local hard drive
      3. aggregate received ARM data into real time statistics (Add-on)
    5. Multiple database connections for high transaction loads (Add-on)
    6. MySQL®, MariaDB and SQLite3® database support
    7. Web-based user interface, stand-alone graphical user interface and command line tools for analysing measured ARM data
      1. using an generic database datasource API
      2. writing and reading XML or MyARM data files
      3. sending runtime configurations to myarmdaemon processes
    Java Edition componentsMove mouse over figure for a legendLegend

    The diagram on the right shows which components can be used in the Java edition:

    1. Java programming language bindings
    2. ARM agent implementation with following components:
      1. File, TCP/IP and database datasink
      2. Runtime configuration component which manages current runtime configuration (Add-on)
      3. Different handler which uses the runtime configuration to adopt the behaviour of the transaction measurement (disable or drop specific transactions)
      4. Filestorage component to write ARM data to a temporary file if the datasink is not available; this component will read in and forward the data to the datasink if it becomes available
    3. myarmdaemon
      1. to read ARM data from files written by the File datasink and
      2. forwarding it to a myarmdaemon using the TCP/IP datasink
      3. runtime configurations received via a TCP/IP connection from a MyARM web application and stores it on local hard drive
    4. myarmdaemon collecting and aggregating ARM data
      1. storing the ARM data to a database
      2. runtime configurations received via a TCP/IP connection from another myarmdaemon and stores it on local hard drive
      3. aggregate received ARM data into real time statistics (Add-on)
    5. Multiple database connections for high transaction loads (Add-on)
    6. MySQL®, MariaDB and SQLite3® database support
    7. Web-based user interface, stand-alone graphical user interface and command line tools for analysing measured ARM data
      1. using an generic database datasource API
      2. writing and reading XML or MyARM data files
      3. sending runtime configurations to myarmdaemon processes
    C# Edition componentsMove mouse over figure for a legendLegend

    The diagram on the right shows which components can be used in the C# edition:

    1. C# programming language bindings
    2. ARM agent implementation with following components:
      1. File, TCP/IP and database datasink
      2. Runtime configuration component which manages current runtime configuration (Add-on)
      3. Different handler which uses the runtime configuration to adopt the behaviour of the transaction measurement (disable or drop specific transactions)
      4. Filestorage component to write ARM data to a temporary file if the datasink is not available; this component will read in and forward the data to the datasink if it becomes available
    3. myarmdaemon
      1. to read ARM data from files written by the File datasink and
      2. forwarding it to a myarmdaemon using the TCP/IP datasink
      3. runtime configurations received via a TCP/IP connection from a MyARM web application and stores it on local hard drive
    4. myarmdaemon collecting and aggregating ARM data
      1. storing the ARM data to a database
      2. runtime configurations received via a TCP/IP connection from another myarmdaemon and stores it on local hard drive
      3. aggregate received ARM data into real time statistics (Add-on)
    5. Multiple database connections for high transaction loads (Add-on)
    6. MySQL®, MariaDB and SQLite3® database support
    7. Web-based user interface, stand-alone graphical user interface and command line tools for analysing measured ARM data
      1. using an generic database datasource API
      2. writing and reading XML or MyARM data files
      3. sending runtime configurations to myarmdaemon processes
    Standard Edition componentsMove mouse over figure for a legendLegend

    The diagram on the right shows which components can be used in the Standard edition:

    1. C/C++ and Java programming language bindings
    2. ARM agent implementation with following components:
      1. File, TCP/IP and database datasink
      2. Runtime configuration component which manages current runtime configuration (Add-on)
      3. Different handler which uses the runtime configuration to adopt the behaviour of the transaction measurement (disable or drop specific transactions)
      4. Filestorage component to write ARM data to a temporary file if the datasink is not available; this component will read in and forward the data to the datasink if it becomes available
    3. myarmdaemon
      1. to read ARM data from files written by the File datasink and
      2. forwarding it to a myarmdaemon using the TCP/IP datasink
      3. runtime configurations received via a TCP/IP connection from a MyARM web application and stores it on local hard drive
    4. myarmdaemon collecting and aggregating ARM data
      1. storing the ARM data to a database
      2. runtime configurations received via a TCP/IP connection from another myarmdaemon and stores it on local hard drive
      3. aggregate received ARM data into real time statistics (Add-on)
    5. Multiple database connections for high transaction loads (Add-on)
    6. MySQL®, MariaDB and SQLite3® database support
    7. Web-based user interface, stand-alone graphical user interface and command line tools for analysing measured ARM data
      1. using an generic database datasource API
      2. writing and reading XML or MyARM data files
      3. sending runtime configurations to myarmdaemon processes
    Professional Edition componentsMove mouse over figure for a legendLegend

    The diagram on the right shows which components can be used in the Professional edition:

    1. C/C++, Java, C# and Python programming language bindings
    2. ARM agent implementation with following components:
      1. File, TCP/IP and database datasink
      2. Runtime configuration component which manages current runtime configuration (Add-on)
      3. Different handler which uses the runtime configuration to adopt the behaviour of the transaction measurement (disable or drop specific transactions)
      4. Filestorage component to write ARM data to a temporary file if the datasink is not available; this component will read in and forward the data to the datasink if it becomes available
    3. myarmdaemon
      1. to read ARM data from files written by the File datasink and
      2. forwarding it to a myarmdaemon using the TCP/IP datasink
      3. runtime configurations received via a TCP/IP connection from a MyARM web application and stores it on local hard drive
    4. myarmdaemon collecting and aggregating ARM data
      1. storing the ARM data to a database
      2. runtime configurations received via a TCP/IP connection from another myarmdaemon and stores it on local hard drive
      3. aggregate received ARM data into real time statistics (Add-on)
    5. Multiple database connections for high transaction loads (Add-on)
    6. MySQL®, MariaDB and SQLite3® database support
    7. Web-based user interface, stand-alone graphical user interface and command line tools for analysing measured ARM data
      1. using an generic database datasource API
      2. writing and reading XML or MyARM data files
      3. sending runtime configurations to myarmdaemon processes
    Enterprise Edition componentsMove mouse over figure for a legendLegend

    The diagram on the right shows which components can be used in the Enterprise edition:

    1. C/C++, Java, C# and Python programming language bindings
    2. ARM agent implementation with following components:
      1. File, TCP/IP and database datasink
      2. Runtime configuration component which manages current runtime configuration (Add-on)
      3. Different handler which uses the runtime configuration to adopt the behaviour of the transaction measurement (disable or drop specific transactions)
      4. Filestorage component to write ARM data to a temporary file if the datasink is not available; this component will read in and forward the data to the datasink if it becomes available
    3. myarmdaemon
      1. to read ARM data from files written by the File datasink and
      2. forwarding it to a myarmdaemon using the TCP/IP datasink
      3. runtime configurations received via a TCP/IP connection from a MyARM web application and stores it on local hard drive
    4. myarmdaemon collecting and aggregating ARM data
      1. storing the ARM data to a database
      2. runtime configurations received via a TCP/IP connection from another myarmdaemon and stores it on local hard drive
      3. aggregate received ARM data into real time statistics (Add-on)
    5. Multiple database connections for high transaction loads (Add-on)
    6. MySQL®, MariaDB, Oracle® and SQLite3® database support
    7. Web-based user interface, stand-alone graphical user interface and command line tools for analysing measured ARM data
      1. using an generic database datasource API
      2. writing and reading XML or MyARM data files
      3. sending runtime configurations to myarmdaemon processes
    Web Edition componentsMove mouse over figure for a legendLegend

    The diagram on the right shows which components can be used in the Web edition:

    1. Web
      Stand-alone HTTP-server and FastCGI-based web server integration of the user interface for browsing through stored data and clearly represented charts.
      Tools
      Command line tools for batch processing of measurement data in the database
    2. Providing runtime configuration data to other editions myarmdaemon processes
    3. MySQL®, MariaDB, Oracle® and SQLite3® database support