Page History

...

Provide technical information on the standard data model that is available for reports.
Users can use this information to create their own reports from the data model, see JobScheduler Reporting Interface (1.9.x, 1.10.x) - Technical Information - Data Model Customization
SQL scripts in this article are provided for PostgreSQL. The SQL scrpts for the respective DBMS are provided by the JobScheduler installer.

...

Expand

title	REPORTING_EXECUTIONS

Field	Nullable	Data type	Constraint	Unique Constraint	Description
`ID`	NOT NULL	NUMERIC	Primary Key
`SCHEDULER_ID`	NOT NULL	NUMERIC		X	corresponds to `SCHEDULER_ORDER_HISTORY.SPOOLER_ID`
`HISTORY_ID`	NOT NULL	NUMERIC		X	corresponds to `SCHEDULER_ORDER_HISTORY.HISTORY_ID`
`TRIGGER_ID`	NOT NULL	NUMERIC	Foreign Key	X	references `REPORT_TRIGGERS.ID`
TASK_ID	NOT NULL	NUMERIC	Foreign Key		references `REPORT_TASKS.ID`
CLUSTER_MEMBER_ID		VARCHAR			corresponds to `SCHEDULER_HISTORY.CLUSTER_MEMBER_ID`
`STEP`	NOT NULL	NUMERIC		X	corresponds to `SCHEDULER_ORDER_STEP_HISTORY.STEP`
FOLDER	NOT NULL	VARCHAR
`NAME`	NOT NULL	VARCHAR			corresponds to `SCHEDULER_HISTORY.JOB_NAME` e.g. `/test/my_job`
`BASENAME`	NOT NULL	VARCHAR			job base name e.g. `my_job`, for a given job path `test/my_job.job.xml`
`TITLE`	NULL	VARCHAR			corresponds to `INVENTORY_JOBS.TITLE`
`START_TIME`	NOT NULL	DATETIME			corresponds to `SCHEDULER_ORDER_STEP_HISTORY.START_TIME`
`END_TIME`	NULL	DATETIME			corresponds to `SCHEDULER_ORDER_STEP_HISTORY.END_TIME`
`STATE`	NOT NULL	VARCHAR			corresponds to `SCHEDULER_ORDER_STEP_HISTORY.STATE`
`CAUSE`	NOT NULL	VARCHAR			start cause for execution, can be mapped to an individual start cause by use of table `REPORT_MAP_CAUSES`
EXIT_CODE	NOT NULL	NUMERIC			corresponds to `SCHEDULER_HISTORY.EXIT_CODE`
`ERROR`	NOT NULL	NUMERIC			specifies if an error occurred: `0: no error` `1: error`
`ERROR_CODE`	NULL	VARCHAR			JobScheduler error code
`ERROR_TEXT`	NULL	VARCHAR			error message
AGENT_URL		VARCHAR			corresponds to `SCHEDULER_HISTORY.AGENT_URL`
`IS_RUNTIME_DEFINED`	NOT NULL	NUMERIC			specifies if a start time has been configured: `1: yes` `0: no`
SYNC_COMPLETED	NOT NULL	NUMERIC			for use by the JobScheduler Reporting Interface only: specifies if a synchronization has been completed: `1: yes` `0: no`
RESULTS_COMPLETED	NOT NULL	NUMERIC			for use by the JobScheduler Reporting Interface only: specifies if a aggregation has been completed: `1: yes` `0: no`
`CREATED`	NOT NULL	DATETIME			timestamp of record creation
`MODIFIED`	NOT NULL	DATETIME			timestamp of record modification

Expand

title	REPORTING_TASKS

Field	Nullable	Data type	Constraint	Unique Constraint	Description
`ID`	NOT NULL	NUMERIC	Primary Key
`SCHEDULER_ID`	NOT NULL	NUMERIC		X	corresponds to `SCHEDULER_HISTORY.SPOOLER_ID`
`HISTORY_ID`	NOT NULL	NUMERIC		X	corresponds to `SCHEDULER_HISTORY.ID`
IS_ORDER	NOT NULL	NUMERIC
CLUSTER_MEMBER_ID		VARCHAR			corresponds to `SCHEDULER_HISTORY.CLUSTER_MEMBER_ID`
`STEPS`	NOT NULL	NUMERIC			corresponds to `SCHEDULER_HISTORY.STEPS`
FOLDER	NOT NULL	VARCHAR
`NAME`	NOT NULL	VARCHAR			corresponds to `SCHEDULER_HISTORY.JOB_NAME` e.g. `/test/my_job`
`BASENAME`	NOT NULL	VARCHAR			job base name e.g. `my_job`, for a given job path `test/my_job.job.xml`
`TITLE`	NULL	VARCHAR			corresponds to `INVENTORY_JOBS.TITLE`
`START_TIME`	NOT NULL	DATETIME			corresponds to `SCHEDULER_HISTORY.START_TIME`
`END_TIME`	NULL	DATETIME			corresponds to `SCHEDULER_HISTORY.END_TIME`
`CAUSE`	NOT NULL	VARCHAR			corresponds to `SCHEDULER_HISTORY.CAUSE` start cause for execution, can be mapped to an individual start cause by use of table `REPORT_MAP_CAUSES`
EXIT_CODE	NOT NULL	NUMERIC			corresponds to `SCHEDULER_HISTORY.EXIT_CODE`
`ERROR`	NOT NULL	NUMERIC			specifies if an error occurred: `0: no error` `1: error`
`ERROR_CODE`	NULL	VARCHAR			JobScheduler error code
`ERROR_TEXT`	NULL	VARCHAR			error message
AGENT_URL		VARCHAR			corresponds to `SCHEDULER_HISTORY.AGENT_URL`
`IS_RUNTIME_DEFINED`	NOT NULL	NUMERIC			specifies if a start time has been configured: `1: yes` `0: no`
SYNC_COMPLETED	NOT NULL	NUMERIC			for use by the JobScheduler Reporting Interface only: specifies if a synchronization has been completed: `1: yes` `0: no`
RESULTS_COMPLETED	NOT NULL	NUMERIC			for use by the JobScheduler Reporting Interface only: specifies if a aggregation has been completed: `1: yes` `0: no`
`CREATED`	NOT NULL	DATETIME			timestamp of record creation
`MODIFIED`	NOT NULL	DATETIME			timestamp of record modification

...

Space shortcuts

Page tree

Versions Compared

Old Version 14

New Version 15

Key