---
layout: docs
title: LMD - Livestatus Multitool Daemon
---

== LMD
{% include new_since.ad version="2.12" %}
link:https://github.com/sni/lmd[LMD] is a transparent livestatus proxy which fetches live data from several remote sites/backends and provides an aggregated livestatus API which can be used by Thruk. When enabled, LMD handles all the backend connection handling and livestatus aggregation.

Using LMD has multiple advantages:

    - It makes Thruk faster when connecting to many remote locations
    - It makes Thruk more stable when having unstable connections
    - LMD fixes some issues in backend specific livestatus implementations, ex.: Icinga 2


[TIP]
.icinga2
=======
It is recommended for Icinga 2 users to use LMD. However, Icinga2 is about to drop Livestatus support, so if possible use Naemon.
=======



There are some slides available (in german)

+++++++++
<iframe src="//www.slideshare.net/slideshow/embed_code/key/4Jc7ybErOqb510" width="595" height="485" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;" allowfullscreen> </iframe> <div style="margin-bottom:5px"> <strong> <a href="//www.slideshare.net/SvenNierlein/lmd-livestatus-multitool-daemon" title="LMD - Livestatus Multitool Daemon" target="_blank">LMD - Livestatus Multitool Daemon</a> </strong> from <strong><a target="_blank" href="//www.slideshare.net/SvenNierlein">Sven Nierlein</a></strong> </div>
+++++++++


== Installation

LMD is written in golang, so we just need a single compiled binary to operate.
It is included in OMD already or has to be build from source otherwise.

=== Using OMD-Labs

Having OMD-Labs in place is the easiest way to enable LMD. OMD includes LMD
since version 2.20. The setup just takes these 3 steps like documented here:

link:https://labs.consol.de/omd/packages/lmd/[OMD-Labs]

=== Using the Source

link:https://github.com/sni/lmd?tab=readme-ov-file#installation[Simply follow the LMD build instructions.]

== Setup

It is best practice to create a `lmd.conf` file in your
`/etc/thruk/thruk_local.d` folder with the following config settings.

    use_lmd_core=1
    lmd_core_bin=/opt/local/go/bin/lmd

Since LMD is totally transparent, there is no need to configure LMD, the
lmd.ini file will be automatically generated and updated from Thruks backend
configuration.

Finally all you need to do is to restart apache and open Thruk in your browser.
After the first request you should be able to see a lmd process running.

=== Icinga2 Cluster Setup

With LMD you can easily connect Thruk to your Icinga2 HA Cluster. Just add both Icinga2 cluster nodes as 'peer' attributes in your <Component Thruk::Backend>.

    <Component Thruk::Backend>
        <peer>
            name    = Icinga2 HA Cluster
            type    = livestatus
            <options>
                peer   = 172.16.0.1:6558
                peer   = 172.16.0.2:6558
            </options>
        </peer>
    </Component>
