Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The Monitor hub provides a guided way to monitor the health and usage of your applications in Microsoft Fabric. Use it to catch service issues early, track usage trends, and spot regressions after a release—without setting up monitoring for each application yourself.
This article shows you how to review baseline health and usage signals for an application, how the available metrics map to common monitoring scenarios, and how to reach richer diagnostics by onboarding to full observability.
Important
Application monitoring in the Monitor hub is currently in preview. See the Supplemental Terms of Use for Microsoft Azure Previews for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
Monitoring tiers
Monitoring comes in two tiers:
Always-on platform observability (default): Available out of the box, with no extra onboarding. This tier provides platform metrics for quick health checks, trend monitoring, and basic issue detection.
Full observability (onboarding-based): Available when you enable Workspace monitoring and advanced telemetry onboarding. This tier adds rich logs and traces, deeper dimensions and diagnostics, broader troubleshooting workflows, and more advanced alerting and root-cause analysis.
Prerequisites
Before you begin, make sure that you have the following:
- Access to Fabric and permission to open the Monitor hub.
- An application or workload that you can view in the Monitor hub.
- For full observability, Workspace monitoring and advanced telemetry onboarding enabled for your workspace.
Get started with monitoring
The default, always-on experience is low-friction and immediately useful. To start monitoring an application:
Sign in to Microsoft Fabric.
Open Monitor from the navigation pane. Switch to the new the Monitor hub experience if you're still in the classic view.
Select Applications.
Use the filters and search box to find your application.
Select the application to open the application experience view.
On the Dashboard, review the health signal metrics:
- Sign-ins count
- Query count
- Query error count
- Query error rate
- Average duration
- App load
Use the charts to identify regressions, then drill into deeper diagnostics if your workspace has full observability onboarding.
Map metrics to monitoring scenarios
The always-on metrics help you address common monitoring scenarios. Use the following table to identify the relevant metrics for each scenario.
| Scenario | Metrics to use |
|---|---|
| Is healthy right now? | Query error count, query error rate, and average duration trends. |
| Is usage stable and growing as expected? | Sign-ins count, app load, and query count. |
| Are regressions happening after release windows? | Correlate changes in query errors, query error rate, and average duration with deployment timing. |
Considerations and limitations
The following limitations apply to the preview:
- Scope is intentionally backend-first. The preview defers some frontend and function-level scenarios.
- The always-on tier doesn't fully expose advanced trace-level workflows. Enable full observability through Workspace monitoring and advanced telemetry onboarding to access rich logs and traces.