Black Friday50% off your first month on any monthly plan with EARLY50 See plans
All 33 lessons
  1. Start here: cloud and data basics

    1. 1. Start here: the exam, the plan and what you already know
    2. 2. Cloud in plain words: SaaS, PaaS, IaaS and where Fabric fits
    3. 3. Data basics: files, tables, formats and the lakehouse idea
    4. 4. A tour of Microsoft Fabric: OneLake, workspaces and items
    5. 5. The three languages: SQL, PySpark and KQL side by side
    6. 6. Getting data in: the map of Fabric tools
  2. Store, ingest and transform batch data (exam area 2, 30-35%)

    1. 7. Choosing a data store and a transformation tool
    2. 8. Shortcuts and mirroring: use data without copying it
    3. 9. Ingest data with pipelines and Copy job
    4. 10. Transform with PySpark and SQL: join, denormalize, aggregate
    5. 11. Messy data: duplicates, missing values and late arrivals
    6. 12. Full and incremental loads, and loading a star schema
  3. Orchestrate and stream (exam areas 1 and 2)

    1. 13. Pipeline or notebook? Choosing how to orchestrate
    2. 14. Schedules and event-based triggers
    3. 15. Parameters and dynamic expressions
    4. 16. Streaming in Fabric: Eventstreams, Spark streaming and KQL
    5. 17. KQL and windowing functions for real-time data
  4. Set up and secure a Fabric solution (exam area 1, 30-35%)

    1. 18. Workspace settings: Spark, domains, OneLake and data workflows
    2. 19. Version control with Git and database projects
    3. 20. Deployment pipelines: development, test and production
    4. 21. Who can see what: workspace roles and item permissions
    5. 22. Fine-grained security: rows, columns, objects, files and masking
    6. 23. Governance: sensitivity labels and endorsement
  5. Monitor, fix and optimize (exam area 3, 30-35%)

    1. 24. Monitoring hub, alerts and Activator
    2. 25. Fixing errors in pipelines, dataflows and notebooks
    3. 26. Fixing errors in Eventhouse, Eventstream and T-SQL
    4. 27. Optimize lakehouse tables: V-Order, OPTIMIZE, VACUUM and partitions
    5. 28. Optimize Spark, pipelines and warehouses
    6. 29. Optimize eventstreams, eventhouses and queries
  6. Exam practice and final review

    1. 30. Exam day: question types, timing and how to think
    2. 31. Mock exam 1
    3. 32. Mock exam 2
    4. 33. Final review: every decision on one page
See the leaderboard

17 min

Monitoring hub, alerts and Activator

Watch ingestion, transformations and refreshes and get alerted when something breaks.

By the end of this lesson you can

  • Find the status of any pipeline, notebook or dataflow run in the Monitor hub
  • Check a semantic model's refresh history
  • Tell the Capacity Metrics app from workspace monitoring
  • Choose and set up an alert for a failing job

From earlier lessons · 1 of 2

You own a semantic model and have write permission, but you aren't an authorized reviewer. Which badge can you apply yourself?

Pick one answer.

From earlier lessons · 2 of 2

You connect a Notebook labeled General to a Lakehouse labeled Confidential. What happens to the Notebook's label?

Pick one answer.

At 6 a.m. the nightly pipeline that loads Northwind Rides trips failed. The certified trips semantic model then refreshed with yesterday's data. The ops team found out at their 9 a.m. meeting, from a report showing zero rides. Your manager asks two things. Where can you see every run? And why didn't anyone get told?

[4]

The Monitor hub: every run in one list

Exam depth: know it cold.

The Monitor hub is the one place in Fabric that shows runs across all item types. Older docs call it the Monitoring hub. The newest version is in preview.

Select Monitor in the navigation pane, then Job runs. Each row is one item. It shows the Last run status, success rate, average duration and the last five runs.

Narrow the list with filters for Time, Item type, Status and Workspace. Pipelines, notebooks, Dataflow Gen2, semantic models, Copy jobs and Spark job definitions all appear. Dataflow Gen1 doesn't.

Anyone can open it. You see only runs of items you have permission to view.

