Configuration

The process pipelines configurations can get found under Pacemaker Process Pipelines Configuration

Pipeline Execute Time

Section Config Type Default Description

Section	Config	Type	Default	Description
Pipeline execute time	*Clean Up*	`Text (Cron Expression Format)`	*`0 3 * `*	Defines the time of creation and Execution of a cleanup pipeline. UTC or GMT+0 gets used as default
	*Use Timezones*	`Yes/No`	`No`	Defined time zones. `global Stores Configuration Locale Options Timezone` UTC is used as default

Pipeline execute time

Clean Up

Text (Cron Expression Format)

0 3 * * *

Defines the time of creation and Execution of a cleanup pipeline.

UTC or GMT+0 gets used as default

Use Timezones

Yes/No

No

Defined time zones.

global Stores Configuration Locale Options Timezone
UTC is used as default

Pipeline cleanups

Section Config Type Default Description

Section	Config	Type	Default	Description
Pipeline Cleanups	*Cleanup time mapping*	`Mapping - Cleanup`	`- All Pipelines - \| 3 weeks \| 3 months \| 6 months \| No`	It Defines the cleanup time periods for desired pipelines. The entry `-- ALL Pipelines -` serves as a fallback
	*Cleanup time mapping (dynamic)*	`Mapping - Cleanup`		Defines the cleanup time spans for dynamic pipelines that get not logged in with `pipeline.xml`. Entries defined here overwrite entries in Cleanup time mapping

Pipeline Cleanups

Cleanup time mapping

Mapping - Cleanup

- All Pipelines - | 3 weeks | 3 months | 6 months | No

It Defines the cleanup time periods for desired pipelines.

The entry -- ALL Pipelines - serves as a fallback

Cleanup time mapping (dynamic)

Mapping - Cleanup

Defines the cleanup time spans for dynamic pipelines that get not logged in with pipeline.xml.

Entries defined here overwrite entries in Cleanup time mapping

Working directory

Section Config Type Default Description

Section	Config	Type	Default	Description
Working Directory	*Location*	`Text - Directory path`	`var/pacemaker/pipelines`	Defines the working directory by which pipeline data gets generated, stored, and processed.
	*Name Pattern*	`Text - Regular Expression`	`%pipeline_id`	Defines the identification pattern of the pipeline data in the directory (system).

Working Directory

Location

Text - Directory path

var/pacemaker/pipelines

Defines the working directory by which pipeline data gets generated, stored, and processed.

Name Pattern

Text - Regular Expression

%pipeline_id

Defines the identification pattern of the pipeline data in the directory (system).

Execution options

Section Config Type Default Description

Section	Config	Type	Default	Description
Execution Options	*Maintenance Mode*	`Yes/No`	`No`	Enables/disables the maintenance mode for process pipelines. If active, no new pipelines get generated, and no waiting steps are processed
	*Mini heartbeat*	`Yes/No`	`Yes`	Defines if mini-heartbeats are allowed, which `beat` after each completed pipeline step to continue processing the pipeline / the next step
	*Initialization for dynamic Pipelines*	`Yes/No`	`Yes`	Enables/disables pipeline initialization. Dynamic pipelines are implemented with PHP and not defined by XML If enabled, dynamic pipelines will get generated
	*Use Init-Pipeline for pipeline generation*	`Yes/No`	`No`	Enable/disable Init-Pipeline. If enabled, all pipelines using `InitializationDataFetcherChain` are generated with an init pipeline and no longer with the heartbeat itself If enabled, it optimizes the heartbeat execution time See Pacemaker Import Pipelines configuration
	*Expire_in Buffer*	`Text`	`30 minutes`	This setting is used to extend the expiry date of a pipeline. This is a workflow protection if only some steps of the pipeline contain expire-in information.
	*Enable Heartbeat via Cron*	`Yes/No`	`Yes`	Enable/Disable the execution of the heartbeat as cron.
	*Heartbeat schedule*	`Text`	*` * * * `*	Cron-Expression for to schedule the heartbeat.

Execution Options

Maintenance Mode

Yes/No

No

Enables/disables the maintenance mode for process pipelines.

If active, no new pipelines get generated, and no waiting steps are processed

Mini heartbeat

Yes/No

Yes

Defines if mini-heartbeats are allowed, which beat after each completed pipeline step to continue processing the pipeline / the next step

Initialization for dynamic Pipelines

Yes/No

Yes

Enables/disables pipeline initialization.

Dynamic pipelines are implemented with PHP and not defined by XML
If enabled, dynamic pipelines will get generated

Use Init-Pipeline for pipeline generation

Yes/No

No

Enable/disable Init-Pipeline.

If enabled, all pipelines using InitializationDataFetcherChain are generated with an init pipeline and no longer with the heartbeat itself
If enabled, it optimizes the heartbeat execution time
See Pacemaker Import Pipelines configuration

Expire_in Buffer

Text

30 minutes

This setting is used to extend the expiry date of a pipeline. This is a workflow protection if only some steps of the pipeline contain expire-in information.

Enable Heartbeat via Cron

Yes/No

Yes

Enable/Disable the execution of the heartbeat as cron.

Heartbeat schedule

Text

* * * * *

Cron-Expression for to schedule the heartbeat.

Log level

Section Config Type Default Description

