Creates a new message.
The ID of the campaign to create the message in.
The new message ID to create.
The ID of the proxy that processed this message.
The ID of the target that handled this message.
The ID of the session that generated this message.
The message type.
The HTTP method.
The HTTP request URL.
The HTTP request headers.
The HTTP request body.
The HTTP status code.
The HTTP response headers.
The HTTP response body.
The connection details.
The payload data extracted from the transaction.
The list of errors that occurred during processing.
The analyze identifier.
The start processing timestamp.
The finish processing timestamp.
DatabaseError If the campaign does not exist.
DatabaseError If the proxy does not exist.
DatabaseError If the target does not exist.
DatabaseError If the session does not exist.
DatabaseError If a message with the same ID already exists.
DatabaseError If the data validation fails.
Creates a new dummy message.
This method only increments counters and does not store the actual message data. Useful for tracking traffic without storing full transaction details.
The ID of the campaign to create the message in.
The new message ID to create.
The ID of the proxy that processed this message.
The ID of the target that handled this message.
The ID of the session that generated this message.
DatabaseError If the campaign does not exist.
DatabaseError If the proxy does not exist.
DatabaseError If the target does not exist.
DatabaseError If the session does not exist.
DatabaseError If a message with the same ID already exists.
DatabaseError If the data validation fails.
Reads the message by its ID.
The ID of the campaign containing the message.
The message ID to read.
The message model, or null if the message is not found.
DatabaseError If the data validation fails.
Reads the full message by its ID.
The ID of the campaign containing the message.
The message ID to read.
The full message model, or null if the message is not found.
DatabaseError If the data validation fails.
Defines the public contract for a message repository.
A message contains a complete HTTP request/response transaction for analysis. Messages are immutable records that capture all details of a processed request.