Document updated on Oct 20, 2022

Service Settings

We call service settings (or the service layer) those parameters that allow you to change how KrakenD behaves globally (and not to a specific call). They determine how you start the HTTP server, enforce security parameters, or define behavioral options like which reporting activities occur, to name a few examples.

Examples of service settings are, the listening port, disabling keep alives, enabling metrics and traces, listening https, or enabling CORS to name a few.

If you haven’t done it yet, read Understanding the configuration file.

All service settings are written directly in the root of the configuration file or its corresponding extra_config. So, for instance, here there is a configuration file describing a service listening on port 8080 with extended logging enabled:

{
    "version": 3,
    "port": 8080,
    "endpoints": [],
    "extra_config": {
      "telemetry/logging": {
        "level": "WARNING",
        "syslog": true,
        "stdout": true
      }
    }
}

The service accepts numerous configuration options that you’ll find explained through the rest of the documentation, but here is a preview of the most important ones:

Other service-level settings you can add:

• HTTP server settings
• HTTP transport settings
• Router settings
• SSL/TLS