DataElicit Logo

Docs

Installation Manual

Step-by-step guide to install, configure, and manage LogConnector.

Installation Manual

Installation Steps

Login into DataElicit's portal. Sign Up if not registered.

Download the LogConnector tgz file from LogConnector homepage > Download.

Extract the LogConnector.tgz file:

tar -xzf LogConnector.tgz

Get your license from the License tab in DataElicit's portal.

Create license.json inside LogConnector/license/ and add your license:

cd LogConnector/license/
nano license.json

Configuration Steps

Create server.conf inside LogConnector/system/local/.

cd LogConnector/system/local
nano server.conf

Configure server.conf as per your organization settings and use the ingest token under the [general] stanza. For example:

[general]
logscaleurl = https://cloud.community.humio.com
token       = XxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXxXx
defaultrepo = main

Note

Use Ingest API HEC URL for logscaleurl. Organization ingest token is recommended so you can manage ingestion across all repositories in the organization. A single repo token will limit ingestion to that repo only.

Basic Commands

In the LogConnector directory, start and manage the LogConnector service with the commands below. Use sudo the first time so the service can create a user and password.

sudo ./bin/logconnector service start

To restart the service after changing configuration files or connectors:

sudo ./bin/logconnector service restart

You can view LogConnector logs in LogConnector/var/log/logconnector/ directory in the logconnector.log file.

To stop the LogConnector service:

sudo ./bin/logconnector service stop

To disable the LogConnector service so it does not auto start on boot:

sudo ./bin/logconnector service disable

Note

Refer connector specific installation and configuration docs for each connector you plan to deploy. The commands above handle the core LogConnector service only.

Troubleshooting Steps

LogConnector logs are stored in LogConnector/var/log/logconnector/logconnector.log. Review this file first when you run into issues.

If you are using a Linux distribution with SELinux or AppArmor enabled, install LogConnector in /opt or adjust the security policy accordingly.

Note

On RedHat based systems, SELinux is often enabled by default. LogConnector may fail to start if installed outside /opt or if the policy is not updated. Disable SELinux or create the required rules if you want LogConnector in another directory.
Still stuck? How can we help?

Updated on July 6, 2025