Endpoints

• IPC - endpoint used by a local Views service to read events
• gRPC Admin (55340) - endpoint used specifically by the local Admin service for configuring settings and requesting status information

Settings

SERVICE SETTINGS

• Delayed Start Time (seconds) - a general delay from when the service starts until calculations/events are evaluated
• Destination Historians - a comma delimited list of Historian machine names where calculations will be written to
• AssetInstanceCount Read Interval (seconds) - the frequency at which the service evaluates the total number of all asset instances for each asset type to be used in the 'AssetInstanceCount' function
• Property Read Interval (minutes) - the frequency at which the service evaluates the properties of each tag to be used in the 'Property' function 
• Check for New Assets Interval (minutes) - the frequency at which the service checks for new assets that have come online
• Views Service Reconnect Delay (seconds) - the frequency at which the Calculation service tries to reconnect to the Views service after a disconnect
• Max backfilling calculations - a throttling mechanism used to limit the max number of calculations that are permitted to backfill simultaneously

• Restart Failed Calculations Interval (minutes) - how frequently calculations in the "Error" state are restarted

• Live Data Read Interval (milliseconds) - how frequently live data is retrieved from Views

• SaF Keepalive Interval (seconds) - how frequently a keepalive request is made to SaF

• SaF Reconnect Interval (seconds) - how quickly to reconnect to SaF when the connection is lost

IDENTITY

• Identity API Token - token used to authorize tag access when the Calc service is remote from the Views service. This token must be mapped to a Canary user who would need placed on the Views>Bypass Security access control list within the Identity tile>Security>Access Control Lists screen.

  

EVENTS DATABASE SETTINGS

• Provider - the method for storing the Events database
  1. SQLite - by default, events will be stored in C:\ProgramData\Canary\Events\CanaryEvents.sqlite
  2. MSSQL - events will be stored in a Microsoft SQL database determined by the remaining parameters. (See Storing Events in an External SQL Database)
• Server - the machine name of the SQL server that will store the events
• Name - the name of the database in which the events table will be created
• User/Password - the credentials used to authenticate and write to the SQL database
• Is Domain User - determines if the configured user is a domain user