Skip to main content

Destinations

Telemetry › Destinations has two sections:

  • Huntbase data lake — where your sources send. Every ingest key sends its events here.
  • Your lakes — Huntbase reads these. Apache Iceberg lakes you own and have connected. Huntbase reads them alongside the Huntbase data lake. It never sends events to them.

Your own lakes are connections. You set them up and fix them in Connections; this tab doesn't change them. See Bring your own lake.

Huntbase data lake​

Marked Managed. The card shows its Region, the time of the Last event, and that reading it isn't counted against the scan budget. Below that: how many sources send to it, their events per minute, and their names.

Browse opens Telemetry › Browse on every source. Live tail opens it with the live tail running.

Your lakes​

One card per lake in your scope, marked In federation (queries that include your lakes read it) or Excluded (queries skip it). Each card shows:

  • the state of its schema sync, and when it last synced;
  • the readiness trail: Probe, Catalog, Tables and Schema sync, each done, failed, in progress or not started.

Browse opens Telemetry › Browse reading your lakes as well as the Huntbase data lake. Open connection opens the lake's connection page.

An excluded lake says why, and its action is Fix in Connections. Until it's fixed, its data is missing from every result. See In federation, or excluded. The Overview lists it as an issue too.

With no lakes of your own, the section offers Connect your own lake.