---
title: "Trace downloads through connected repositories in client log exports"
description: "A connected_repositories field in client log exports lists the connected repositories a package was served through, so you can trace a download back from the repository that served it."
canonical_url: "https://cloudsmith.com/changelog/trace-downloads-through-connected-repositories-in-client-log-exports"
last_updated: "2026-10-01T14:15:04.034Z"
---
# Trace downloads through connected repositories in client log exports

A `connected_repositories` field in client log exports lists the connected repositories a package was served through, so you can trace a download back from the repository that served it.  


**Example JSON output:**

```json
{
  "_key": "c2e986cd15f0",
  "_type": "code",
  "code": "{\n  \"repository\": \"acme/source\",\n  \"uri\": \"/packages/example.tar.gz\",\n  \"connected_repositories\": [\n    \"acme/target\",\n    \"other/shared\"\n  ]\n}",
  "filename": null,
  "language": null,
  "markDefs": null
}
```

`repository` is the source repository the package lives in; `connected_repositories` lists the connected repositories it was served through.



**Example CSV output:**

```json
{
  "_key": "547bef7392a6",
  "_type": "code",
  "code": "repository,uri,connected_repositories\nacme/source,/packages/example.tar.gz,acme/target;other/shared",
  "filename": null,
  "language": null,
  "markDefs": null
}
```

CSV separates multiple values with semicolons.



If no connected repositories were involved, the field is an empty array in JSON and an empty value in CSV.



The `connected_repositories` field is disabled by default. If you already receive log exports and use connected repositories, [contact support](/company/contact-us) to have this field added to your exports.



Log exports are available on Ultra and Enterprise plans.