Re-add page

ee/dtr/admin/configure/auto-delete-repo-events.md

@@ -0,0 +1,48 @@
+
+---
+title: Enable Auto-Deletion of Repository Events
+description: Enable auto-deletion of image events within a repository for maintenance.
+keywords: registry, events, log, activity stream
+---
+
+> BETA DISCLAIMER
+>
+> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
+
+## Overview 
+
+Auto-deletion of repository events is a Docker Trusted Registry (DTR) global setting which allows event records to be removed as part of [garbage collection](../admin/configure/garbage-collection.md). As a DTR administrator, you can enable auto-deletion of repository events in DTR 2.6 based on your specified conditions. 
+
+## Steps
+
+1. In your browser, navigate to `https://<dtr-url>` and log in with your UCP credentials. 
+
+2. Select **System** on the left navigation pane which will display the **Settings** page by default.
+
+3. Scroll down to ***Repository Events*** and turn on **Auto-Deletion**.
+
+![](../images/auto-delete-repo-events-0.png){: .img-fluid .with-border}
+
+4. Specify the conditions with which an event deletion will be triggered.
+
+![](../images/auto-delete-repo-events-1.png){: .img-fluid .with-border}
+
+DTR allows you to set your deletion triggers based on the following optional event attributes:
+
+| Name            | Description                                        | Example           |
+|:----------------|:---------------------------------------------------| :----------------|
+| Age        | Lets you remove events older than your specified number of  hours, days, weeks or months| `2 months` |
+| Max number of events  | Lets you specify the maximum number of events allowed in the repositories.  | Component name starts with `b` |
+
+If you specify both, events in your repositories will be evaluated against both conditions. You should see a "settings saved successfully" confirmation right away.
+
+5. Click **Start GC** if you're ready. Read more about [garbage collection](../admin/configure/garbage-collection/#under-the-hood) if you're unsure about this operation.
+
+6. Navigate to **System > Job Logs** to confirm that `onlinegc` has happened.
+
+![](../images/auto-delete-repo-events-1.png){: .img-fluid .with-border}
+
+## Where to go next
+
+- [Manage job logs](../admin/configure/manage-job-logs.md)
+