Configure logging and related middleware
Print
- Last Updated: December 23, 2025
- 1 minute read
- OpenEdge
- Version 12.8
- Documentation
Logging and timing features can be configured using runtime settings within
the mcp_server_config.json configuration file. These options
control log format, payload inclusion, and method filtering.
Logging configuration keys
The configuration keys in the
The following example shows how to enable structured logging and
timing:
runtime.middleware section control how logging
and timing behave in the OpenEdge MCP Server. These settings allow administrators to
enable or disable features, choose log formats, and decide what level of detail is
captured during request processing. The following table describes the configuration
keys for runtime.middleware.logging:| Key | Type | Default value | Recommended value in production | Description |
|---|---|---|---|---|
enabled |
Boolean | true |
_ | Turns request logging on or off. |
structured |
Boolean | false |
true |
When set to true, outputs logs as JSON objects for easier integration with log aggregators. |
include_payloads |
Boolean | false |
false (enable temporarily for
debugging) |
Includes truncated request and response payload excerpts. Avoid enabling in production to prevent sensitive data exposure. |
methods |
List[str] (List of strings) |
Unset | _ | Restricts logging to specific HTTP verbs or internal method tags. If unset, all methods are logged. |
|
Note: Do not enable
include_payloads in production
because payloads may contain sensitive data.