Inspect recorded network activity
This page shows you how to open the Audit Log, read a row, and find the connections you care about.
Who this is for: administrators and security officers. You need: a user in the Network Audit group (Odoo administrators are in it automatically).
Before you begin
- Install the module and let it record traffic.
- Know what a row is: one captured connection, as metadata. It is not a copy of the message.
- Know the limits. The log holds only what the module captured. See Security and capture limits.
Open the Audit Log
- Click Network Audit ▸ Audit Log. You can also click Audit Log in the Trust Report header.
What you should see: a list of recorded connections. The newest row is at the top.
The Audit Log. Each row is one captured connection.
Read a row
| Column | What it tells you |
|---|---|
| Logged | When the row was saved. |
| Direction | in (a request that arrived at your Odoo) or out (a call that your Odoo made). |
| Channel | The way the call was captured, for example requests, httpx, imap, smtp, pop3 or socket. |
| Host | The destination host (or the host that was called, for inbound requests). |
| Method, Status | The HTTP method or protocol action, and the result code where the channel reports one. |
| Addon | The Odoo module that the module believes made the call. It reads the call stack to find the first Odoo module that is not base or web. Other standard Odoo apps, such as Discuss (mail), are named too. A blank value means the module could not name one. |
| MIT-bound | Whether the destination matches the Egress Components list. |
| Req B, Resp B | The size of the request and response in bytes. |
| Seq | The position of the row in the hash chain. |
Extra columns such as Protocol, Addon author and Resp type can be switched on with the column selector in the list header.
Find the rows you need
Use the search box and the filters:
- Type a host, a module name or a channel in the search box.
- Click a filter: Outbound, Inbound, MIT-bound or Errors.
- Click the filter menu and choose Group By ▸ Host, Addon, Channel, Direction or MIT-bound to see counts.
What you should see: only the matching rows, with totals for Req B and Resp B at the bottom of the list.
To see the full detail of one row, click it. See Understand a recorded event.
What a row does not contain
In normal auditing the log has no field for request or response bodies. It holds the destination, sizes, times, the module that made the call, masked sensitive headers and a salted fingerprint of method, host and path. The size columns tell you how much data moved. They do not tell you what it was.
Forensic body capture is separate
An optional forensic body capture can store bodies in a separate list, Captured Bodies. It is off by default. Only users in the Network Forensic Officer group can turn it on or read the bodies, and each read is logged. The Audit Log itself never shows a body. See Change audit settings.
How rows are protected
This section is for administrators and developers.
- The log model refuses
writeandunlinkin Odoo, even forsudo. The only exception is the retention job. - A database trigger blocks changes to the hashed and chain fields of a sealed row. It blocks deletes unless the retention job sets a session flag. A person who controls the database role can set that flag, so the trigger does not stop that person. The hash chain and the signed head are there to make such changes visible. See Verify the log and export evidence.
- Each row has a hash that includes the hash of the row before it.
If it does not work
- The list is empty: check the installation and the Network auditing enabled setting. See Install MIT Network Audit.
- An expected connection is missing: it may be one of the kinds that are not captured, or its channel may be disabled. See Security and capture limits.
- The Addon column is blank: the module found no Odoo module in the call stack, for example because only
baseorwebcode made the call. The Call site is then blank too. Use the host, the time and the channel to judge the row.
Next step
Related: Verify the log and export evidence.