# Edge Configuration

## Overview

The Senseforce Edge solution is a headless piece of software, running either as Console Application, Windows Service, or as Linux Daemon. To define, which data to collect, which Edge operations to perform, and where to send the data to, an XML file-based configuration workflow is implemented. 

{% hint style="info" %}
You can define a set of default Edge configurations which you can easily check into your configuration management systems as well as copy\&paste to your newly installed Edge instances.
{% endhint %}

## Edge configuration workflow

Any Edge software instance is delivered with a default set of configurations.

Depending on whether you use the Edge console application or the Edge service application, the configuration can be found in the following folders.

{% tabs %}
{% tab title="Console Application" %}

```
[Edge Main Folder]/configs
```

{% hint style="danger" %}
These configs are only used for the Edge instance Luna.Console, executed directly from the \[Edge Main Folder].
{% endhint %}
{% endtab %}

{% tab title="Service Application" %}

```
C:/ProgramData/Senseforce/Luna Data/[YourServiceName]
```

{% hint style="info" %}
You can install several Luna service instances onto one device - for example to collect data of several machines from a local data collection device. Each service instance needs it's own set of configurations. When using the Senseforce Edge Service Installer, the default configurations are automatically installed for any service.
{% endhint %}
{% endtab %}
{% endtabs %}

There are four areas where the Edge solution needs to be configured: 

{% tabs %}
{% tab title="Which Plugins to load" %}
Define **which Plugins to load** and where to find the plugins binaries

#### File-path:

```
configs/appsettings.xml
```

{% endtab %}

{% tab title="Input Plugin(s)" %}
Configure the **input plugin**(s): Which data to collect, sampling frequency, advanced operations like filtering

#### File-path:

```
configs/configurations/InputPlugins/[Plugin]
```

{% hint style="info" %}
Note: Depending on which input plugin is used, several configuration files need to be adjusted for each plugin
{% endhint %}
{% endtab %}

{% tab title="Output Plugin(s)" %}
Configure the **output plugin**(s): Define where to send your data

#### File-path:

```
configs/configurations/OutputPlugins/[Plugin]/[PluginSettings.xml]
```

{% endtab %}

{% tab title="Data Routing" %}
**Data routing** and **data translation**: Senseforce Edge provides a powerful data routing and data translation layer where you can define which data points are transmitted to which output plugin as well as how the data points are designated.

#### File-path:

```
configs/configurations/EventDefinition.xlm
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://manual.senseforce.io/manual/senseforce-edge/edge-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.