MIT Network Audit docs
The audit log

Understand a recorded event

4 min read Odoo 18.0

This page explains each field of one recorded event, so you know what the log tells you about a connection and what it leaves out.

Who this is for: administrators and security officers. You need: a user in the Network Audit group.

Before you begin

  1. Open Network Audit ▸ Audit Log and find a row. See Inspect recorded network activity.
  2. Click the row. The Network egress event form opens. It is read-only.

One row of the Audit Log opened as a form, showing the groups What, Where, Who, Size and timing, and the chain fields One recorded event.

Metadata, not content

In normal auditing, the event has no field for a request or response body. The form shows what the module recorded about the call, not what was in it.

What happened

Field What it tells you
Direction out for a call your Odoo made, in for a request that arrived.
Channel The way the call was captured, for example requests, httpx, urllib, imap, smtp, pop3, the TLS socket, or the plain socket connection.
Protocol The protocol seen, for example HTTP or HTTPS.
Method The HTTP method, or the matching action for the channel.
Status The result code, where the channel reports one.
Is MIT-bound Whether the destination matches the Egress Components list when the row was saved. Later changes to the list do not change old rows.

A socket channel row is not an error. It is the lowest-level capture of a connection that no library-level capture picked up. Such rows usually hold less detail than library-level rows.

Where it went

Field What it tells you
Host The destination host.
Url path The path of the URL, stored in full. If a path contains a token or an identifier, it is stored too. Strict redaction removes the path.
Query keys The names of the query parameters, never their values.
Dest ip, Dest port The address and port the connection reached.
Src ip, Src port The local address and port.

Who made the call

Field What it tells you
Addon technical name The technical name of the Odoo module found on the call stack, for example maildesk_mail_client.
Module The matching installed module record.
Addon author The author in that module's manifest.
Call site The file, line and function of the call in that module.

The module reads the live call stack and takes the first Odoo module that is not base, web or MIT Network Audit itself. Calls from other standard Odoo apps, such as Discuss (mail), are shown under that app. The result names the module whose code started the call. It does not prove that the module's author intended the call.

Size and timing

Field What it tells you
Request bytes, Response bytes How many bytes were sent and received.
Size buckets A coarse size label, for example "1–10 KB".
Request content type, Response content type The media type, without parameters.
Duration ms How long the call took.
Request fingerprint A salted hash of the method, host and path. It groups repeated calls. It is not a hash of the content. Strict redaction removes it.
Response fingerprint Currently always empty.
Error A short error text with credentials removed, if the call failed.

Where the record came from

Field What it tells you
Logged at When the row was saved.
Worker pid The process ID of the Odoo process that captured the call.
Db name The database in which the event was saved.

The chain fields

Field What it tells you
Seq The position of the row in the hash chain.
Prev Hash The hash of the previous row.
Row Hash A SHA-256 hash over this row's fixed fields and the previous hash.

The chain fields and the request and response headers on one recorded event The chain fields, and below them the request and response headers.

Each row's hash includes the hash of the row before it. If someone changes or removes a row in the middle of the chain, the later hashes no longer match, and Verify chain names the first row that fails.

What the chain shows and what it does not

  • It shows edits, inserted rows and removed rows inside the chain.
  • It does not show that every connection was captured.
  • It does not show that the tail of the log was cut off. Only the daily signed head can show that, and only if you compare it with the log. The signing key is stored in the same database, so a person with full control of the database could replace the chain and the signed head together.
  • The headers and content types that you see on this form are not part of the hash.

Headers

The form shows request and response headers. The module masks the value of headers that it treats as sensitive: Authorization, Proxy-Authorization, Cookie, Set-Cookie, X-Api-Key, WWW-Authenticate, Proxy-Authenticate, and any header whose name contains token, secret, password, api-key or auth. It cuts Location to the scheme and host and Content-Disposition to its type. All other header values are stored as they are.

Strict redaction

With Strict redaction on, new rows keep no URL path, no query keys and no fingerprint. They still keep the host, address, port, sizes, timing, status and the module. See Change audit settings.

If it does not work

  • The form shows less detail than described: the row may come from the socket channel, or Strict redaction was on when it was saved.
  • A field is blank: the channel does not report it. For example, a raw socket has no HTTP status.
  • You need the content of a call: the normal log cannot give it to you. Forensic body capture is the only source, and it needs a Network Forensic Officer. See Change audit settings.

Next step

Verify the log and export evidence.

Related: Understand the Trust Report.