LogoLogo
ReleasesHomepageBlogSlack
3.0
3.0
  • Welcome
  • Concept
  • SQLWATCH Database
    • Requirements
      • Permissions
      • Performance Overhead
      • Storage Utilisation
    • Installation
      • Install with dbatools
      • Install with SqlPackage
      • Install with SSMS
      • Deploy from source code
      • Optional Components
      • Upgrade
      • Removal
      • Downgrade
    • Configuration
    • Known Issues
      • Collation conflict
      • Database drift
      • Login failed error when running disk logger
      • Deadlock when creating database
    • Notifications
      • Checks
      • Actions
      • Reports
      • How To
        • Add or modify check
        • Add or modify action
        • Add or modify report
      • Process Flow
    • Large Environments
  • Central Repository
    • Requirements
      • Performance overhead on the remote instance
      • Permissions
    • Installation
      • Removal
      • Upgrade
    • Configuration
    • Known Issues
  • Power BI Dashboard
    • Requirements
      • Permissions
    • Installation
    • Configuration
    • Known Issues
      • Power BI Load Errors
    • Performance
  • Grafana Dashboard
    • Requirements
    • Installation
    • Configuration
  • Azure Log Analytics Dashboard
    • Concept
    • Requirements
    • Installation
    • Configuration
  • Design Decision
    • Relations
    • Trend Tables
    • Data Types
      • Real Type
    • Primary Keys
    • Data Compression
    • Configuration Items
    • Using Apply instead of Join
  • Reference
    • Data-Tier Application Package
  • Integrations
    • Send notifications to Slack and Teams
    • dbachecks
  • FAQ
    • How do I check if SQLWATCH is running OK?
    • I am not seeing any data in Power BI
    • Can I modify default checks?
    • The app_log is growing fast
Powered by GitBook
On this page

Was this helpful?

  1. Azure Log Analytics Dashboard

Concept

PreviousConfigurationNextRequirements

Last updated 4 years ago

Was this helpful?

SQLWATCH can send data to Azure Log Analytics which can be used centralised storage for long term storage and data analysis.

Each SQLWATCH instance can send data independently and does not require any central repository or central servers. Each server will require access to the Azure Log API over the internet.

Although it is possible to set it up in a way that the central server is sending the data rather than individual instance, such configuration is out of the scope of this document.

The main benefit is that we can offload the entire reporting to Azure where we can keep months worth of data and do all kinds of data analysis using Azure Workbooks.

Power BI also has the functionality to interface with the Azure Log Analytics. Although the default dashboard that comes with SQLWATCH connects to a SQL Server, it can be modified to connect to Azure Log Analytics.

Alerts can also be set in Azure Log to monitor missing data and alert us when a server stopped sending data or when the thresholds are out of bounds.

Screenshots