Pull History

Pull history tracks every time a customer pulls an image from your repositories. Use this data to understand usage patterns, verify deployments, and support billing discussions.

What is Tracked?

Every successful image pull records:

• Timestamp: When the pull occurred
• Customer: Which customer pulled the image
• Repository: Which repository was accessed
• Tag: The specific image tag pulled
• Auth Token: Which token was used

Viewing Pull History

All Pulls

1. Navigate to Pulls in the vendor portal
2. View the list of recent pulls (up to 100 most recent)

Customer-Specific Pulls

1. Navigate to a customer's detail page
2. View their recent pulls at the bottom of the page

Or filter the main pulls page:

1. Go to Pulls
2. Use the customer dropdown to filter

Repository-Specific Pulls

1. Navigate to a repository's detail page
2. View recent pulls for that repository

Filtering Pull History

The Pulls page supports filtering by:

Customer

Select a customer from the dropdown to see only their pulls.

Date Range

Filter by date range:

• Start Date: Show pulls on or after this date
• End Date: Show pulls on or before this date

You can use one or both filters to narrow down the results.

Pull Details

Each pull record shows:

Use Cases

Usage Tracking

Monitor how customers are using your software:

• Which versions are most popular
• How often customers are pulling updates
• Whether customers are staying current or on older versions

Deployment Verification

Confirm that customers have deployed:

• New versions after release
• Security updates
• Licensed versions (not expired tags)

Troubleshooting

Help customers debug issues:

• Verify they're pulling the expected version
• Check if pulls are succeeding
• Identify which token/server is pulling

Billing Support

Support usage-based billing discussions:

• Document pull frequency
• Show activity over time periods
• Verify access within license dates

Reading the Data

Recent vs Historical

The Pulls page shows the 100 most recent pulls. For comprehensive historical data, use the date filters to focus on specific time periods.

Multiple Pulls

You may see multiple pulls for the same image because:

• Docker checks for updates (pulls manifest even if image is cached)
• Different servers in customer's infrastructure
• Customer's CI/CD pipeline pulling the same image repeatedly

Vendor Pulls

Pulls from your own vendor tokens are not shown in the main pulls list, which focuses on customer activity.

Best Practices

Regular Review

• Check pulls periodically to understand usage
• Look for customers who stopped pulling (may indicate issues)
• Monitor adoption of new versions

Customer Support

When helping customers:

1. Check recent pulls to understand their situation
2. Verify they're using the correct version
3. Confirm auth tokens are working

Release Monitoring

After releasing a new version:

1. Filter by date to see recent activity
2. Check if customers are pulling the new version
3. Follow up with customers still on old versions

Limitations

• 100 pull limit: The page shows the 100 most recent pulls
• Customer pulls only: Vendor token pulls are not tracked in this view
• Successful pulls only: Failed authentication or access denied attempts are not shown