Nexus Repository Telemetry

Starting in Nexus Repository 3.97.0, an administrator must acknowledge the required base telemetry requirement during onboarding. The acknowledgement appears for both new self-hosted installations and instances upgraded to Nexus Repository 3.97.0 or later.

The acknowledgement records that an administrator understands the telemetry requirement and the effect of unsuccessful telemetry delivery. Acknowledgement is recorded once for the Nexus Repository instance. After it is recorded, administrators are not prompted to acknowledge the requirement again.

Nexus Repository monitors required base telemetry delivery and provides a grace period when telemetry cannot be successfully uploaded. The grace period depends on the Nexus Repository edition:

Nexus Repository counts qualifying failures by the date of the telemetry report's collection period. Multiple failed attempts for the same reporting day, including attempts from different nodes in a high-availability deployment, count as one day. Only reporting days after the latest successful upload count toward the grace period. Retrying the same report does not consume an additional day.

During the grace period, Nexus Repository continues to operate normally. A Baseline Telemetry Upload Issue warning appears when upload failures require administrator attention and shows the remaining grace-period time.

To resolve a required base telemetry upload issue, take the following steps:

After Nexus Repository successfully uploads required base telemetry, the telemetry warning is cleared.

Use GET /service/rest/v1/status/check to monitor required base telemetry. The endpoint requires authentication and the nexus:metrics:read permission. The endpoint returns all registered health checks.

Use the following command to retrieve the Baseline Telemetry result:

curl -u '<username>:<password>' \
  'https://<nexus-host>/service/rest/v1/status/check' \
  | jq '."Baseline Telemetry"'

Example Response 1:

"Baseline Telemetry": {
  "healthy": true,
  "message": "Baseline Telemetry status: Active. Last successful upload: 2026-10-20T03:15:42.123456-04:00.",
  "error": null,
  "details": null,
  "duration": 4,
  "timestamp": "2026-10-21T09:12:01.512Z"
}

Example Response 2:

"Baseline Telemetry": {
  "healthy": false,
  "message": "Baseline Telemetry status: Not acknowledged. Mandatory telemetry acknowledgement was not received.",
  "error": null,
  "details": null,
  "duration": 1,
  "timestamp": "2026-10-21T09:12:01.490Z"
}

Review healthy and message fields to identify the telemetry state and required action. The following table describes the possible states and the action to take for each.

You can query or record the required base telemetry acknowledgement through the Nexus Repository REST API.

Both operations require authentication and the nexus:* permission. The endpoint is:

/service/rest/v1/system/mandatory-telemetry-acknowledgement

GET Example:

curl -u <username>:<password> \
  -X GET \
  https://<nexus-host>/service/rest/v1/system/mandatory-telemetry-acknowledgement

POST Example:

curl -u <username>:<password> \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"acknowledgement":true}' \
  https://<nexus-host>/service/rest/v1/system/mandatory-telemetry-acknowledgement

Refer to Nexus Repository API Reference page for more details.

Nexus Repository enters telemetry-related read-only mode when the number of qualifying failed reporting days reaches the grace period limit for your edition and version.

To restore normal operation, resolve the telemetry connectivity issue and successfully send required base telemetry. Run the Upload Retry task after restoring connectivity if you want to retry the upload immediately. To know the general procedure to create and configure a task, see Tasks.