DataTugPull more from your data
Open app
☰

For your role · SRE, on-call and L3 engineers

For SRE and on-call: incidents across systems

An incident rarely stays in one system. DataTug is building investigations that keep the queries, the log lines and the finding together, so the trail survives the handover, and a Check that spots the same cause next time.

Explore the demo project All roles
Watercolor of a calm night watch on a tugboat’s bridge, a crew member at the wheel with a mug, a logbook under a small lamp and a lighthouse beam outside.

The incident touches four systems. By the time I have the evidence in one place the shift is over, and the next person starts again.

Your day

  • Evidence in six tabs. Queries, dashboards and log searches each live in their own tool, joined by IDs copied by hand.
  • Handovers that lose the thread. The next on-call reads a chat thread to find out what you already ruled out.
  • The same cause twice. The postmortem says “add monitoring”, and the same data problem comes back a month later.

One task, before and after: trace a payment that was taken but never booked

Who: SRE, on-call and L3 engineers

Today

4 tools2 hand-offsno shared password

  1. On-call · SQL clientQuery the orders database, then the payments database.
  2. On-call · Log searchSearch the logs for the same order and time window.
  3. Next on-call · ChatSummarise the findings in chat for the handover.
  4. Someone, later · TicketWrite a ticket to add monitoring later.
Today4 tools · 2 hand-offs · no shared passwordQuery the orders database, then the payments database.Search the logs for the same order and time window.Summarise the findings in chat for the handover.Click to see

With DataTug

1 workspace0 hand-offsno shared password

Some steps are planned or in development.

  1. On-callStart from the order and follow its related records across sources.Related records in the web appAvailable
  2. On-callRead the logs filtered to the same order and time window.Log viewerPreview
  3. Next on-callKeep queries, evidence and notes in one case the next engineer can resume (in development).Detective CasesIn development
  4. The teamTurn the query that found the cause into a Check you rerun (in development).Reusable ChecksIn development
With DataTug1 workspace · 0 hand-offs · no shared passwordStart from the order and follow its related records across sources.Read the logs filtered to the same order and time window.Keep queries, evidence and notes in one case the next engineer can resume (in development).Click to see

Each step names the part of DataTug it relies on and that part’s status today. “Planned” and “In development” steps describe where the product is going, not what you can use now.

Solutions for you

Also useful: Data Understanding

Try it on sample data

The public demo project opens in the browser with sample Northwind and Chinook data. No sign-up.

Explore the demo project