Skip to main content

Inbox listener configuration

Configure the inbox listener​

The inbox listener processes recordings from the inbox bucket to the lake bucket for indexing, storage, and access.

It uses a combination of compute, memory, and disk resources and can be scaled horizontally (see Autoscaling). In many cases, the default configuration is appropriate and does not need to be changed.

If your primary site is expected to process unindexed MCAP or ROS 1 BAG files, consider configuring your inbox listener deployment with local scratch storage. We recommend allocating at least three times as much capacity as your largest expected input file size. If unconfigured or if processing an input might exceed its capacity, the inbox listener will use the lake bucket as scratch storage instead, which is usually slower.

Scratch storage can be configured in your helm values file:

inboxListener:
  deployment:
    localScratch:
      enabled: true
      capacity: "107374182400" # a string specifying a whole number of bytes.