Pinot supports inspecting and modifying Log4J log levels dynamically in production environments through REST. This can often be helpful when debugging an issue that is transient in nature and restarting the server with new configurations files could alter the behavior.
Header
accept string
Setting to "accept: application/json" is recommended
Sample Usage:
Header
accept string
Setting to "accept: application/json" is recommended
Path Parameter
loggerName string
The name of the logger (fully qualified path)
Sample Usage:
Header
accept string
Setting to "accept: application/json" is recommended
Path Parameter
loggerName string
The name of the logger (fully qualified path)
Query Parameter
level string
the log level (such as DEBUG or INFO
Sample Usage
Pinot supports downloading logs directly over HTTP in situations where the operator may not have access to the container, but has access to the rest endpoints.
If the operator has access to the Controller, they can download log files from any one of the other components.
Header
accept string
Setting to "accept: application/json" is recommended
Header
accept string
Setting to "accept: application/octet_string" is recommended
Query Parameter
filePath string
The path to the file, can be obtained using GET /loggers/files
These APIs are only supported on the Controller
Header
accept string
Setting to "accept": application/json" is recommended
Header
accept string
Setting to "accept": application/json" is recommended
Path Parameter
instanceName string
Indicates which instance to collect logs from
Header
accept string
Setting to "accept: application/octet
Path Parameter
instanceName string
Indicates which instance to collect logs from
Query Parameter
filePath string
Indicates which file to download