Dashboard

The dashboard is inndx's web user interface for operating a deployment: creating and inspecting jobs and runs, managing triggers, schemas, data maps, and the other resources crawlctl and the HTTP API expose, without writing commands or requests by hand.

Every action the dashboard supports is also available through crawlctl or the HTTP API.

Signing in

The dashboard reads its credentials from the INNDX_USERNAME and INNDX_PASSWORD environment variables, set when the dashboard starts, and requires LICENSE_KEY to be set with the customer's license key to run. These credentials are used to sign in; if INNDX_USERNAME and INNDX_PASSWORD are not set, the login screen shows a warning in place of the sign-in form. The username is the tenant id used when communicating with the backend services.

Navigation

The sidebar links to each resource type: Overview, Crawl Jobs, Runs, Hosts, Links, Data Schemas, Host Data Maps, and Host URL Patterns. The Overview is the landing view, a deployment-wide snapshot of all jobs, the active jobs, and high-level metrics across them.

Two controls sit at the bottom corners of the layout. The license badge shows the license tier and, when clicked, opens a popup with license details such as when it expires and who issued it. The operational status indicator opens a popup showing the current connectivity to the backend services: the orchestrator, fetcher, parser, sink, and analytics.

Resource lists

Every resource type has a list view. They share the same mechanics and differ only in their columns and the filters each one offers. The header reports the result count and carries a button to create a new resource of that type, which opens that resource's create form.

A control row provides Refresh to reload the data, an Auto toggle for periodic automatic refreshes, Views to save the current filters and reload them later, and Filter to narrow the list by that resource's available filters. The list pages with a next-page control and a dropdown to choose how many items appear per page.

Resource details

Each resource has its own detail view, with a layout suited to that resource type. Jobs and runs use tabbed detail views where each tab shows different information; the other resources have their own layouts.

A job's detail view has Overview, Runs, Triggers, and Configuration tabs: Overview is a snapshot of the job, Runs lists the job's runs, Triggers lists its triggers, and Configuration shows the full job configuration. While the job has an active run, the header shows Pause run and Stop run controls. An overflow menu holds the Edit and Delete actions. The Activity panel on the Overview tab is a non-interactive snapshot of the most recent audit entries for the job and for actions on its runs.

Creating, editing, and deleting

Each list view's create button opens that resource's create form. Because a job has many sections, its create form is a multi-step wizard, moving through Basics, Orchestration, Fetcher, Parser, and a final Review step; the Create button in the card footer of the Review step submits it. Other resources have their own forms suited to their shape.

Editing a job is done on its Configuration tab, which presents the same fields as one large form rather than a stepped wizard. A save pill anchored to the bottom of the page appears only when changes are made and carries the Save action; the import button on that pill is always visible. Editing for the other resources differs per resource.

Deletable resources are deleted from their detail view, usually through the overflow menu. Deleting opens a confirmation modal that requires typing in a value to confirm, usually the resource's name or id.

Applying a manifest from a file

Most resources that can be created and managed expose an Import button in their create and update forms. It opens a modal that accepts JSON, either pasted into the content editor or loaded with Upload file. Applying the import populates the form's fields from that document for submission, replacing the current values.