Logging

Hop allows data developers to influence how, where and at which level of detail logging information is generated and where it is written to.

The amount of text logging generated depends on the logging level which is used when executing a workflow or pipeline:

Runtime levels

The logging level can be specified when executing using hop-run or in the Hop GUI. It is also possible to use the debug plugin to set custom logging levels on a transform:

You can set a custom logging level for this particular transform and only for certain rows of data:

You can do likewise for a workflow:

The logging file of the Hop GUI is saved in the folder (or in the folder set by ) in the file.

Write to log

The Write to log acction writes a specific string to the Hop logging system.

Check the Write To Log page for more details.

Metadata Types

Pipeline Log

A pipeline log allows to log the activity of a pipeline with another pipeline.

Check the and logging reflection pages for more details.

Workflow Log

Allows to log the activity of a workflow with a pipeline.

Check the workflow log and pages for more details.

Neo4j

Hop can write execution logs for workflows and pipelines to a Neo4j database.

Check page for more details.

Transforms

Write to Log

This transform writes information to the Hop logging system.