Inventory & Discovery

This dashboard summarizes document-level results from Processing discovery, broken down by file type. It shows how many documents were discovered for each file type and how many failed, helping administrators identify which content types are driving volume or errors during processing.

Availability

The Inventory & Discovery dashboard is available in Relativity Server 2026 and later. It depends on discovery instrumentation shipped with the Invariant processing components. If the tables are empty, the environment does not include the instrumentation yet, or no discovery activity occurred in the selected time range.

Prerequisites

  • Environment Watch is installed and the Elastic/Kibana stack is receiving telemetry from the target Relativity Server.
  • The Relativity Server is version 2026+ so that Invariant discovery metrics are emitted.
  • Discovery jobs have run within the selected time range.

The Inventory & Discovery dashboard is part of the Processing feature domain. A tab strip at the top lets you switch between:

A left-hand navigation panel provides quick links to other Environment Watch feature domains.

Filters and Time Range

  • Time range - Use the time picker in the top-right to scope both tables. The dashboard does not save a fixed time range, so it opens with your Kibana default (or last-used) range.
  • KQL filter bar - Use the query bar to narrow results, for example by file type or host.

Discovery Results by File Type

  • Discover Documents Processed - Table of file types and the number of documents discovered for each, sorted with the highest count first. Columns: File Type and Processed.
  • Discover Documents Failed - Table of file types and the number of documents reported as failed by the Invariant failed-document count, sorted with the highest count first. The count comes from a single Invariant metric and does not by itself identify at which processing stage or for what reason a document failed. Columns: File Type and Failed Count.

Both tables are paginated (10 rows per page). Discovered counts non-container files only, while Failed is any document-level error from any processing phase and can include containers. Because the two counts cover different scopes, do not use the failed count to calculate a discovery failure rate against the discovered count. Use it to see which file types account for the most reported failures, then investigate those file types further.

Metrics Reference

OTEL metrics

OTEL metric Description
relsvr.invariant.common.documentdiscovercount Number of documents discovered.
relsvr.invariant.common.documentfailedcount Number of documents reported as failed by Invariant.

Label fields

Field Description
labels.relsvr_system Source system; the dashboard uses Invariant.
labels.file_type File type of the discovered document.

Panel-to-metric mapping

Panel Type Metric Key fields
Discover Documents Processed Table relsvr.invariant.common.documentdiscovercount sum, grouped by labels.file_type
Discover Documents Failed Table relsvr.invariant.common.documentfailedcount sum, grouped by labels.file_type

Use Cases

Use Case Description
Understand discovery volume See which file types make up the discovered content.
Isolate problematic file types Identify file types with high failed-document counts.
Validate processing after changes After an installation or configuration change, confirm documents are discovered and failures stay low.

Associated Alerts

No processing-specific Environment Watch alerts are currently associated with this dashboard. This section will be updated as processing alerts are published.

Feedback