Admin: RPI Realtime decisions - Logging

Realtime API logging in RPI is split into independent channels that can be configured separately in the Helm chart. This allows you to see detailed connector and endpoint logs while keeping core framework logging quiet, solving the common problem of log noise in production environments with custom connectors.

Turning on logging, especially verbose logging, will impact the performance of the Realtime API. Anything higher than Error level logging should only be left on when debugging an issue.

Each of the settings below support the following logging levels, from least to most noisy:

Critical
Error
Warning
Information
Trace
Debug

realtimeapi:
  logging:
    realtimeapi:
      default: Error
      endpoint: Information
      shared: Error
      plugins: Information
      other: Error
      console: "true"
    realtimeagent:
      default: Error
      database: Error
      rpiTrace: Error
      rpiError: Error
      console: "false"

realtimeapi:

default: the core Redpoint framework, which is quiet in production. The default is Error.
endpoint: the HTTP request/response details. The default is Error.
shared: the shared libraries. The default is Error.
plugins: the custom plugin execution. The default is Error.
other: this covers everything else. The default is Error.
console: the option to turn standard output logging on or off. Standard output logging streams the container logs within the container output; if turned off nothing shows up when a user tries to query the container. The default is “true” (on).

realtimeagent:

default: the background worker service. Default is Error.
database: the database operations. Default is Error.
rpiTrace: the RPI trace events. Default is Error.
rpiError: the RPI error events. Default is Error.
console: the option to turn standard output logging on or off. Standard output logging streams the container logs within the container output; if turned off nothing shows up when a user tries to query the container. The default is “false” (off).