Sonatype is adding optional, in-product analytics to Nexus Repository OSS. This is an important change that will help us improve Repository, guiding the areas on which we focus our efforts. What’s working at scale? What might need some attention?
For some time, we’ve had a similar analytics program for Nexus Repository Pro that’s been enormously helpful. We’d now like to do the same for OSS.
This is an optional program. As of version 3.31.0, the first time you sign in as an administrator, you’ll be asked if you’d like to participate.
If you agree, Nexus Repository OSS will periodically send Sonatype a data packet about feature usage and configuration choices. If you decline, analytics remains disabled (it’s off by default) and nothing gets sent to Sonatype.
If you change your mind, you can enable or disable analytics in the Capabilities administration section of the UI. If at any point you want to inspect what’s being sent to Sonatype, you can do so by visiting the /service/data/metrics endpoint on your Nexus Repository instance and looking for elements that start with “nexus.analytics.”
This feature will collect anonymous, non-sensitive information about your use of Nexus Repository OSS.
By anonymous, we mean that we don’t collect information that would identify specific users: no usernames, passwords, emails, hostnames, or URLs of any kind.
By non-sensitive, we mean this feature doesn’t collect anything that could identify anything 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.
What we do collect is 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?
We also 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 see how the great cloud migration is going and when it’s time to deepen our support for new environments where you are deploying Nexus Repository.
Of course, while automated data is extremely useful, we continue to rely on feedback from developers and DevOps professionals like you to truly understand how you’re using Nexus Repository OSS 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 on this post or in the Nexus Repository Manager category.