...
- The Reporting Interface provides a data basis for individual reports:
- User requirements are far too individual to be covered with a single, general solution.
- A data model ist provided that can be used to import the scheduling history into individual reporting systems, e.g. data warehouses. For details see JobScheduler Reporting Interface (1.9.x, 1.10.x) - Technical Information - Standard Data Model
- No standards reports are provided as they are not in scope of the Reporting Interface. Sample reports for MS Excel are provided that can be used as a starting point for individual reports.
- The Reporting Interface is used to provide facts and aggregations in a timely manner, e.g. for daily reporting.
...
- Facts and Aggregations
- Implications
- The steps for collection of facts and aggregation of data are clearly separated and are provided by different jobs with individual start times:
- Facts
- are collected from the JobScheduler history and are stored to fact tables.
- can be collected multiple times per day.
- collection intervals can be freely configured.
- Aggregations
- are created for periods, e.g. daily, weekly, monthly, quarterly, yearly.
- are created exclusively based on fact tables.
- can be re-created any time (provided that the facts are available).
- Facts
- The steps for collection of facts and aggregation of data are clearly separated and are provided by different jobs with individual start times:
- Implications
- Clustering
- User Story
- As an Application Manager I want to create reports across Cluster Members and Agents.
- Implications
- The history data of all JobScheduler instances that are logging to the same database are used by the Reporting Interface. The reporting jobs can be configured to collect reporting data for individual JobSchedulers specified by the Scheduler IDs.
- If multiple JobScheduler clusters are operated then then Reporting Interface can be used
- to collect history data from a number of JobScheduelr databases and
- to write reporting data into a common reporting database.
- Periods
- User Story
- As an Application Manager I would like to specify a period from..to for all reports.
- Implications
- The period of one day includes the start times of jobs and orders with respect to the UTC time zone.
- Parameterisation
- Date from, previous month
- Date to, for one month
- User Story
- Mandators and Applications
- User Story
- As an Application Manager I would like to restrict reports to specific mandators and applications.
- Implications
- The rules for assigning mandators and applications to job objects are individual per user.
- A mapping mechanism is provided that includes look-up tables for individual mandators and applications.
- Mandators and applications are not included in fact tables.
- Parameterisation
- Mapping tables for the mapping of job objects to mandators and applications are provided.
- Job Reporting
- User Story
- As an Application Manager I want to restrict reports to specific jobs and job chains.
- Parameterisation
- Specification of jobs and job chains, e.g. by regular expressions.
- User Story
- File Transfer Reporting
- Inclusion of file transfer history data requires use of the JADE the YADE Background Service.
- The jobs for file transfers are in scope of the job reporting.
- The Reporting Interface makes use of the tables for history data that are specific for JADEYADE.
- Impact on Job Objects
- The Reporting Interface does not affect the configuration and execution of jobs.
- No modifications of existing jobs are required.
...