[220][221]

The Monitor hub Job runs page. Filters for Time, Item type, Status and Workspace sit above a list of items with columns for item type, last run status (Failed, Succeeded, Cancelled), success rate, average duration, run history and workspace.
Microsoft Learn, CC BY 4.0

[220]

Select a row to open its details pane. Run history lists past runs, so you can spot a pattern, like a failure every Monday. Open detail page shows the full run. For pipelines and dataflows that includes each activity in a table or a Gantt chart.

The status tells you the next step:

  • Failed: open the run details and read the error.
  • Queued for a long time: check whether the capacity is busy.
  • Canceled: someone stopped it. Rerun it if the work still matters.

[221]

[221]

Ingestion, transformation and semantic model refresh

Exam depth: know it cold.

Ingestion jobs bring data in, such as pipelines and Copy jobs. Transformation jobs reshape it, such as notebooks and dataflows. All of them land in the Monitor hub. Each item also has its own history view:

  • Pipeline: in the workspace, select ... > View run history.
  • Dataflow Gen2: select Recent runs to open its refresh history. It lists start time, status, duration and type for up to 50 refreshes.
  • Semantic model: open its settings and select Refresh history. A semantic model is the Power BI layer reports read. Its history lists every attempt, because Power BI retries a failed refresh by itself.

A failed semantic model also shows a warning icon in the workspace list.

[224][228][229]

Match

Match each Northwind Rides question to where you'd look first

Pick an item on the left, then its match on the right.

[221][228][229][230]

Capacity Metrics app and workspace monitoring

Exam depth: recognize it.

The Capacity Metrics app is a Power BI app for capacity admins. It shows how much compute each item used, and when the capacity slowed jobs down (throttling). The Compute page covers 14 days. The app can't send alerts.

Workspace monitoring is an optional feature, off until you turn it on. It creates a monitoring Eventhouse in the workspace and writes logs there. One table, ItemJobEventLogs, records each job's status and times. You query the logs with KQL. Collection starts when you enable it, with no history before that.

ToolAnswers
Monitor hubDid my run succeed?
Capacity Metrics appWho is using up the capacity?
Workspace monitoringWhat do the logs say over time?

[230][231][232]

The pipeline failed at 6 a.m. The ops team noticed at 9. The alert would have noticed at 6:01. Picture: Retro pixel art, 16-bit video game style: a tiny pixel data engineer sleeps at a desk while a red pixel alarm bell on the wall rings, with a

Alerts: three ways to hear about a failure

Exam depth: know it cold.

AlertHow it worksBest for
Schedule failure emailsA free email when a scheduled run fails.Simple, free failure email.
Outlook or Teams activityA pipeline step on the failure path sends the message.A custom message about one step.
Activator ruleA rule watches job events and acts.Many events, Teams or automatic actions.

Activator is Fabric's no-code rules engine. It watches events, checks a condition, then acts. It can send an email or Teams message, run a pipeline or notebook, or start a Power Automate flow.

Schedule failure emails cover scheduled runs only, not manual ones.

Decision rule: free email on failure is the schedule email. A message from inside the pipeline is an Outlook or Teams activity. Anything richer is Activator.

[116][222][225]

Failure paths inside a pipeline

Exam depth: know it cold.

In a pipeline, a line from one activity to the next has a condition. It decides when the next activity runs:

  • On success (green): the first activity succeeded.
  • On failure (red): the first activity failed.
  • On completion (blue): it finished, either way.
  • On skip (gray): it never ran.

To alert on one step, add an Office 365 Outlook or Teams activity. Then connect it with an On failure line from the activity you want to watch.

[225][227]

Rendering diagram…
The Teams message runs only when the copy fails. The notebook runs only when it succeeds.

[227]

[226]

You are a data engineer at Northwind Rides. A pipeline runs two Copy data activities in parallel. You connect both to one Office 365 Outlook activity with On failure lines. One copy fails and no email arrives. You need an email when either copy fails. What should you do?

Pick one answer.

Activator rules on job events

Exam depth: know it cold.

