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. Integrations

dbachecks

PreviousSend notifications to Slack and TeamsNextHow do I check if SQLWATCH is running OK?

Last updated 4 years ago

Was this helpful?

Integration with dbachecks allows SQLWATCH to pick up dbachecks' failures and notify via the SQLWATCH actions mechanism as well as show on the SQLWATCH dashboard. This is not a replacement for the dbachecks dashboard but a simple indication to allow time correlation with SQLWATCH performance metrics

The SQLWATCH check is simply querying the dbo.dbachecksResults table for any records where the result equals to 'Failed'.

dbachecks tables are deployed with SQLWATCH to satisfy the check criteria, however, they can be in another database, in which case the check will need to be modified to reference the correct database:

 @check_id = -48
,@check_name = 'dbachecks failed'
,@check_description = 'This check looks up any dbachceks that have a result of failed. Please check the dbachecks dashboard or tables for details.'
,@check_query = 'select @output=count(*)
from DATABASE.[dbo].[dbachecksResults]
where Result = ''Failed'' AND [Date] >= ''{LAST_CHECK_DATE}'''

For information around dbachecks please check their website

https://dbachecks.readthedocs.io