title | description | services | documentationcenter | author | manager | editor | ms.assetid | ms.service | ms.devlang | ms.topic | ms.tgt_pltfrm | ms.workload | ms.date | ms.author |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Collect data from CollectD in OMS Log Analytics | Microsoft Docs |
CollectD is an open source Linux daemon that periodically collects data from applications and system level information. This article provides information on collecting data from CollectD in Log Analytics. |
log-analytics |
mgoedtel |
carmonm |
tysonn |
f1d5bde4-6b86-4b8e-b5c1-3ecbaba76198 |
log-analytics |
na |
article |
na |
infrastructure-services |
05/02/2017 |
magoedte |
CollectD is an open source Linux daemon that periodically collects performance metrics from applications and system level information. Example applications include the Java Virtual Machine (JVM), MySQL Server, and Nginx. This article provides information on collecting performance data from CollectD in Log Analytics.
A full list of available plugins can be found at Table of Plugins.
The following CollectD configuration is included in the OMS Agent for Linux to route CollectD data to the OMS Agent for Linux.
LoadPlugin write_http
<Plugin write_http>
<Node "oms">
URL "127.0.0.1:26000/oms.collectd"
Format "JSON"
StoreRates true
</Node>
</Plugin>
Additionally, if using an versions of collectD before 5.5 use the following configuration instead.
LoadPlugin write_http
<Plugin write_http>
<URL "127.0.0.1:26000/oms.collectd">
Format "JSON"
StoreRates true
</URL>
</Plugin>
The CollectD configuration uses the defaultwrite_http
plugin to send performance metric data over port 26000 to OMS Agent for Linux.
Note
This port can be configured to a custom-defined port if needed.
The OMS Agent for Linux also listens on port 26000 for CollectD metrics and then converts them to OMS schema metrics. The following is the OMS Agent for Linux configuration collectd.conf
.
<source>
type http
port 26000
bind 127.0.0.1
</source>
<filter oms.collectd>
type filter_collectd
</filter>
- Log Analytics currently supports CollectD version 4.8 and above.
- OMS Agent for Linux v1.1.0-217 or above is required for CollectD metric collection.
The following are basic steps to configure collection of CollectD data in Log Analytics.
- Configure CollectD to send data to the OMS Agent for Linux using the write_http plugin.
- Configure the OMS Agent for Linux to listen for the CollectD data on the appropriate port.
- Restart CollectD and OMS Agent for Linux.
-
To route CollectD data to the OMS Agent for Linux,
oms.conf
needs to be added to CollectD's configuration directory. The destination of this file depends on the Linux distro of your machine.If your CollectD config directory is located in /etc/collectd.d/:
sudo cp /etc/opt/microsoft/omsagent/sysconf/omsagent.d/oms.conf /etc/collectd.d/oms.conf
If your CollectD config directory is located in /etc/collectd/collectd.conf.d/:
sudo cp /etc/opt/microsoft/omsagent/sysconf/omsagent.d/oms.conf /etc/collectd/collectd.conf.d/oms.conf
[!NOTE] For CollectD versions before 5.5 you will have to modify the tags in
oms.conf
as shown above. -
Copy collectd.conf to the desired workspace's omsagent configuration directory.
sudo cp /etc/opt/microsoft/omsagent/sysconf/omsagent.d/collectd.conf /etc/opt/microsoft/omsagent/<workspace id>/conf/omsagent.d/ sudo chown omsagent:omiusers /etc/opt/microsoft/omsagent/<workspace id>/conf/omsagent.d/collectd.conf
-
Restart CollectD and OMS Agent for Linux with the following commands.
sudo service collectd restart sudo /opt/microsoft/omsagent/bin/service_control restart
To maintain a familiar model between infrastructure metrics already collected by OMS Agent for Linux and the new metrics collected by CollectD the following schema mapping is used:
CollectD Metric field | Log Analytics field |
---|---|
host | Computer |
plugin | None |
plugin_instance | Instance Name If plugin_instance is null then InstanceName="_Total" |
type | ObjectName |
type_instance | CounterName If type_instance is null then CounterName=blank |
dsnames[] | CounterName |
dstypes | None |
values[] | CounterValue |
- Learn about log searches to analyze the data collected from data sources and solutions.
- Use Custom Fields to parse data from syslog records into individual fields.