Azure Application Insights by 2G

Content Type: Module
Categories: Tracing

Overview

This module was created to integrate the logging from the Mendix applciation into Azure Application Insights. The purpose of this module is two-fold: - Send default Mendix logging to Application Insights - Send custom metrics information to Application Insights The reason for this is that if you are already using Application Insights to monitor your other Azure components (like Functions or Logic apps) you can now use a single location for your system / functional administrators for their logging information. You can use custom attributes to provide correlation information to the Application Insights. Usage The Java action InitializeApplicationInsights needs to be called when the Mendix application starts. So add a call to this Java action in your AfterStartup flow. You need to provide an instrumentation key which is the unique identifier for your App Insights instance. Make a constant for this. You need this key later on to send custom traces. By default only informational messages and up are logged. If you want you can also send the traces to AppInsights. Be aware that this will also include the Jetty logs! After the initialization is done you can use one of the other Java actions to send custom information to AppInsights: - Traces - Dependency calls - Metrics - Request information

Documentation

mendix-applicationinsights

This module was created to integrate the logging from the Mendix applciation into Azure Application Insights. The purpose of this module is two-fold:

  • Send default Mendix logging to Application Insights
  • Send custom metrics information to Application Insights

The reason for this is that if you are already using Application Insights to monitor your other Azure components (like Functions or Logic apps) you can now use a single location for your system / functional administrators for their logging information.

You can use custom attributes to provide correlation information to the Application Insights.

Usage

The Java action InitializeApplicationInsights needs to be called when the Mendix application starts. So add a call to this Java action in your AfterStartup flow. You need to provide an instrumentation key which is the unique identifier for your App Insights instance. Make a constant for this. You need this key later on to send custom traces.

By default only informational messages and up are logged. If you want you can also send the traces to AppInsights. Be aware that this will also include the Jetty logs!

After the initialization is done you can use one of the other Java actions to send custom information to AppInsights:

  • Traces
  • Dependency calls
  • Metrics
  • Request information

Releases

Version: 1.5.1
Framework Version: 9.0.5
Release Notes: Updated dependecy jars **Full Changelog**: https://github.com/2gplus/mendix-applicationinsights/compare/1.1.0...1.5.1
Version: 1.5.0
Framework Version: 9.0.5
Release Notes: - Fixed the models to have proper max sizes accoring to AppInsights schema - Added microflows to do the telemetry logging with adding default Mendix context information
Version: 1.4.4
Framework Version: 9.0.5
Release Notes: Updated AppInsights SDK
Version: 1.3.0
Framework Version: 9.0.5
Release Notes: Bumped modeler to Mx9