Skip to main content

Nexus Repository Telemetry

Sonatype Nexus Repository's in-product analytics feature helps improve Nexus Repository, guiding the areas on which we focus our efforts.

Required Base Telemetry

Nexus Repository sends required base telemetry to provide expected daily usage metrics for entitlement review.

Expected daily usage metrics include request and component usage data, such as daily repository request counts and current component totals. These values can help Sonatype review usage over time, including total requests in a calendar month and peak components observed in a calendar month.

If expected daily metrics are not received, a grace period may apply.

Note

If your Nexus Repository instance is expected to start frequently, run for short periods, or be unable to send required base telemetry during normal operation, contact Sonatype Support to review available options for your entitlement.

What Gets Sent?

This feature will collect anonymous, non-sensitive information on the general use of Nexus Repository.

  • Anonymous

    We do not collect information that identifies specific users: no usernames, passwords, emails, hostnames, or URLs of any kind.

  • Non-Sensitive

    This feature doesn’t collect identifying information on which you or your teams are working. We don’t collect repository names, component names, coordinates or paths, the names or content of content selectors or routing rules, or paths of any kind—anything that might inadvertently contain information about your organization’s projects or the components you’re using.

  • Configuration

    We collect high-level configuration choices, feature usage rates, internal error frequency, and performance information. Are you using the S3 blob store support? Is it working well? Is it fast enough? Have you switched to NuGet v3, or is v2 still everywhere?

  • Environmental Details

    We collect a limited amount of environmental information to help us understand nuts-and-bolts details like memory and thread pool efficiency. This also helps us understand how organizations are adopting cloud environments and when to expand support for the platforms where you deploy Nexus Repository.

Endpoints to Whitelist

Whitelist the following endpoints to ensure that your Nexus Repository instance can successfully send telemetry:

Community Edition Endpoints

  • https://nxrm.telemetry.sonatype.com/production/oss/ingest

  • https://nxrm.telemetry.sonatype.com/production/oss/v2/ingest

Nexus Repository Pro Endpoints

  • https://nxrm.telemetry.sonatype.com/production/ingest

  • https://nxrm.telemetry.sonatype.com/production/v2/ingest

Example Success and Error Logs

The samples below provide an example of what you can expect to see in the logs when telemetry is successfully sent or when it fails to send:

Success

Telemetry upload successfully with valid signature

Issues Validating Telemetry Payload Signature

Telemetry upload failed (signature verification). Status: {}, URL: {}

Issues with Telemetry Content

 Telemetry upload failed (client error). Status: {}, URL: {}, Response: {}

Issues with Required Base Telemetry

This instance of Nexus Repository has been unable to upload required base telemetry data for the past {} days. This is a warning only. Your instance will continue to operate normally. Check that your server can reach the Sonatype telemetry service, then run the Upload Retry task. If your environment cannot send telemetry or the issue persists, contact Sonatype Support.

Feedback

While automated data is useful, we continue to rely on feedback from developers and DevOps professionals like you to truly understand how you’re using Nexus Repository and how well it meets your needs.

If you have questions or feedback about this program or any other aspect of Nexus Repository, please let us know in the Nexus Repository Manager category.