> 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/principais-funcionalidades/monitoramento-de-notebooks.md).

# Notebook Monitoring

How Power Monitor tracks runs of Microsoft Fabric notebooks, data pipelines and Copy jobs.

Microsoft Fabric notebooks, data pipelines and Copy jobs often support critical processing chains. Power Monitor tracks the runs of these items and notifies you when one of them **fails or is cancelled**, without you having to check each item in Fabric.

## What is monitored

| Item               | What is tracked           | Alert                                            |
| ------------------ | ------------------------- | ------------------------------------------------ |
| **Notebooks**      | Runs, status and duration | **Fabric Item Failed** (failure or cancellation) |
| **Data pipelines** | Runs, status and duration | **Fabric Item Failed**                           |
| **Copy jobs**      | Runs, status and duration | **Fabric Item Failed**                           |
| **Dataflows Gen2** | Runs, status and duration | **Fabric Item Failed**                           |

* Runs are collected **every 2 hours**, in the monitored workspaces.
* **Duration** can be tracked in **Performance › Average Execution Time**, and the **Execution Duration Deviation** alert can be turned on item by item to notify you when a run takes much longer than the average.

{% hint style="info" %}
Currently, Power Monitor does not detect stuck or timed-out runs: a run in progress is simply recorded as such. Runs of **Spark job definitions** are not monitored (the item appears only in the inventory).
{% endhint %}

## Where to track it

* **Monitoring › Fabric Items** and **Dashboards › Artifact Refreshes:** runs and failures.
* **Performance › Average Execution Time:** average duration and deviations.
* **Governance › Data and Engineering › Data Engineering:** inventory of notebooks, pipelines, Spark job definitions, environments and other items.
* **Governance › Operations › Schedules:** schedules of Fabric items.

## Notebook or pipeline: which one to monitor?

Both. In Fabric environments, notebooks are often orchestrated by pipelines. Tracking both shows the failure of the orchestration as well as that of the individual processing step.

{% hint style="info" %}
Monitoring of Fabric items depends on the Power Monitor application being able to read the runs in the monitored workspaces (Fabric tenant settings enabled).
{% endhint %}

## Related pages

* [Microsoft Fabric Items](/en/power-monitor/monitoramento/itens-do-microsoft-fabric.md)
* [Data Engineering](/en/power-monitor/governanca/dados-e-engenharia/engenharia-de-dados.md)
* [Data Refresh Failures](/en/principais-funcionalidades/falhas-de-atualizacao.md)


---

# 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/principais-funcionalidades/monitoramento-de-notebooks.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.