Section	Config	Type	Default	Description
Log Level	*Heartbeat Log Level*	`Select - Loglevel`	`ERROR`	Defines the log level for the pipeline heartbeat. `Log file = heartbeat.log`
	*Runner log level*	`Select - Loglevel`	`ERROR`	Defines the log level for the pipeline runner. `Log file = runner.log`
	*Executor log level*	`Select - Loglevel`	`INFO`	Defines the log level for the pipeline executors. Log `file = executor.log`
	*Step warning status by Executor Log*	`Yes/No`	`No`	Enables/Disables updating the step status based on logged warning messages.

Log Level

Heartbeat Log Level

Select - Loglevel

ERROR

Defines the log level for the pipeline heartbeat.

Log file = heartbeat.log

Runner log level

Select - Loglevel

ERROR

Defines the log level for the pipeline runner.

Log file = runner.log

Executor log level

Select - Loglevel

INFO

Defines the log level for the pipeline executors.

Log file = executor.log

Step warning status by Executor Log

Yes/No

No

Enables/Disables updating the step status based on logged warning messages.

Pipeline Overview

Section Config Type Default Description

Section	Config	Type	Default	Description
Pipeline Overview	*Shape of the pipeline steps*	`Select - PipelineShape`	`circle`	Defines the visual representation of the pipeline steps as circles or rectangles on the overview and detail pages.
	*Update Check Timeout*	`Text`	`30`	Timeout in seconds between pipeline list and step detail page update checks on `Pacemaker SYSTEM Process Pipelines`.
	*Autoreload Timeout*	`Text`	`2`	Timeout in seconds between pipeline list reloads, when autoreload is enabled on `Pacemaker SYSTEM Process Pipelines`.

Pipeline Overview

Shape of the pipeline steps

Select - PipelineShape

circle

Defines the visual representation of the pipeline steps as circles or rectangles on the overview and detail pages.

Update Check Timeout

Text

30

Timeout in seconds between pipeline list and step detail page update checks on Pacemaker SYSTEM Process Pipelines.

Autoreload Timeout

Text

2

Timeout in seconds between pipeline list reloads, when autoreload is enabled on Pacemaker SYSTEM Process Pipelines.

Pipeline Monitoring

Section Config Type Default Description

Section	Config	Type	Default	Description
Pipeline monitoring	*Enable Monitoring*	`Yes/No`	`No`	Enables/Disables the monitoring functionality.
	*Selection for Pipelines to monitor*	`Select - MonitorSelection`	{"0":{"pipeline_monitor_type":"all"}}	Select the pipelines to be monitored. With the standard all pipelines are monitored
	*Mapping for Pipeline Monitor Emails*	`Select - EmailMapping`	{"0":{"pipeline_type":"all", "email_receiver":"","disable_sending":"0"}}	Map different emails to each pipeline or decide to disable the email for specific pipelines. If you want to add more than one mail receiver, then do this by comma separate each entry
	*Monitor Email Sender*	`Text`		Sender email address for monitor mails.
	*Update observable schedule*	`Text - CronExpression`	*`/15 * * * `*	Schedule for review of pipelines to get monitored.
	*Update status schedule*	`Text - CronExpression`	*`/5 * * * `*	Schedule to check pipeline status of observing pipelines.
	*Send notification schedule*	`Text - CronExpression`	*`0 * * `*	Schedule to send the message regarding the monitoring.
	*Record all Pipeline interruptions*	`YES/NO`	`NO`	Activate/deactivate recording of all pipeline cancellations and interruptions via heartbeat.
	*Waiting Status Time Period*	`Text`	`6 hours`	Time to determine when a pipeline should change its status to waiting.
	*Keep monitor data of deleted pipelines*	`YES/NO`	`NO`	Select if you want to keep monitor data even if the pipeline was deleted.

Pipeline monitoring

Enable Monitoring

Yes/No

No

Enables/Disables the monitoring functionality.

Selection for Pipelines to monitor

Select - MonitorSelection

{"0":{"pipeline_monitor_type":"all"}}

Select the pipelines to be monitored.

With the standard all pipelines are monitored

Mapping for Pipeline Monitor Emails

Select - EmailMapping

{"0":{"pipeline_type":"all", "email_receiver":"","disable_sending":"0"}}

Map different emails to each pipeline or decide to disable the email for specific pipelines.

If you want to add more than one mail receiver, then do this by comma separate each entry

Monitor Email Sender

Text

Sender email address for monitor mails.

Update observable schedule

Text - CronExpression

*/15 * * * *

Schedule for review of pipelines to get monitored.

Update status schedule

Text - CronExpression

*/5 * * * *

Schedule to check pipeline status of observing pipelines.

Send notification schedule

Text - CronExpression

0 * * * *

Schedule to send the message regarding the monitoring.

Record all Pipeline interruptions

YES/NO

NO

Activate/deactivate recording of all pipeline cancellations and interruptions via heartbeat.

Waiting Status Time Period

Text

6 hours

Time to determine when a pipeline should change its status to waiting.

Keep monitor data of deleted pipelines

YES/NO

NO

Select if you want to keep monitor data even if the pipeline was deleted.

The Config Monitor Email Recipients has been removed
This configuration was migrated to the new Config Mapping for Pipeline Monitor Emails

Configuration

Pipeline Execute Time

Pipeline cleanups

Working directory

Execution options

Log level

Pipeline Overview

Pipeline Monitoring

WIR HÄTTEN IHNEN DIESE MELDUNG AUCH GERNE ERSPART ...