At the moment, the traces of the conduit service are logging either the consumer ID or the consumer name. Examples:

[category=org.candlepin.subscriptions.conduit.InventoryController]  - Skipping consumer e14a08e7-dbc8-494a-8e77-28cdefef99c1 due to exception ...

Or

[category=org.candlepin.subscriptions.conduit.InventoryController]  - Consumer c5b01008-e213-4503-9dee-4102aac43b39 failed validation: ...

In both traces, the ID and the name seem to be an UUID identifier which is internal to the RHSM API.

On the other hand, the UI displays the systems using the network fdqn:

Therefore, to better troubleshoot issues about system not being ingested or similar, it would be very practical to also trace the network fdqn.

Acceptance Criteria

• Log the network fdqn in the logs of InventoryController
• Also, include into the MDC, the org_id