> For the complete documentation index, see [llms.txt](https://docs.powermonitor.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powermonitor.com.br/en/power-monitor/governanca/dados-e-engenharia.md).

# Data and Engineering

Governance menu group that brings together the inventories of the Microsoft Fabric data artifacts that are neither reports nor storage: mirroring, data engineering, data science, ontologies, developme

The **Data and Engineering** group brings together, in the Governance menu, the inventories of the Microsoft Fabric artifacts that move, transform and process data: mirrored databases, pipelines and notebooks, ML models, variable libraries and real-time items. These are the items that sit "behind" the reports and semantic models.

Use the group to find out what exists in each workspace, who created and who last modified each item, when the items were changed and, depending on the screen, the synchronization state, the schedules and the lineage. All screens in the group are available to all profiles and respect each user's workspace scope and page blocking.

## How to open

1. In the side menu, click **Governance**.
2. Click **Data and Engineering** to expand the group and choose the screen, for example *Governance › Data and Engineering › Data Engineering*.

The group is collapsible: clicking its name only expands or collapses the list, without changing the screen. When the open screen belongs to it, the group is already expanded. On the [Home](/en/power-monitor/pagina-inicial.md) page, each screen in the group has its own shortcut in the Governance section.

## Screens in the group

| Screen                                                                                     | What it shows                                                                                                         |
| ------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- |
| [Fabric Mirroring](/en/power-monitor/governanca/dados-e-engenharia/fabric-mirroring.md)    | Mirrored Databases and the synchronization status of each table, queried live                                         |
| [Data Engineering](/en/power-monitor/governanca/dados-e-engenharia/engenharia-de-dados.md) | Data Pipelines, Dataflows, Copy Jobs, Notebooks, Environments, dbt, Spark Job Definitions and Apache Airflow Jobs     |
| [Data Science](/en/power-monitor/governanca/dados-e-engenharia/ciencia-de-dados.md)        | ML Models, Data Agents, ML Experiments, Ontologies and Graph Models                                                   |
| [Ontologies](/en/power-monitor/governanca/dados-e-engenharia/ontologias.md)                | Structure of the Fabric ontologies and the problems found, with the notice about the retirement of the old experience |
| [Development](/en/power-monitor/governanca/dados-e-engenharia/desenvolvimento.md)          | Variable Libraries, App Backend and User Data Functions                                                               |
| [Real Time](/en/power-monitor/governanca/dados-e-engenharia/tempo-real.md)                 | Reflex (Activator), Eventhouses, Event Subscriptions and KQL Querysets                                                |

## Related pages

* [Governance](/en/power-monitor/governanca.md): overview of the module and of the menu groups
* [Storage](/en/power-monitor/governanca/armazenamento.md): Lakehouses, Warehouses, SQL databases, KQL databases and Event Streams
* [Operations](/en/power-monitor/governanca/operacao.md): schedules, deployment pipelines and deleted artifacts


---

# 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.powermonitor.com.br/en/power-monitor/governanca/dados-e-engenharia.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.