Get Logging Configuration
get
/v1/configuration/logging
Returns the service's current runtime logging level.
Request
Header Parameters
-
X-Request-Id: string
Optional request correlation ID.
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/json
200 Response
Returns the current logging configuration.
Root Schema : LoggingConfigurationResponse
Type:
objectCurrent logging configuration.
Show Source
-
level(required): string
Allowed Values:
[ "SEVERE", "WARNING", "INFO", "FINE" ]Configured logging level.
Examples
500 Response
Unexpected service error.
Root Schema : ErrorResponse
Type:
objectError response returned by the service.
Show Source
-
decodedError:
Returned only when `decode.errors=true` and decodable revert bytes are present.
-
error: string
Short error summary suitable for display.
-
hint: [
"string",
"null"
]
Optional guidance for resolving the error.
-
message: [
"string",
"null"
]
Additional error details, when available.
-
policy:
Present for policy warnings or denials such as preflight failure.
-
preflight:
Present for preflight-gated transaction submission errors.
-
requestId: [
"string",
"null"
]
Client-provided correlation ID echoed in the response.
-
upstreamCode: [
"integer",
"null"
]
Besu node error code, when provided by the RPC endpoint.
-
upstreamData: [
"string",
"null"
]
Error data returned by the Besu node in 0x-prefixed hexadecimal or JSON format, when available.
-
upstreamError: [
"object",
"null"
]
upstreamError
Additional Properties Allowed:
trueComplete error object returned by the Besu node, including code, message, and data fields, when available.
Nested Schema : upstreamError
Type:
objectAdditional Properties Allowed:
trueComplete error object returned by the Besu node, including code, message, and data fields, when available.