You can build an Activator rule on job events in two ways.

  • From the Monitor hub. On Job runs, select ... next to an item, then Create and manage alerts > Alerts (paid). This needs workspace monitoring turned on, and the Contributor role or higher.
  • From an Activator item. Create an Activator, select Get data, then job events. Pick the pipeline and the event, such as failed or succeeded. Then choose email or Teams.

For one alert covering every pipeline in a workspace, use workspace monitoring. A KQL query finds failed jobs in ItemJobEventLogs, and an Activator rule alerts on its results.

[222][225]

Try it in Fabric

You need a scheduled item, such as a pipeline with a schedule, and the Contributor role.

  1. Sign in to Fabric and open Monitor from the navigation pane.
  2. Under Manage, select Alerts.
  3. Select the Schedule failure emails tab, then + Configure notifications.
  4. Choose your scheduled item and select Select a scheduled item.
  5. In Select recipients, enter your name or a group in your organization.
  6. Select Save.
  7. Go back to Job runs and filter Status to failed runs.

[222]

Exam-style practice

You are a data engineer at Northwind Rides. The nightly trips pipeline runs on a schedule. The team wants an email when a scheduled run fails. They want no extra cost and no changes to the pipeline. What should you set up?

Pick one answer.

[222]

You are a data engineer at Northwind Rides. The trips semantic model refreshed late this morning but finally succeeded. You need to see whether earlier attempts failed and why. Where do you look?

Pick one answer.

[229]

You are a data engineer at Northwind Rides. The rides workspace has 40 pipelines, and more get added each month. You need one alert for any failed pipeline run, without a rule per pipeline. What should you use?

Pick one answer.

[225]

FlashcardsIndex cardsFlashcards ⚡

Card 1 of 14

[116][221][222][227][228][229][230][231]

Worth keeping

  1. The Monitor hub shows every run; filter by time, item type, status and workspace.
  2. Semantic model refresh history lists each attempt, including automatic retries.
  3. The Capacity Metrics app shows compute use; workspace monitoring stores logs you query with KQL.
  4. Free email on scheduled failure, Outlook or Teams activity on a failure path, or Activator for the rest.

On the job

After the zero-rides morning, you set up three layers at Northwind Rides.

First, schedule failure emails on the nightly pipeline. They're free, and the on-call engineer gets them.

Second, a Teams activity on the failure path of the load step. It posts to the ops channel, so ops knows well before their 9 a.m. meeting.

Third, workspace monitoring with one Activator rule over ItemJobEventLogs. New pipelines are covered the day they're added.

Each morning you open Job runs, filter to failed, and check that the list is empty.

[222][225][227]

Now you hear about failures at 6:01. But the alert only says Failed. Next lesson: read the error, find the cause and fix pipelines, dataflows and notebooks.

Leaderboard

Loading…

50 XP for each lesson you finish, 10 for each right answer. Names show only for learners who turn on Show me on leaderboards.

Sources for this lesson (14)

Each fact in the lesson is marked with the number of the page it comes from.

  1. [4]Microsoft Learn: Study Guide for Exam DP-700
  2. [116]Microsoft Learn: What is Fabric Activator?
  3. [220]Microsoft Learn: What is the Monitor hub?
  4. [221]Microsoft Learn: Monitor job runs in the Monitor hub
  5. [222]Microsoft Learn: Set up job alerts in the Monitor hub (preview)
  6. [224]Microsoft Learn: Monitor pipeline runs in the legacy Monitoring hub
  7. [225]Microsoft Learn: Create alerts for pipeline runs
  8. [226]Microsoft Learn: Use the Office 365 Outlook activity to send an email with Outlook
  9. [227]Microsoft Learn: Pipeline canvas in Fabric Data Factory
  10. [228]Microsoft Learn: View refresh history and monitor your dataflows
  11. [229]Microsoft Learn: Data refresh in Power BI
  12. [230]Microsoft Learn: What is the Microsoft Fabric Capacity Metrics app?
  13. [231]Microsoft Learn: What is workspace monitoring (preview)?
  14. [232]Microsoft Learn: Enable workspace monitoring in Microsoft Fabric (pipelines)