> For the complete documentation index, see [llms.txt](https://help.sbtinstruments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sbtinstruments.com/software/file-formats/device-data-bundle-ddb.md).

# Device data bundle (DDB)

ZIP archive that contains everything from system logs to measurement files

💾 Typical file size **10–100 MiB**

💽 Media type `application/zip`

The device data bundle allows our support team to peek into everything from system logs to raw measurement files. It allows us to help you better and faster!

{% hint style="success" %}

## Create a support case in Access

A support case from Access can include a device data bundle when you check that option. See [Contact support](/troubleshooting/contact-support.md).

You rarely need to handle the device data bundle yourself.
{% endhint %}

{% hint style="danger" %}

### Only for our support team

The structure and content of the DDB may change without any notice. Don't rely on the DDB for measurement data or the like.
{% endhint %}

Wondering what we can actually see when you share a bundle? See [What data is shared with SBT](/software/miscellaneous/what-data-is-shared-with-sbt.md).

## File name

Usually, the file name is something like `bb2241039-2026-01-09.zip` that includes both the ID if your device (`bb2241039`) and the current date (`2026-01-09`).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sbtinstruments.com/software/file-formats/device-data-bundle-ddb.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.