Start free

Investigate

When something looks wrong, find out why.

Open an investigation and Juno drives it with a dedicated toolkit. It pulls run history, audit logs, contract violations and lineage, runs the statistics, and hands back structured findings, cited evidence, a timeline and a causal diagram.

Start freeSee pricing

Lenses

Look at the problem from the right angle.

Every investigation starts with a lens, and you can blend several.

Root causeWhat started it, and what followed.
AnomalyWhat’s out of the ordinary, and since when.
ImpactWho and what the problem touched.
TimelineWhat happened, in order.
TrendWhere a number is heading, and how fast.
Data qualityDuplicates, invalid cells, stale sources.
PerformanceSlow runs, failure streaks, reliability.
LineageWhere data came from and where it went.
ComplianceWho changed what, according to the audit log.

An example investigation

“Why did revenue drop on Tuesday?”

Juno traces the dashboard back to its source, finds where the chain broke, and lays out the evidence in order.

Credentials rotatedorders_db · Mon 23:10 Sync failed 3 timeshourly import · 401 Orders sheet staleno new rows for 6 h Contract warnedfreshness · 6 h Revenue graphmissing Tue orders Revenue looked 18% lowerdashboard · Tue

Timeline

  1. Credentials rotated on orders_db, per the audit log.

  2. First failed sync. The hourly import returns 401.

  3. Third failure. A failure streak begins.

  4. Freshness contract warns. Orders hasn’t updated in 6 hours.

  5. Dashboard viewed. Revenue appears 18% lower than Monday.

Example data. Finding: update the connection credentials, then re-run the import.

Toolkits

The statistics and the checks, built in.

Statistical tools

Period comparisons, outlier detection, change points, correlation, error clustering, failure streaks, reliability stats, forecasting and periodicity.

Data-quality tools

Column profiling, duplicate and invalid-cell detection, freshness checks, recent-change review, connection health, blast radius, orphaned resources and contract coverage.

Findings

Share what you found.

Every investigation ends in structured findings with cited evidence, a timeline and a causal diagram. Save your approach as a reusable template, export the report, or share read-only findings with a link.

  • Export to Markdown, plus PDF from Beam
  • Templates and shareable findings from Ray
  • Scheduled, recurring investigations from Aurora
Finding 1Rotated credentials broke the orders import3 sources
Finding 2No alert fired for the failure streak2 sources
Next stepUpdate credentials, enable connection alertsowner: Ops