Skip to content

Now with a max duration of data to query configuration
Compare
Choose a tag to compare
@jbsouthe jbsouthe released this 07 Feb 22:51
· 20 commits to main since this release
release-v1.12
fcd40aa

The default settings are shown:

<Scheduler enabled="false">
    <PollIntervalMinutes>60</PollIntervalMinutes>
    <FirstRunHistoricNumberOfDays>2</FirstRunHistoricNumberOfDays>
    **<MaxNumberOfDaysToQueryAtATime>14</MaxNumberOfDaysToQueryAtATime>**
    <ControllerThreads>50</ControllerThreads>
    <DatabaseThreads>50</DatabaseThreads>
    <ConfigurationRefreshEveryHours>12</ConfigurationRefreshEveryHours>
</Scheduler>
  • enabled=false causes the Scheduler to exit after one run, true is the default, when this option is missing.
  • PollIntervalMinutes 60, if enabled, causes the Scheduler to sleep for 60 minutes and run again, continuously
  • FirstRunHistoricNumberOfDays 2, causes the extract to default in pulling the last 48 hours of data for a given query, if no previous run is detected in the control table, specified in the database section later
  • MaxNumberOfDaysToQueryAtATime 14, forces the run to only pull a maximum of 14 days of data at a time, this means it will always have work to do grabbing 14 days of data each scheduled interval until caught up.
  • ControllerThreads 50, the number of threads to run pulling data from the controllers concurrently
  • DatabaseThreads 50, the number of worker threads watching the data queue to insert into the database
  • ConfigurationRefreshEveryHours 12, after this many hours, all the applications with the configuration setting to pull all metrics, will refresh the metrics in case new ones are registered since start.
Assets 5
Loading