Read logs where they live

The problem

When the database says an order did not ship, how do you see what the services logged about it?

Logs sit in files and cloud logging while the business record sits in a database. Lining them up means exporting, searching and copying timestamps, or copying the logs into yet another store just to look at them.

A clearer workflow

1. Point at the source

   Choose a log collection served through OpenVaultDB, or an allowed Cloud Logging view. Nothing is copied or ingested. Serving logs is separate from OVDB (OpenVaultDB) session storage, which is DataTug’s own working context.

2. Filter to the case

   Narrow by order ID, correlation ID, time range and severity. For log files, include untimed or malformed entries when you need them.

3. Inspect the evidence

   Sort and select entries in a grid, and read the original raw entry beside its parsed fields.