---
updatedAt: 2025-11-05T20:10:57.000Z
agentTools:
  projectIndex: https://esf.eurotech.com/v5.0.0/llms.txt
---

# Directory Layout

This section describes the default ESF directory layout that is created upon installation. The default installation directory is as follows:

```shell
/opt/eurotech/
```

The **esf** sub-directory is a logical link on the actual ESF release directory:

```text
esf -> /opt/eurotech/esf_3.0.2_reliagate-10-20_yocto_1.2.1`
esf_3.0.2_reliagate-10-20_yocto_1.2.1`
```

# ESF File Structure

All of the ESF files are located within this parent directory using the structure shown in the following table:

<Table align={["left","left"]}>
  <thead>
    <tr>
      <th>
        Directory
      </th>

      <th>
        Description
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        bin
      </td>

      <td>
        Scripts that start ESF
      </td>
    </tr>

    <tr>
      <td>
        console
      </td>

      <td>
        Web console CSS file
      </td>
    </tr>

    <tr>
      <td>
        data
      </td>

      <td>
        Data of the ESF application
      </td>
    </tr>

    <tr>
      <td>
        data/db
      </td>

      <td>
        HSQL embedded database
      </td>
    </tr>

    <tr>
      <td>
        data/paho-persistence
      </td>

      <td>
        Message storage for paho (MQTT client) persistence
      </td>
    </tr>

    <tr>
      <td>
        data/snapshots
      </td>

      <td>
        XML snapshot files; up to 10 successive configurations including the original (see [Snapshot Management](https://esf.eurotech.com/v5.0.0/docs/snapshot-management))
      </td>
    </tr>

    <tr>
      <td>
        kura
      </td>

      <td>
        Configuration files for the ESF framework and logging
      </td>
    </tr>

    <tr>
      <td>
        kura/plugins
      </td>

      <td>
        All of the ESF specific jar files
      </td>
    </tr>

    <tr>
      <td>
        kura/packages
      </td>

      <td>
        Deployment package files that are not part of the standard ESF framework, but are installed at a later time (see [Application Management](https://esf.eurotech.com/v5.0.0/docs/application-management) )
      </td>
    </tr>

    <tr>
      <td>
        lib/ext
      </td>

      <td>
        Repository for the native libraries config files
      </td>
    </tr>

    <tr>
      <td>
        log
      </td>

      <td>
        Log file from the latest ESF installation
      </td>
    </tr>

    <tr>
      <td>
        plugins
      </td>

      <td>
        All of the libraries needed for ESF execution as jar files
      </td>
    </tr>
  </tbody>
</Table>

# Log Files

ESF regularly updates two log files in the **/var/log** directory:

* **/var/log/kura-console.log** - stores the standard console output of the application. This log file contains the eventual errors that are thrown upon ESF startup.

* **/var/log/kura.log** - stores all of the logging information from ESF bundles. The logger levels are defined in the **log4j.properties** configuration file as shown below:

```shell
/opt/eurotech/esf/kura/log4j.properties
```

The default logger level in this file is set to INFO. This level may be modified for the whole application or for a specific bundle as shown in the following example:

```text
log4j.logger.org.eclipse.kura=INFO
log4j.logger.org.eclipse.kura.net.admin=DEBUG
```

In this example, the logger level is set to DEBUG only for the **net.admin** bundle. Additional, more specific, properties may be defined as required for your particular logging needs. The logger levels are hierarchical, so that those in a deeper level of the hierarchy will apply; otherwise, the more general logger level will override them.

Once the logger levels are modified as needed and the **log4j.properties** configuration file is saved, ESF must be restarted in order for the changes to take affect.