---
title: "New field: Cache hit / miss data added to client log exports"
description: "We have added the edge_response field to our automated S3 and Azure client log exports."
canonical_url: "https://cloudsmith.com/changelog/new-field-cache-hit-miss-data-added-to-client-log-exports"
last_updated: "2026-02-09T17:11:47.933Z"
---
# New field: Cache hit / miss data added to client log exports

We have added the `edge_response` field to our automated **S3 and Azure client log exports**. This brings our automated exports into parity with the Cloudsmith UI and manual CSV downloads, giving you deeper visibility into your package delivery performance.

For teams managing high-traffic repositories or optimizing CI/CD pipelines, understanding cache performance is vital. This update ensures your external logging and observability tools have the same level of granularity as the Cloudsmith web app.

### The details

- **Field Name:** `edge_response`
- **Possible Values:** `Hit` or `Miss`
- **Description:** Identifies whether a package was served from an existing cache (`Hit`) or required a cold load (`Miss`).

### Format & compatibility

- **JSON Exports:** This field is now live and included in the JSON payload. As a standard JSON addition, this is a non-breaking change for downstream consumers.
- **CSV Exports:** To prevent breaking existing automated workflows, we are releasing the CSV update separately. We are currently coordinating with customers who utilize our larger CSV delivery format to ensure a smooth transition.

If you have any questions, please [contact us](https://cloudsmith.com/company/contact-us). Learn more about client logs in [our documentation](https://docs.cloudsmith.com/logs-and-observability/client-logs).