If you’re using the Replicated proxy registry to give your customers pull-through access to images hosted in your own external registries, you may not be aware that you have access to pull activity logs for those connected registries directly in the Vendor Portal.
This can be useful when you need a quick answer to questions like: which images are my customers pulling from a given registry, and are those pulls succeeding?
Where to find it
Navigate to Image Registries in the Vendor Portal sidebar. For each connected external registry, you’ll see a Recent Pull Activity section on the right side of the registry detail card showing the most recent pulls at a glance, including the image name, the date, the customer who pulled it, and whether the pull was successful.
To see the full history, click View all logs. This opens a detailed view with the following columns:
- Date: timestamp of the pull event
- Customer: which customer license was used
- Action: the type of registry operation (e.g. `auth`, `manifest`)
- Image: the image name that was pulled
- Tag: the image tag or version, when applicable
What’s covered
This pull activity tracking applies to external registries that you have connected to the Replicated proxy registry such as an Amazon ECR, Docker Hub, or other OCI-compatible registry that you’ve added via the + Add external registry flow in Vendor Portal. The logs capture pulls that your customers make through the proxy (e.g. via `proxy.replicated.com` or your custom domain).
The logs are a handy spot check to confirm whether a customer has pulled a specific image, or verifying that a registry connection is working after setup. The log view is currently a straightforward chronological list that is most useful for recent pull access awareness.
What’s not covered
Pull activity logs are not available for images hosted directly in the Replicated private registry. This feature is specific to external registries connected through the Replicated proxy registry, as Replicated recommends using the Replicated proxy registry for both private and public image distribution to customers for production-level installations.