> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/datalogz-architecture.md).

# Datalogz Architecture

<figure><img src="https://1435452537-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI51V8nP3ZjMKt2bCO9HR%2Fuploads%2FACG4dZkDe9GWuEGVRWIg%2FScreenshot%202025-08-19%20at%2011.15.03.png?alt=media&amp;token=9b1668e4-0517-44b8-887c-2da9672a8ece" alt=""><figcaption></figcaption></figure>

Datalogz connects to BI tools exclusively via their authenticated REST APIs, ensuring secure and controlled access. The key points are:

* **Read-Only Metadata Access:**\
  We only retrieve metadata—such as report configurations, usage statistics, and asset lineage—without accessing any underlying report data or user content. This guarantees data privacy and limits access scope.
* **Authenticated API Calls:**\
  All API requests use credentials provisioned and managed securely through service principals or managed identities, ensuring only authorized access to metadata endpoints.
* **Encryption in Transit:**\
  All communication between Datalogz and BI tools occurs over secure HTTPS connections, protecting metadata from interception or tampering during transmission.
* **Metadata Storage Location:**\
  All metadata collected from BI tools is securely stored within a dedicated Datalogz AWS account to ensure isolation and control.


---

# 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://docs.datalogz.io/guides/datalogz-architecture.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.