mirror of
https://github.com/docker/docs.git
synced 2026-03-27 06:18:55 +07:00
hub: dvp docs update (#23474)
<!--Delete sections as needed -->
## Description
- Added Hub infrastructure as benefit for DVP, and add a visual.
- Based on existing public info at:
- https://www.docker.com/trust/availability/
- https://www.cloudflare.com/case-studies/docker/
- Rearranged topic structure and flesh out the benefits section.
- Added DVP Core GUI and reports to analytics topic
- Added how DVPers can verify no pull limit
- Added that DVP is applied per namespace/org.
Updated pages:
https://deploy-preview-23474--docsdocker.netlify.app/docker-hub/repos/manage/trusted-content/dvp-program/
https://deploy-preview-23474--docsdocker.netlify.app/docker-hub/repos/manage/trusted-content/insights-analytics/
## Related issues or tickets
ENGDOCS-3020
ENGDOCS-3035
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Editorial review
- [ ] Product review
- [ ] Engineering review
---------
Signed-off-by: Craig <craig.osterhout@docker.com>
Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
This commit is contained in:
Craig Osterhout
@@ -73,6 +73,7 @@ EPERM
|
||||
ESXi
|
||||
Ethernet
|
||||
exploitability
|
||||
[Ff]ailover
|
||||
Fargate
|
||||
Fedora
|
||||
firewalld
|
||||
@@ -226,6 +227,7 @@ Zsh
|
||||
[Aa]gentic
|
||||
[Aa]utobuilds?
|
||||
[Aa]utotests?
|
||||
[Aa]utoscaling
|
||||
[Bb]uildx
|
||||
[Bb]uildpack(s)?
|
||||
[Bb]uildx
|
||||
@@ -234,6 +236,7 @@ Zsh
|
||||
[Cc]onfigs
|
||||
[dD]eduplicate
|
||||
[Dd]ev
|
||||
[Dd]iscoverability
|
||||
[Dd]istroless
|
||||
[Ff]ilepaths?
|
||||
[Ff]iletypes?
|
||||
@@ -271,6 +274,7 @@ Zsh
|
||||
[Ss]yscalls?
|
||||
[Ss]ysfs
|
||||
[Tt]eardown
|
||||
[Tt]echnographic
|
||||
[Tt]odo
|
||||
[Tt]oolchains?
|
||||
[Uu]narchived?
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 176 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 8.0 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 37 KiB After Width: | Height: | Size: 13 KiB |
@@ -31,8 +31,7 @@ These benefits are valid for one year and publishers can renew annually if the p
|
||||
DSOS organizations can upload custom images for individual repositories on Docker Hub.
|
||||
This lets you override the default organization-level logo on a per-repository basis.
|
||||
|
||||
Only a user with administrative access (owner or team member with administrator permission)
|
||||
over the repository can change the repository logo.
|
||||
Only a user with an owner or editor role for the organization can change the repository logo.
|
||||
|
||||
#### Image requirements
|
||||
|
||||
|
||||
@@ -14,44 +14,156 @@ aliases:
|
||||
- /docker-hub/publish/repository-logos/
|
||||
- /docker-hub/dvp-program/
|
||||
- /trusted-content/dvp-program/
|
||||
toc_max: 2
|
||||
---
|
||||
|
||||
[The Docker Verified Publisher Program](https://hub.docker.com/search?q=&image_filter=store) provides high-quality images from commercial publishers verified by Docker.
|
||||
[The Docker Verified Publisher
|
||||
Program](https://hub.docker.com/search?q=&image_filter=store) provides
|
||||
high-quality images from commercial publishers verified by Docker.
|
||||
|
||||
These images help development teams build secure software supply chains, minimizing exposure to malicious content early in the process to save time and money later.
|
||||
These images help development teams build secure software supply chains,
|
||||
minimizing exposure to malicious content early in the process to save time and
|
||||
money later.
|
||||
|
||||
Images that are part of this program have a special badge on Docker Hub making it easier for users to identify projects that Docker has verified as high-quality commercial publishers.
|
||||
## Who's eligible to become a verified publisher?
|
||||
|
||||
|
||||
Any independent software vendor who distributes software on Docker Hub can join
|
||||
the Verified Publisher Program. Find out more by heading to the [Docker Verified
|
||||
Publisher Program](https://www.docker.com/partners/programs) page.
|
||||
|
||||
The Docker Verified Publisher Program (DVP) provides several features and benefits to Docker
|
||||
Hub publishers. The program grants the following perks based on participation tier:
|
||||
> [!NOTE]
|
||||
>
|
||||
> DVP entitlements are applied per namespace (organization). If you operate
|
||||
> multiple Docker Hub namespaces, each requires a separate DVP application and
|
||||
> verification process.
|
||||
|
||||
- Repository logo
|
||||
- Verified publisher badge
|
||||
- Priority search ranking in Docker Hub
|
||||
- Insights and analytics
|
||||
- Vulnerability analysis
|
||||
- Additional Docker Business seats
|
||||
- Removal of rate limiting for developers
|
||||
- Co-marketing opportunities
|
||||
## Program benefits
|
||||
|
||||
The Docker Verified Publisher Program (DVP) provides several features and
|
||||
benefits to Docker Hub publishers. The program grants the following perks based
|
||||
on participation tier:
|
||||
|
||||
- [Enterprise-grade infrastructure](#enterprise-grade-infrastructure): High
|
||||
availability hosting with 99.9% uptime
|
||||
- [Verified publisher badge](#verified-publisher-badge): Special badge
|
||||
identifying high-quality commercial publishers
|
||||
- [Repository logo](#repository-logo): Upload custom logos for individual
|
||||
repositories
|
||||
- [Insights and analytics](#insights-and-analytics): Detailed usage metrics and
|
||||
community engagement data
|
||||
- [Vulnerability analysis](#vulnerability-analysis): Automated security scanning
|
||||
with Docker Scout
|
||||
- [Priority search ranking](#priority-search-ranking): Enhanced discoverability
|
||||
in Docker Hub search results
|
||||
- [Removal of rate limiting](#removal-of-rate-limiting): Unrestricted pulls for
|
||||
development teams
|
||||
- [Co-marketing opportunities](#co-marketing-opportunities): Joint promotional
|
||||
activities with Docker
|
||||
|
||||
### Enterprise-grade infrastructure
|
||||
|
||||
The Docker Verified Publisher Program runs on Docker Hub's enterprise-scale
|
||||
infrastructure, serving millions of developers globally. Your published content
|
||||
benefits from:
|
||||
|
||||
- High availability and uptime: Docker's systems are designed for failover
|
||||
across multiple availability zones, with load-balanced autoscaling, enabling
|
||||
99.9% uptime.
|
||||
- Global delivery and fast downloads: Docker leverages Cloudflare's CDN and
|
||||
caching (with Cache Reserve) to achieve cache hit ratios more than 99%,
|
||||
reducing reliance on origin traffic and ensuring fast access for developers
|
||||
everywhere.
|
||||
- Durability: Docker maintains a documented backup policy and performs full
|
||||
daily backups of production data.
|
||||
|
||||
You simply push your images to Docker Hub as usual, and Docker takes care of the
|
||||
rest, serving your image to millions of developers worldwide.
|
||||
|
||||
|
||||
|
||||
To learn more, see [Availability at
|
||||
Docker](https://www.docker.com/trust/availability/).
|
||||
|
||||
### Verified publisher badge
|
||||
|
||||
Images that are part of this program have a special badge on Docker Hub making
|
||||
it easier for users to identify projects that Docker has verified as
|
||||
high-quality commercial publishers.
|
||||
|
||||
|
||||
|
||||
### Repository logo
|
||||
|
||||
DVP organizations can upload custom images for individual repositories on Docker Hub.
|
||||
This lets you override the default organization-level logo on a per-repository basis.
|
||||
DVP organizations can upload custom images for individual repositories on Docker
|
||||
Hub. This lets you override the default organization-level logo on a
|
||||
per-repository basis.
|
||||
|
||||
Only a user with administrative access (owner or team member with administrator permission)
|
||||
over the repository can change the repository logo.
|
||||
To manage the repository logo, see [Manage repository logo](#manage-repository-logo).
|
||||
|
||||
#### Image requirements
|
||||
### Vulnerability analysis
|
||||
|
||||
[Docker Scout](/scout/) provides automatic vulnerability analysis
|
||||
for DVP images published to Docker Hub.
|
||||
Scanning images ensures that the published content is secure, and proves to
|
||||
developers that they can trust the image.
|
||||
|
||||
You can enable analysis on a per-repository basis. For more about using this
|
||||
feature, see [Basic vulnerability
|
||||
scanning](/docker-hub/repos/manage/vulnerability-scanning/).
|
||||
|
||||
### Priority search ranking
|
||||
|
||||
Verified publisher images receive enhanced visibility in Docker Hub search
|
||||
results, making it easier for developers to discover your content. This improved
|
||||
discoverability helps drive adoption of your images within the developer
|
||||
community.
|
||||
|
||||
### Removal of rate limiting
|
||||
|
||||
Verified publisher images are exempt from standard [Docker Hub rate
|
||||
limits](../../../usage/_index.md), ensuring developers can pull your images
|
||||
without restrictions. **This applies to all users, including unauthenticated users**,
|
||||
who get unlimited pulls for DVP images. This eliminates potential barriers to adoption and
|
||||
provides a seamless experience for users of your content.
|
||||
|
||||
DVP partners can verify this unlimited access by checking the absence of rate
|
||||
limiting headers when pulling their images. When pulling DVP images, users won't
|
||||
see `ratelimit-limit` or `ratelimit-remaining` headers, indicating unlimited
|
||||
access. For more details on checking rate limits, see [View pull rate and
|
||||
limit](../../../usage/pulls.md#view-pull-rate-and-limit).
|
||||
|
||||
### Co-marketing opportunities
|
||||
|
||||
Docker collaborates with verified publishers on joint marketing initiatives,
|
||||
including blog posts, case studies, webinars, and conference presentations.
|
||||
These opportunities help amplify your brand visibility within the Docker
|
||||
ecosystem.
|
||||
|
||||
### Insights and analytics
|
||||
|
||||
The insights and analytics service provides usage metrics for how
|
||||
the community uses Docker images, granting insight into user behavior.
|
||||
|
||||
There is both a [web interface](./insights-analytics.md) and an
|
||||
[API](/reference/api/dvp/latest/) for accessing the analytics data.
|
||||
|
||||
The usage metrics show the number of image pulls by tag or by digest,
|
||||
geolocation, cloud provider, client, and more.
|
||||
|
||||
## Manage repository logo
|
||||
|
||||
After joining the Docker Verified Publisher Program, you can set a custom logo
|
||||
for each repository in your organization. The following requirements apply:
|
||||
|
||||
- The supported filetypes for the logo image are JPEG and PNG.
|
||||
- The minimum allowed image size in pixels is 120×120.
|
||||
- The maximum allowed image size in pixels is 1000×1000.
|
||||
- The maximum allowed image file size is 5MB.
|
||||
|
||||
#### Set the repository logo
|
||||
Only a user with an owner or editor role for the organization can change the repository logo.
|
||||
|
||||
### Set the repository logo
|
||||
|
||||
1. Sign in to [Docker Hub](https://hub.docker.com).
|
||||
2. Go to the page of the repository that you want to change the logo for.
|
||||
@@ -61,44 +173,12 @@ current repository logo.
|
||||
4. In the dialog that opens, select the PNG image that you want to upload to
|
||||
set it as the logo for the repository.
|
||||
|
||||
#### Remove the logo
|
||||
### Remove the logo
|
||||
|
||||
Select the **Clear** button ({{< inline-image src="../../../images/clear_logo_sm.png"
|
||||
alt="clear button" >}}) to remove a logo.
|
||||
|
||||
Removing the logo makes the repository default to using the organization logo, if set, or the following default logo if not.
|
||||
Removing the logo makes the repository default to using the organization logo,
|
||||
if set, or the following default logo if not.
|
||||
|
||||
|
||||
|
||||
### Verified publisher badge
|
||||
|
||||
Images that are part of this program have a badge on Docker Hub making it easier for developers
|
||||
to identify projects that Docker has verified as high quality publishers and with content they can trust.
|
||||
|
||||
|
||||
|
||||
### Insights and analytics
|
||||
|
||||
The [insights and analytics](./insights-analytics.md) service provides usage metrics for how
|
||||
the community uses Docker images, granting insight into user behavior.
|
||||
|
||||
The usage metrics show the number of image pulls by tag or by digest, and breakdowns by
|
||||
geolocation, cloud provider, client, and more.
|
||||
|
||||
You can select the time span for which you want to view analytics data. You can also export the data in either a summary or raw format.
|
||||
|
||||
### Vulnerability analysis
|
||||
|
||||
[Docker Scout](/scout/) provides automatic vulnerability analysis
|
||||
for DVP images published to Docker Hub.
|
||||
Scanning images ensures that the published content is secure, and proves to
|
||||
developers that they can trust the image.
|
||||
|
||||
You can enable analysis on a per-repository
|
||||
basis. For more about using this feature, see [Basic vulnerability scanning](/docker-hub/repos/manage/vulnerability-scanning/).
|
||||
|
||||
### Who's eligible to become a verified publisher?
|
||||
|
||||
Any independent software vendor who distributes software on Docker Hub can join
|
||||
the Verified Publisher Program. Find out more by heading to the
|
||||
[Docker Verified Publisher Program](https://www.docker.com/partners/programs) page.
|
||||
|
||||
File diff suppressed because one or more lines are too long
|
After Width: | Height: | Size: 21 KiB |
@@ -8,22 +8,289 @@ aliases:
|
||||
- /trusted-content/insights-analytics/
|
||||
---
|
||||
|
||||
Insights and analytics provides usage analytics for Docker Verified
|
||||
Publisher (DVP) and Docker-Sponsored Open Source (DSOS) images on Docker Hub. This includes self-serve access to image and extension usage metrics for a desired time span. You can also display the number of image pulls by tag or by digest, and get breakdowns by geolocation, cloud provider, client, and more.
|
||||
Insights and analytics provides usage analytics for [Docker Verified Publisher
|
||||
(DVP)](https://www.docker.com/partners/programs/) and [Docker-Sponsored Open
|
||||
Source (DSOS)](https://www.docker.com/community/open-source/application/#)
|
||||
images on Docker Hub. This includes self-serve access to image and extension
|
||||
usage metrics for a desired time span. You can see the number of image pulls by
|
||||
tag or by digest, geolocation, cloud provider, client, and more.
|
||||
|
||||
<!-- prettier-ignore -->
|
||||
> [!TIP]
|
||||
> [!NOTE]
|
||||
>
|
||||
> Head to the
|
||||
[Docker Verified Publisher Program](https://www.docker.com/partners/programs/) or [Docker-Sponsored Open Source](https://www.docker.com/community/open-source/application/#) pages
|
||||
to learn more about the programs.
|
||||
> The Legacy DVP program applies to existing customers who have not yet renewed
|
||||
> to DVP Core. The DVP Legacy program is deprecated and will be retired. Contact
|
||||
> your Docker sales representative or
|
||||
> [Docker](https://www.docker.com/partners/programs/) for more information.
|
||||
|
||||
{{< tabs >}}
|
||||
{{< tab name="DVP program" >}}
|
||||
|
||||
All members of an organization have access to the analytics data. Members can
|
||||
access analytics data in the [Docker Hub](https://hub.docker.com/) web interface
|
||||
or by using the [DVP Data API](/reference/api/dvp/latest/). The following covers
|
||||
the web interface.
|
||||
|
||||
## Available reports
|
||||
|
||||
The following reports may be available for download as CSV files:
|
||||
|
||||
- [Summary](#summary-report)
|
||||
- [Trends](#trends-report)
|
||||
- [Technographic](#technographic-report)
|
||||
- [Technographic companies](#technographic-companies-report)
|
||||
- [Tracked companies](#tracked-companies-report)
|
||||
|
||||
The reports available for download may vary based on your organization's
|
||||
subscription. Contact your Docker sales representative or
|
||||
[Docker](https://www.docker.com/partners/programs/) for more information.
|
||||
|
||||
### Summary report
|
||||
|
||||
The summary report provides high-level usage metrics aggregated across all your
|
||||
Docker Hub content, organized by namespace and repository. This report gives you
|
||||
a comprehensive overview of your image portfolio performance, helping you
|
||||
understand which repositories, tags, and specific image versions are most
|
||||
popular with your users.
|
||||
|
||||
You can use this report to answer questions like:
|
||||
|
||||
- Which of my repositories are getting the most usage?
|
||||
- How do different image tags compare in terms of adoption?
|
||||
- What's the ratio of actual downloads versus version checks across my
|
||||
portfolio?
|
||||
- Which specific image digests are being pulled most frequently?
|
||||
- How has overall usage changed over time for my entire image collection?
|
||||
|
||||
To access the report:
|
||||
|
||||
1. Sign in to [Docker Hub](https://hub.docker.com/).
|
||||
2. Select **My Hub** in the top navigation.
|
||||
3. Select your organization in the left navigation.
|
||||
4. Select **Analytics** > **Overview** in the left navigation.
|
||||
5. Download the report by doing one of the following:
|
||||
- Select **Download Weekly Summary**.
|
||||
- Select the **Download Monthly Summary**.
|
||||
- Expand the **Summary reports for the year** drop-down and then select
|
||||
**Download report** for the desired week or month.
|
||||
|
||||
The summary report is a CSV file that contains the following data points:
|
||||
|
||||
| Field | Description |
|
||||
|-------|-------------|
|
||||
| `DATE_GRANULARITY` | Weekly or monthly granularity of the data. Indicates whether the data is aggregated by week or month. |
|
||||
| `DATE_REFERENCE` | The start date of the week or month in YYYY-MM-DD format (e.g., `2025-09-29` for the week starting September 29, 2025). |
|
||||
| `PUBLISHER_NAME` | The name of the Docker organization that owns the repository (e.g., `demonstrationorg`). |
|
||||
| `LEVEL` | The aggregation level of the data - either `repository` (summary for entire repository), `tag` (summary for specific tag), or `digest` (summary for specific digest). |
|
||||
| `REFERENCE` | The specific reference being summarized - the repository name, tag name, or digest hash depending on the level. |
|
||||
| `DATA_DOWNLOADS` | The number of actual image downloads. |
|
||||
| `VERSION_CHECKS` | The number of version checks performed (HEAD requests to check for updates without downloading the full image). |
|
||||
| `EVENT_COUNT` | The total number of events, calculated as the sum of data downloads and version checks. |
|
||||
|
||||
### Trends report
|
||||
|
||||
The trends report helps you understand how adoption of your container images
|
||||
evolves over time. It provides visibility into pull activity across repositories
|
||||
and tags, enabling you to identify adoption patterns, version migration trends,
|
||||
and usage environments (e.g., local development, CI/CD, production).
|
||||
|
||||
You can use this report to answer questions like:
|
||||
|
||||
- Which versions are gaining or losing traction?
|
||||
- Is a new release being adopted?
|
||||
- How does usage vary across cloud providers?
|
||||
|
||||
To access the report:
|
||||
|
||||
1. Sign in to [Docker Hub](https://hub.docker.com/).
|
||||
2. Select **My Hub** in the top navigation.
|
||||
3. Select your organization in the left navigation.
|
||||
4. Select **Analytics** > **Trends** in the left navigation.
|
||||
5. Select **DATA BY WEEK** or **DATA BY MONTH** to choose the data granularity.
|
||||
6. Select **Download report** for the desired week or month.
|
||||
|
||||
The trends report is a CSV file that contains the following data points:
|
||||
|
||||
| Field | Description |
|
||||
|-------|-------------|
|
||||
| `DATE_GRANULARITY` | Weekly or monthly granularity of the data. |
|
||||
| `DATE_REFERENCE` | The start date of the week or month. |
|
||||
| `PUBLISHER_NAME` | The name of the organization that owns the repository. |
|
||||
| `IMAGE_REPOSITORY` | The full name of the image repository (e.g., `demonstrationorg/scout-demo`). |
|
||||
| `NAMESPACE` | The Docker organization or namespace that owns the repository. |
|
||||
| `IP_COUNTRY` | The country code (ISO 3166-1 alpha-2) where the pull request originated from (e.g., `US`, `CA`). |
|
||||
| `CLOUD_SERVICE_PROVIDER` | The cloud service provider used for the pull request (e.g., `gcp`, `aws`, `azure`) or `no csp` for non-cloud providers. |
|
||||
| `USER_AGENT` | The client application or tool used to pull the image (e.g., `docker`, `docker-scout`, `node-fetch`, `regclient`). |
|
||||
| `TAG` | The specific image tag that was pulled, or `\\N` if no specific tag was used. |
|
||||
| `DATA_DOWNLOADS` | The number of data downloads for the specified criteria. |
|
||||
| `VERSION_CHECKS` | The number of version checks (HEAD requests) performed without downloading the full image. |
|
||||
| `PULLS` | The total number of pull requests (data downloads + version checks). |
|
||||
| `UNIQUE_AUTHENTICATED_USERS` | The number of unique authenticated users who performed pulls. |
|
||||
| `UNIQUE_UNAUTHENTICATED_USERS` | The number of unique unauthenticated users who performed pulls. |
|
||||
|
||||
### Technographic report
|
||||
|
||||
The technographic report provides insights into how your Docker Verified
|
||||
Publisher (DVP) images are used alongside other container images in real-world
|
||||
technology stacks. This report helps you understand the technical ecosystem
|
||||
where your images operate and identify co-usage patterns with other images.
|
||||
|
||||
You can use this report to answer questions like:
|
||||
|
||||
- Which other images are commonly used together with your images?
|
||||
- What percentage of your user base also uses specific complementary
|
||||
technologies?
|
||||
- How many companies in your ecosystem use both your image and other popular
|
||||
images?
|
||||
- What technology stacks are most popular among your users?
|
||||
|
||||
To access the report:
|
||||
|
||||
1. Sign in to [Docker Hub](https://hub.docker.com/).
|
||||
2. Select **My Hub** in the top navigation.
|
||||
3. Select your organization in the left navigation.
|
||||
4. Select **Analytics** > **Technographic** in the left navigation.
|
||||
5. Select **DATA BY WEEK** or **DATA BY MONTH** to choose the data granularity.
|
||||
6. Select **Download report** for the desired week or month.
|
||||
|
||||
The technographic report is a CSV file that contains the following data points:
|
||||
|
||||
| Field | Description |
|
||||
|-------|-------------|
|
||||
| `DATE_GRANULARITY` | Weekly or monthly granularity of the data. |
|
||||
| `DATE_REFERENCE` | The start date of the week or month in YYYY-MM-DD format. |
|
||||
| `PUBLISHER_ID` | The unique identifier for the publisher organization. |
|
||||
| `PUBLISHER_NAME` | The name of the organization that owns the DVP repository. |
|
||||
| `DVPP_IMAGE` | Your Docker Verified Publisher image repository name. |
|
||||
| `PAIRED_IMAGE` | The other image repository that is commonly used together with your DVP image. |
|
||||
| `USERS` | The number of unique users who pulled both your DVP image and the paired image within the time period. |
|
||||
| `TOTAL_PULLERS` | The total number of unique users who pulled your DVP image during the time period. |
|
||||
| `PCT_USERS` | The percentage of your image's users who also use the paired image (users/total_pullers). |
|
||||
| `DOMAINS` | The number of unique company domains that pulled both your DVP image and the paired image. |
|
||||
| `TOTAL_DOMAINS` | The total number of unique company domains that pulled your DVP image. |
|
||||
| `PCT_DOMAINS` | The percentage of company domains using your image that also use the paired image (domains/total_domains). |
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
> To protect user privacy and ensure statistical significance, the technographic
|
||||
> report only includes image pairings that have at least 10 unique users.
|
||||
> Personal, disposable, and university email domains are excluded from the
|
||||
> company domain analysis.
|
||||
|
||||
### Technographic companies report
|
||||
|
||||
The technographic companies report provides a detailed view of which specific
|
||||
companies (identified by their domains) are using your Docker Verified Publisher
|
||||
(DVP) images together with other container images. This report gives you
|
||||
visibility into the actual organizations adopting your technology stack
|
||||
combinations, enabling targeted business development and partnership
|
||||
opportunities.
|
||||
|
||||
You can use this report to answer questions like:
|
||||
|
||||
- Which companies are using my image alongside specific complementary
|
||||
technologies?
|
||||
- What technology stacks are adopted by enterprise customers in my target
|
||||
market?
|
||||
- Which organizations might be good candidates for partnership discussions?
|
||||
- How can I identify potential customers who are already using related
|
||||
technologies?
|
||||
|
||||
To access the report:
|
||||
|
||||
1. Sign in to [Docker Hub](https://hub.docker.com/).
|
||||
2. Select **My Hub** in the top navigation.
|
||||
3. Select your organization in the left navigation.
|
||||
4. Select **Analytics** > **Technographic** in the left navigation.
|
||||
5. Select **DATA BY WEEK** or **DATA BY MONTH** to choose the data granularity.
|
||||
6. Select **Download report** for the desired week or month.
|
||||
|
||||
The technographic companies report is a CSV file that contains the following
|
||||
data points:
|
||||
|
||||
| Field | Description |
|
||||
|-------|-------------|
|
||||
| `DATE_GRANULARITY` | Weekly or monthly granularity of the data. |
|
||||
| `DATE_REFERENCE` | The start date of the week or month in YYYY-MM-DD format. |
|
||||
| `PUBLISHER_NAME` | The name of the organization that owns the DVP repository. |
|
||||
| `DOMAIN` | The company domain that pulled both your DVP image and the paired image (e.g., `example.com`). |
|
||||
| `DVPP_IMAGE` | Your Docker Verified Publisher image repository name. |
|
||||
| `PAIRED_IMAGE` | The other image repository that was used together with your DVP image by this company. |
|
||||
|
||||
Each row represents a unique combination of a company domain, your DVP image,
|
||||
and another image that were used together during the specified time period.
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
> To protect privacy and ensure data quality, this report excludes personal
|
||||
> email domains, disposable email services, and university domains. Only
|
||||
> business and organizational domains are included in the analysis.
|
||||
|
||||
### Tracked companies report
|
||||
|
||||
The tracked companies report provides detailed insights into how specific
|
||||
companies are using your Docker Verified Publisher (DVP) images. This report
|
||||
helps you understand usage patterns, deployment environments, and adoption
|
||||
trends across your customer base and potential prospects.
|
||||
|
||||
You can use this report to answer questions like:
|
||||
|
||||
- How are specific companies using my images across different environments?
|
||||
- What deployment patterns do I see across local development, CI/CD, and
|
||||
production?
|
||||
- Which companies are heavy users of my images?
|
||||
- How does usage vary by geography and cloud providers for tracked companies?
|
||||
|
||||
To access the report:
|
||||
|
||||
1. Sign in to [Docker Hub](https://hub.docker.com/).
|
||||
2. Select **My Hub** in the top navigation.
|
||||
3. Select your organization in the left navigation.
|
||||
4. Select **Analytics** > **Tracked Companies** in the left navigation.
|
||||
5. Select **DATA BY WEEK** or **DATA BY MONTH** to choose the data granularity.
|
||||
6. Select **Download report** for the desired week or month.
|
||||
|
||||
The tracked companies report is a CSV file that contains the following data
|
||||
points:
|
||||
|
||||
| Field | Description |
|
||||
|-------|-------------|
|
||||
| `DATE_GRANULARITY` | Weekly or monthly granularity of the data. |
|
||||
| `DATE_REFERENCE` | The start date of the week or month in YYYY-MM-DD format. |
|
||||
| `PUBLISHER_NAME` | The name of the organization that owns the DVP repository. |
|
||||
| `DOMAIN` | The company domain (e.g., `docker.com`) associated with the image pulls. |
|
||||
| `IP_COUNTRY` | The country code (ISO 3166-1 alpha-2) where the pull request originated from. |
|
||||
| `CLOUD_SERVICE_PROVIDER` | The cloud service provider used for the pull request or `no csp` for non-cloud providers. |
|
||||
| `USER_AGENT` | The client application or tool used to pull the image. |
|
||||
| `INFERRED_USE_CASE` | The inferred deployment environment based on user agent and cloud provider analysis. Values include: <br>• `Local Dev`: Local development environment (e.g., Docker Desktop, direct `docker` commands) <br>• `CI/CD`: Continuous integration/deployment pipelines (e.g., containerd, build tools, registry mirroring) <br>• `Prod`: Production environments (e.g., Kubernetes, container orchestration platforms) <br>• `Unknown`: Unable to determine the use case from available data |
|
||||
| `IMAGE_REPOSITORY` | The specific DVP image repository that was pulled. |
|
||||
| `DATA_DOWNLOADS` | The number of actual image layer downloads for this combination. |
|
||||
| `VERSION_CHECKS` | The number of version checks (HEAD requests) performed without downloading the full image. |
|
||||
| `PULLS` | The total number of pull requests (data downloads + version checks). |
|
||||
| `UNIQUE_AUTHENTICATED_USERS` | The number of unique authenticated users from this domain who performed pulls. |
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
> Use case inference is determined by analyzing user agent patterns and cloud
|
||||
> service provider usage. Local development tools used on cloud infrastructure
|
||||
> are reclassified as CI/CD, and CI/CD tools used on cloud infrastructure are
|
||||
> reclassified as production to better reflect actual deployment patterns.
|
||||
|
||||
{{< /tab >}}
|
||||
{{< tab name="DSOS & Legacy DVP programs" >}}
|
||||
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> The Legacy DVP program applies to existing customers who have not yet renewed
|
||||
> to DVP Core. The DVP Legacy program is deprecated and will be retired. Contact
|
||||
> your Docker sales representative or
|
||||
> [Docker](https://www.docker.com/partners/programs/) for more information.
|
||||
|
||||
## View the image's analytics data
|
||||
|
||||
You can find analytics data for your repositories on the **Insights and
|
||||
analytics** dashboard at the following URL:
|
||||
`https://hub.docker.com/orgs/{namespace}/insights/images`. The dashboard contains a
|
||||
visualization of the usage data and a table where you can download
|
||||
`https://hub.docker.com/orgs/{namespace}/insights/images`. The dashboard
|
||||
contains a visualization of the usage data and a table where you can download
|
||||
the data as CSV files.
|
||||
|
||||
To view data in the chart:
|
||||
@@ -34,7 +301,6 @@ To view data in the chart:
|
||||
|
||||
|
||||
|
||||
<!-- prettier-ignore -->
|
||||
> [!TIP]
|
||||
>
|
||||
> Hovering your cursor over the chart displays a tooltip, showing precise data
|
||||
@@ -42,8 +308,9 @@ To view data in the chart:
|
||||
|
||||
### Share analytics data
|
||||
|
||||
You can share the visualization with others using the **Share** icon above the chart.
|
||||
This is a convenient way to share statistics with others in your organization.
|
||||
You can share the visualization with others using the **Share** icon at the top
|
||||
of the chart. This is a convenient way to share statistics with others in your
|
||||
organization.
|
||||
|
||||
|
||||
|
||||
@@ -54,14 +321,19 @@ configuration as you had set up when creating the link.
|
||||
|
||||
## Extension analytics data
|
||||
|
||||
If you have published Docker Extensions in the Extension marketplace, you can also get analytics about your extension usage, available as CSV files.
|
||||
You can download extension CSV reports from the **Insights and analytics** dashboard at the following URL:
|
||||
`https://hub.docker.com/orgs/{namespace}/insights/extensions`. If your Docker namespace contains extensions known in the marketplace, you will see an **Extensions** tab listing CSV files for your extension(s).
|
||||
If you have published Docker Extensions in the Extension marketplace, you can
|
||||
also get analytics about your extension usage, available as CSV files. You can
|
||||
download extension CSV reports from the **Insights and analytics** dashboard at
|
||||
the following URL:
|
||||
`https://hub.docker.com/orgs/{namespace}/insights/extensions`. If your Docker
|
||||
namespace contains extensions known in the marketplace, you will see an
|
||||
**Extensions** tab listing CSV files for your extension(s).
|
||||
|
||||
## Exporting analytics data
|
||||
|
||||
You can export the analytics data either from the web dashboard, or using the
|
||||
[DVP Data API](/reference/api/dvp/latest.md). All members of an organization have access to the analytics data.
|
||||
[DVP Data API](/reference/api/dvp/latest.md). All members of an organization
|
||||
have access to the analytics data.
|
||||
|
||||
The data is available as a downloadable CSV file, in a weekly (Monday through
|
||||
Sunday) or monthly format. Monthly data is available from the first day of the
|
||||
@@ -70,14 +342,13 @@ can analyze it manually as a spreadsheet.
|
||||
|
||||
### Export data
|
||||
|
||||
Export usage data for your organization's images using the Docker Hub website by following these steps:
|
||||
Export usage data for your organization's images using the Docker Hub website by
|
||||
following these steps:
|
||||
|
||||
1. Sign in to [Docker Hub](https://hub.docker.com/) and select **My Hub**.
|
||||
|
||||
2. Choose your organization and select **Analytics**.
|
||||
|
||||
|
||||
|
||||
3. Set the time span for which you want to export analytics data.
|
||||
|
||||
The downloadable CSV files for summary and raw data appear on the right-hand
|
||||
@@ -183,7 +454,8 @@ pulls. To provide feedback or ask questions about these rules,
|
||||
|
||||
There are two levels of extension summary data available:
|
||||
|
||||
- Core summary, with basic extension usage information: number of extension installs, uninstalls, and total install all times
|
||||
- Core summary, with basic extension usage information: number of extension
|
||||
installs, uninstalls, and total install all times
|
||||
|
||||
The core-summary-data file contains the following data points for the selected time
|
||||
span:
|
||||
@@ -196,7 +468,8 @@ span:
|
||||
| TotalUninstalls | Number of uninstalls for the extension all times | Feb 1, 2024 |
|
||||
| Updates | Number of updates for the extension | Feb 1, 2024 |
|
||||
|
||||
- Premium summary, with advanced extension usage information: installs, uninstalls by unique users, extension opening by unique users.
|
||||
- Premium summary, with advanced extension usage information: installs,
|
||||
uninstalls by unique users, extension opening by unique users.
|
||||
|
||||
The core-summary-data file contains the following data points for the selected time
|
||||
span:
|
||||
@@ -222,12 +495,14 @@ from the date of when the field was first introduced, and going forward.
|
||||
Refer to the tables in the [Data points](#data-points) section to see from which
|
||||
date a given data point is available.
|
||||
|
||||
{{< /tab >}}
|
||||
{{< /tabs >}}
|
||||
|
||||
## Privacy
|
||||
|
||||
This section contains information about privacy-protecting measures that ensures
|
||||
consumers of content on Docker Hub remain completely anonymous.
|
||||
|
||||
<!-- prettier-ignore -->
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Docker never shares any Personally Identifiable Information (PII) as part of
|
||||
@@ -237,10 +512,10 @@ The image pulls summary dataset includes unique IP address count. This data poin
|
||||
includes the number of distinct unique IP addresses that request an image.
|
||||
Individual IP addresses are never shared.
|
||||
|
||||
The image pulls raw dataset includes user IP domains as a data point. This is the domain name
|
||||
associated with the IP address used to pull an image. If the IP type is
|
||||
`business`, the domain represents the company or organization associated with
|
||||
that IP address (for example, `docker.com`). For any other IP type that's not
|
||||
`business`, the domain represents the internet service provider or hosting
|
||||
The image pulls raw dataset includes user IP domains as a data point. This is
|
||||
the domain name associated with the IP address used to pull an image. If the IP
|
||||
type is `business`, the domain represents the company or organization associated
|
||||
with that IP address (for example, `docker.com`). For any other IP type that's
|
||||
not `business`, the domain represents the internet service provider or hosting
|
||||
provider used to make the request. On average, only about 30% of all pulls
|
||||
classify as the `business` IP type (this varies between publishers and images).
|
||||
classify as the `business` IP type (this varies between publishers and images).
|
||||
@@ -39,6 +39,7 @@ These permissions apply organization-wide, including all repositories in your or
|
||||
| Pull images | ✅ | ✅ | ✅ |
|
||||
| Create and publish an extension | ✅ | ✅ | ✅ |
|
||||
| Become a Verified, Official, or Open Source publisher | ❌ | ❌ | ✅ |
|
||||
| Edit and delete publisher repository logos | ❌ | ✅ | ✅ |
|
||||
| Observe content engagement as a publisher | ❌ | ❌ | ✅ |
|
||||
| Create public and private repositories | ❌ | ✅ | ✅ |
|
||||
| Edit and delete repositories | ❌ | ✅ | ✅ |
|
||||
|
||||
@@ -6,7 +6,7 @@ info:
|
||||
url: https://docs.docker.com/assets/images/logo-docker-main.png
|
||||
href: /reference
|
||||
description: |
|
||||
The Docker DVP Data API allows [Docker Verified Publishers](https://docs.docker.com/docker-hub/publish/) to view image pull analytics data for their namespaces. Analytics data can be retrieved as raw data, or in a summary format.
|
||||
The Docker DVP Data API allows [Docker Verified Publishers](https://docs.docker.com/docker-hub/publish/) to view image pull analytics data for their namespaces. Analytics data can be retrieved in a CSV as raw data, or in a summary format.
|
||||
|
||||
#### Summary data
|
||||
|
||||
|
||||
Reference in New Issue
Block a user