collectd: Linux performance metrics in Application Insights [Deprecated]


The recommended approach to monitor Java applications is to use the auto-instrumentation without changing the code. Please follow the guidelines for Application Insights Java 3.0 agent.

To explore Linux system performance metrics in Application Insights, install collectd, together with its Application Insights plug-in. This open-source solution gathers various system and network statistics.

Typically you'll use collectd if you have already instrumented your Java web service with Application Insights. It gives you more data to help you to enhance your app's performance or diagnose problems.

Get your instrumentation key

In the Microsoft Azure portal, open the Application Insights resource where you want the data to appear. (Or create a new resource.)

Take a copy of the instrumentation key, which identifies the resource.

Browse all, open your resource, and then in the Essentials drop-down, select, and copy the Instrumentation Key

Install collectd and the plug-in

On your Linux server machines:

  1. Install collectd version 5.4.0 or later.
  2. Download the Application Insights collectd writer plugin. Note the version number.
  3. Copy the plugin JAR into /usr/share/collectd/java.
  4. Edit /etc/collectd/collectd.conf:
    • Ensure that the Java plugin is enabled.
    • Update the JVMArg for the java.class.path to include the following JAR. Update the version number to match the one you downloaded:
    • /usr/share/collectd/java/applicationinsights-collectd-1.0.5.jar
    • Add this snippet, using the Instrumentation Key from your resource:

     LoadPlugin ""
     <Plugin ApplicationInsightsWriter>
        InstrumentationKey "Your key"

Here's part of a sample configuration file:

    # collectd plugins
    LoadPlugin cpu
    LoadPlugin disk
    LoadPlugin load

    # Enable Java Plugin
    LoadPlugin "java"

    # Configure Java Plugin
    <Plugin "java">
      JVMArg "-verbose:jni"
      JVMArg "-Djava.class.path=/usr/share/collectd/java/applicationinsights-collectd-1.0.5.jar:/usr/share/collectd/java/collectd-api.jar"

      # Enabling Application Insights plugin
      LoadPlugin ""

      # Configuring Application Insights plugin
      <Plugin ApplicationInsightsWriter>
        InstrumentationKey "12345678-1234-1234-1234-123456781234"

      # Other plugin configurations ...

Configure other collectd plugins, which can collect various data from different sources.

Restart collectd according to its manual.

View the data in Application Insights

In your Application Insights resource, open Metrics and add charts, selecting the metrics you want to see from the Custom category.

By default, the metrics are aggregated across all host machines from which the metrics were collected. To view the metrics per host, in the Chart details blade, turn on Grouping and then choose to group by CollectD-Host.

To exclude upload of specific statistics

By default, the Application Insights plugin sends all the data collected by all the enabled collectd 'read' plugins.

To exclude data from specific plugins or data sources:

  • Edit the configuration file.
  • In <Plugin ApplicationInsightsWriter>, add directive lines like this:
Directive Effect
Exclude disk Exclude all data collected by the disk plugin
Exclude disk:read,write Exclude the sources named read and write from the disk plugin.

Separate directives with a newline.


I don't see data in the portal

  • Open Search to see if the raw events have arrived. Sometimes they take longer to appear in metrics explorer.
  • You might need to set firewall exceptions for outgoing data
  • Enable tracing in the Application Insights plugin. Add this line within <Plugin ApplicationInsightsWriter>:
    • SDKLogger true
  • Open a terminal and start collectd in verbose mode, to see any issues it is reporting:
    • sudo collectd -f

Known issue

The Application Insights Write plugin is incompatible with certain Read plugins. Some plugins sometimes send "NaN" where the Application Insights plugin expects a floating-point number.

Symptom: The collectd log shows errors that include "AI: ... SyntaxError: Unexpected token N".

Workaround: Exclude data collected by the problem Write plugins.