Skip to main content

Monitoring using custom SQL Queries

Whilst Cardiograph does not directly support SQL monitoring, the WfD Stored Procedure Executor does have an integration to send query rows off to the Cardiograph proxy.

  • Download the latest version of the WfD Stored Procedure Executor from [https://wfd-public.s3.eu-west-2.amazonaws.com/Utilities/SQLExecutor/a.zip](https://wfd-public.s3.eu-west-2.amazonaws.com/Utilities/SQLExecutor/a.zip)
  • Extract the zip file, and copy the service files to a logical local folder on the server (C:\wfd\Services\WfD Stored Proecudure Executor
  • Open appsettings.json
  • Ensure IsDebug is set to true
  • Set the database connection string
  • Set the endpoint URL for the [Cardiograph Proxy](https://drflow.freshdesk.com/a/solutions/articles/44002039626)
  • Set the procedure name to be the stored procedure you want to use for monitoring. The service will send the data in the first column of the first row to Cardiograph. Ordinarily, this would mean returning a simple COUNT from the query inside the SPROC
  • Set EnableCardiograph to be true and the CardiographIdentifier to the client's identifier
  • Install the service as a Windows Service and start.