Monitoring: System Overview
The Monitoring system is structured in the following manner:
Web Application Database
The Web Application database stores data for report and user interface events. The type of data tracked depends on the configuration. At the Extract interval, the monitoring service moves this data from the local db to the collected db.
Each Scheduler Service has a local database which stores report execution data, if enabled in the configuration. At the Extract interval, the monitoring service moves this data from the local dbs to the collected db.
Scheduler performance data is “persistent,” that is, always available, and is therefore not stored in the local scheduler databases. At the Statistics interval, the monitoring service polls the schedulers for their performance statistics, and logs this data in the collected db.
File Paths for Config Files & Databases
This topic references
<Sched>/as a placeholder for the Web Application, Web Service API and Scheduler Service's install location respectively. The default install location is
/opt/Exago/WebServiceApi/on Linux) or
/opt/Exago/Scheduler/on Linux); however, these directories can be changed during installation.
<WebApp>Monitoring\Monitoring.sqlite– WebApp db
<WebApp>appSettings.config– Select which web app data to track
MonitoringService\Monitoring.sqlite– Main collected db
MonitoringService\Monitoring.exe.config– Set Extraction & Statistics intervals
<Sched>Monitoring.sqlite– Scheduler local db
<Sched>eWebReportsScheduler.exe.config– Select which scheduled report data to track