mirror of https://github.com/docker/docs.git
Fixing what's broken
This commit is contained in:
Maria Bermudez
parent
b2ec8ba7d9
commit
f778e75d51
|
|
@ -124,7 +124,7 @@ guides:
|
|||
- path: /toolbox/faqs/troubleshoot/
|
||||
title: Troubleshooting
|
||||
- title: Release notes
|
||||
path: /release-notes/docker-ce/
|
||||
path: /engine/release-notes/
|
||||
nosync: true
|
||||
- sectiontitle: Docker EE
|
||||
section:
|
||||
|
|
@ -145,7 +145,7 @@ guides:
|
|||
- path: /install/windows/docker-ee/
|
||||
title: Microsoft Windows Server
|
||||
- title: Release notes
|
||||
path: /ee/engine/release-notes/
|
||||
path: /engine/release-notes/
|
||||
nosync: true
|
||||
- sectiontitle: Compatibility between Docker versions
|
||||
section:
|
||||
|
|
@ -1529,7 +1529,7 @@ manuals:
|
|||
title: Install Docker EE Engine
|
||||
nosync: true
|
||||
- title: Release notes
|
||||
path: /ee/engine/release-notes/
|
||||
path: /engine/release-notes/
|
||||
- sectiontitle: Universal Control Plane
|
||||
section:
|
||||
- path: /ee/ucp/
|
||||
|
|
@ -3945,11 +3945,9 @@ manuals:
|
|||
section:
|
||||
- path: /release-notes/
|
||||
title: Overview
|
||||
- path: /ee/engine/release-notes/
|
||||
title: Docker EE
|
||||
- path: /engine/release-notes/
|
||||
title: Docker EE and CE
|
||||
nosync: true
|
||||
- path: /release-notes/docker-ce/
|
||||
title: Docker CE
|
||||
- path: /cs-engine/1.13/release-notes/
|
||||
title: CS Docker Engine
|
||||
nosync: true
|
||||
|
|
|
|||
|
|
@ -0,0 +1,61 @@
|
|||
---
|
||||
title: Audit Repository Events
|
||||
description: View and audit your repository events.
|
||||
keywords: dtr, events, log, activity stream
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Starting in DTR 2.6, each repository page includes an **Activity** tab which displays a sortable and paginated list of the most recent events within the repository. This offers better visibility along with the ability to audit events. Event types listed will vary according to your [repository permission level](../../admin/manage-users/permission-levels/). Additionally, DTR admins can [enable auto-deletion of repository events](../../admin/configure/auto-delete-repo-events/) as part of maintenance and cleanup.
|
||||
|
||||
In the following section, we will show you how to view and audit the list of events in a repository. We will also cover the event types associated with your permission level.
|
||||
|
||||
## View List of Events
|
||||
|
||||
As of DTR 2.3, admins were able to view a list of DTR events [using the API](../../../../datacenter/dtr/2.3/reference/api/#!/events/GetEvents). DTR 2.6 enhances that feature by showing a permission-based events list for each repository page on the web interface. To view the list of events within a repository, do the following:
|
||||
1. Navigate to `https://<dtr-url>`and log in with your UCP credentials.
|
||||
|
||||
2. Select **Repositories** on the left navigation pane, and then click on the name of the repository that you want to view. Note that you will have to click on the repository name following the `/` after the specific namespace for your repository.
|
||||
|
||||
3. Select the **Activity** tab. You should see a paginated list of the latest events based on your repository permission level. By default, **Activity** shows the latest `10` events and excludes pull events, which are only visible to repository and DTR admins.
|
||||
* If you're a repository or a DTR admin, uncheck "Exclude pull" to view pull events. This should give you a better understanding of who is consuming your images.
|
||||
* To update your event view, select a different time filter from the drop-down list.
|
||||
|
||||
{: .img-fluid .with-border}
|
||||
|
||||
|
||||
### Activity Stream
|
||||
|
||||
The following table breaks down the data included in an event and uses the highlighted "Create Promotion Policy" event as an example.
|
||||
|
||||
| Event Detail | Description | Example |
|
||||
|:----------------|:-------------------------------------------------|:--------|
|
||||
| Label | Friendly name of the event. | `Create Promotion Policy`
|
||||
| Repository | This will always be the repository in review following the `<user-or-org>/<repository_name>` convention outlined in [Create a Repository](../manage-images/#create-a-repository). | `test-org/test-repo-1` |
|
||||
| Tag | Tag affected by the event, when applicable. | `test-org/test-repo-1:latest` where `latest` is the affected tag|
|
||||
| SHA | The [digest value](../../../../registry/spec/api/#content-digests) for `CREATE` operations such as creating a new image tag or a promotion policy. | `sha256:bbf09ba3` |
|
||||
| Type | Event type. Possible values are: `CREATE`, `GET`, `UPDATE`, `DELETE`, `SEND`, `FAIL` and `SCAN` | `CREATE` |
|
||||
| Initiated by | The actor responsible for the event. For user-initiated events, this will reflect the user ID and link to that user's profile. For image events triggered by a policy – pruning, pull / push mirroring, or promotion – this will reflect the relevant policy ID except for manual promotions where it reflects `PROMOTION MANUAL_P`, and link to the relevant policy page. Other event actors may not include a link. | `PROMOTION CA5E7822` |
|
||||
| Date and Time | When the event happened in your configured time zone. | `9/13/2018 9:59 PM` |
|
||||
|
||||
### Event Audits
|
||||
|
||||
Given the level of detail on each event, it should be easy for DTR and security admins to determine what events have taken place inside of DTR. For example, when an image which shouldn’t have been deleted ends up getting deleted, the security admin can determine when and who initiated the deletion.
|
||||
|
||||
### Event Permissions
|
||||
|
||||
For more details on different permission levels within DTR, see [Authentication and authorization in DTR](../../admin/manage-users/) to understand the minimum level required to view the different repository events.
|
||||
|
||||
| Repository Event | Description | Minimum Permission Level |
|
||||
|:----------------|:---------------------------------------------------| :----------------|
|
||||
| Push | Refers to "Create Manifest" and "Update Tag" events. Learn more about [pushing images](../manage-images/pull-and-push-images/#push-the-image). | Authenticated Users |
|
||||
| Scan | Requires [security scanning to be set up](../../admin/configure/set-up-vulnerability-scans/) by a DTR admin. Once enabled, this will display as a `SCAN` event type. | Authenticated Users |
|
||||
| Promotion | Refers to a "Create Promotion Policy" event which links to the **Promotions** tab of the repository where you can edit the existing promotions. See [Promotion Policies](../promotion-policies/) for different ways to promote an image. | Repository Admin |
|
||||
| Delete | Refers to "Delete Tag" events. Learn more about [deleting images](../manage-images/delete-images). | Authenticated Users |
|
||||
| Pull | Refers to "Get Tag" events. Learn more about [pulling images](../manage-images/pull-and-push-images/#pull-an-image). | Repository Admin |
|
||||
| Mirror |Refers to "Pull mirroring" and "Push mirroring" events. See [Mirror images to another registry](../promotion-policies/#mirror-images-to-another-registry) and [Mirror images from another registry](../promotion-policies/#mirror-images-from-another-registry) for more details. | Repository Admin |
|
||||
| Create repo | Refers to "Create Repository" events. See [Create a repository](../manage-images/) for more details. | Authenticated Users |
|
||||
|
||||
## Where to go next
|
||||
|
||||
- [Enable auto-deletion of repository events](../../admin/configure/auto-delete-repo-events.md)
|
||||
|
|
@ -6,9 +6,9 @@ title: Docker Release Notes
|
|||
|
||||
Find out what's new in Docker products!
|
||||
|
||||
- [Docker Enterprise and Community Engine] (/engine/release-notes)
|
||||
- [Docker Trusted Registry] (/ee/dtr/release-notes/)
|
||||
- [Docker Universal Control Plane] (/ee/ucp/release-notes/)
|
||||
- [Docker Enterprise and Community Engine](/engine/release-notes)
|
||||
- [Docker Trusted Registry](/ee/dtr/release-notes/)
|
||||
- [Docker Universal Control Plane](/ee/ucp/release-notes/)
|
||||
- [Docker for Mac](/docker-for-mac/release-notes.md) ([Edge Releases](/docker-for-mac/edge-release-notes.md))
|
||||
- [Docker for Windows](/docker-for-windows/release-notes.md) ([Edge Releases](/docker-for-windows/edge-release-notes.md))
|
||||
- [Docker for Azure](/docker-for-azure/release-notes.md) or [Docker for AWS](/docker-for-aws/release-notes.md)
|
||||
|
|
|
|||
Loading…
Reference in New Issue