Service Configuration
Each EdgeX micro service requires configuration (i.e. - a repository of initialization and operating values). The configuration is initially provided by a TOML file but a service can utilize the centralized configuration management provided by EdgeX for its configuration.
See the Configuration and Registry documentation for more details about initialization of services and the use of the configuration service.
Please refer to the EdgeX Foundry architectural decision record for details (and design decisions) behind the configuration in EdgeX.
Please refer to the general Common Configuration documentation for configuration properties common to all services. Find service specific configuration references in the tabs below.
EdgeX 2.0
For EdgeX 2.0 the Service configuration section has been standardized across all EdgeX services.
| Service Name | Configuration Reference |
|---|---|
| core-data | Core Data Configuration |
| core-metadata | Core Metadata Configuration |
| core-command | Core Command Configuration |
| Service Name | Configuration Reference |
|---|---|
| support-notifications | Support Notifications Configuration |
| support-scheduler | Support Scheduler Configuration |
| Services Name | Configuration Reference |
|---|---|
| app-service | General Application Service Configuration |
| app-service-configurable | Configurable Application Service Configuration |
| eKuiper rules engine/eKuiper | Basic eKuiper Configuration |
| Services Name | Configuration Reference |
|---|---|
| device-service | General Device Service Configuration |
| device-virtual | Virtual Device Service Configuration |
| Services Name | Configuration Reference |
|---|---|
| API Gateway | Kong Configuration |
| Add-on Services | Configuring Add-on Service |
| Services Name | Configuration Reference |
|---|---|
| system management | System Management Agent Configuration |