- 2 minutes to read

MessageProcessingMaxBodySize - System Parameter

The MessageProcessingMaxBodySize System Parameter sets the largest message body, in MB, that the Logging Service processes. A message above the limit is not processed, so one very large message can't exhaust the memory of the Logging Service.

At a Glance

Property Value
Key MessageProcessingMaxBodySize
Data type integer (MB)
Default 250
Read by Logging Service
Takes effect Within about 5 minutes; no restart needed
Status ✅ Active
Since Nodinite 5.0.0.29

How It Works

When the Logging Service processes a Log Event whose message body is larger than MessageProcessingMaxBodySize, it skips the processing of that message (for example, no Search Field values are extracted) and instead:

  1. Sets the processing state of the Log Event to Error.
  2. Adds a Comment to the Log Event that explains why.
  3. Writes an entry to the Log Audit, which you can find with Log Audit Search.

All other messages keep being processed. Message processing in general is described in the Logging Service Performance section.

Processing State in a Log View

In a Log View, the message that exceeded the limit shows the Error processing state.

Log View with a Log Event in the Error processing state after exceeding MessageProcessingMaxBodySize
The topmost Log Event exceeded the MessageProcessingMaxBodySize limit and got the Error processing state.

Comment on the Log Event

The Logging Service adds a Comment to the Log Event, visible in the Log View.

Comment added by the Logging Service when a message exceeds MessageProcessingMaxBodySize
The Comment tells users why the message was not processed.

Log Audit Entry

The Logging Service also writes a Log Audit entry for traceability.

Log Audit entry written when a message exceeds MessageProcessingMaxBodySize
Search for these entries with Log Audit Search to find every message that was skipped because of its size.

Choosing a Value

  • ✅ Keep the default 250 MB unless you need Search Field values from even larger messages.
  • Before you raise the limit, make sure the Logging Service server has enough RAM: MessageProcessingBatchSize × the largest message body is roughly what the Logging Service may hold in memory at once. Test higher values before you use them in production.
  • Lowering the limit gives more protection, but messages above it are no longer searchable by their Search Fields.

Next Steps