From bbebeaed2eb27956d32330f04371b9a747270d49 Mon Sep 17 00:00:00 2001 From: Jim Galasyn Date: Tue, 9 Jan 2018 09:52:14 -0800 Subject: [PATCH] Port DTR monitor topics to template (#403) --- .../admin/monitor-and-troubleshoot/index.md | 12 +++++++++--- .../monitor-and-troubleshoot/notary-audit-logs.md | 7 +++++++ .../troubleshoot-batch-jobs.md | 7 +++++++ .../troubleshoot-with-logs.md | 15 +++++++++++---- 4 files changed, 34 insertions(+), 7 deletions(-) diff --git a/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/index.md b/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/index.md index 79b44edac4..e4cdc3fc1a 100644 --- a/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/index.md +++ b/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/index.md @@ -2,8 +2,16 @@ title: Monitor Docker Trusted Registry description: Learn how to monitor your DTR installation. keywords: registry, monitor, troubleshoot +ui_tabs: +- version: dtr-2.5 + orlower: true +next_steps: +- path: troubleshoot-with-logs/ + title: Troubleshoot with logs --- +{% if include.version=="dtr-2.5" %} + Docker Trusted Registry is a Dockerized application. To monitor it, you can use the same tools and techniques you're already using to monitor other containerized applications running on your cluster. One way to monitor @@ -70,6 +78,4 @@ You can find health status on the `current_issues` and `replica_health` arrays. If this endpoint doesn't provide meaningful information when trying to troubleshoot, try [troubleshooting using logs](troubleshoot-with-logs.md). -## Where to go next - -* [Troubleshoot with logs](troubleshoot-with-logs.md) +{% endif %} \ No newline at end of file diff --git a/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/notary-audit-logs.md b/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/notary-audit-logs.md index 44e543f8b5..8d9adde4a5 100644 --- a/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/notary-audit-logs.md +++ b/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/notary-audit-logs.md @@ -3,8 +3,13 @@ title: Check Notary audit logs description: When you push signed images, Docker Trusted Registry keeps audit logs for the changes made to the image metadata. Learn how to view these logs. keywords: registry, monitor, troubleshoot +ui_tabs: +- version: dtr-2.5 + orlower: true --- +{% if include.version=="dtr-2.5" %} + Docker Content Trust (DCT) keeps audit logs of changes made to trusted repositories. Every time you push a signed image to a repository, or delete trust data for a repository, DCT logs that information. @@ -264,3 +269,5 @@ curl --insecure --silent \ --header "Authorization: Bearer $TOKEN" \ "https:///v2///_trust/changefeed?records=10&change_id=0" | jq . ``` + +{% endif %} diff --git a/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/troubleshoot-batch-jobs.md b/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/troubleshoot-batch-jobs.md index f3beb8811e..22406ad942 100644 --- a/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/troubleshoot-batch-jobs.md +++ b/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/troubleshoot-batch-jobs.md @@ -2,8 +2,13 @@ title: Troubleshoot batch jobs description: Learn how Docker Trusted Registry run batch jobs, so that you can troubleshoot when something goes wrong keywords: dtr, troubleshoot +ui_tabs: +- version: dtr-2.5 + orlower: true --- +{% if include.version=="dtr-2.5" %} + DTR uses a job queue to schedule batch jobs. A job is placed on this work queue, and a job runner component of DTR consumes work from this cluster-wide job queue and executes it. @@ -230,3 +235,5 @@ see those jobs using the `GET /api/v0/crons` endpoint: ``` The `schedule` uses a Unix crontab syntax. + +{% endif %} \ No newline at end of file diff --git a/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md b/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md index 731ddd987a..d4b93db1f1 100644 --- a/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md +++ b/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md @@ -2,8 +2,13 @@ title: Troubleshoot Docker Trusted Registry description: Learn how to troubleshoot your DTR installation. keywords: registry, monitor, troubleshoot +ui_tabs: +- version: dtr-2.5 + orlower: true --- +{% if include.version=="dtr-2.5" %} + This guide contains tips and tricks for troubleshooting DTR problems. ## Troubleshoot overlay networks @@ -15,7 +20,7 @@ and see if they can ping one another. Use SSH to log into a UCP node, and run: -```none +```bash docker run -it --rm \ --net dtr-ol --name overlay-test1 \ --entrypoint sh {{ page.dtr_org }}/{{ page.dtr_repo }} @@ -23,7 +28,7 @@ docker run -it --rm \ Then use SSH to log into another UCP node and run: -```none +```bash docker run -it --rm \ --net dtr-ol --name overlay-test2 \ --entrypoint ping {{ page.dtr_org }}/{{ page.dtr_repo }} -c 3 overlay-test1 @@ -119,7 +124,7 @@ Warning: The following replicas are unhealthy: 59e4e9b0a254; Reasons: Replica re To fix this, you should remove the unhealthy replica from the DTR cluster, and join a new one. Start by running: -```none +```bash docker run -it --rm \ {{ page.dtr_org }}/{{ page.dtr_repo }}:{{ page.dtr_version }} remove \ --ucp-insecure-tls @@ -127,9 +132,11 @@ docker run -it --rm \ And then: -```none +```bash docker run -it --rm \ {{ page.dtr_org }}/{{ page.dtr_repo }}:{{ page.dtr_version }} join \ --ucp-node \ --ucp-insecure-tls ``` + +{% endif %} \ No newline at end of file