# Pipeline Log

## Pipeline Log

### Description

![pipeline log](/files/DCqBhwxh352N5vplwBov)

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

A pipeline log streams logging information from a running pipeline to another pipeline.

The only requirement for the receiving pipeline is that it starts with a [Pipeline Logging](https://github.com/mbertazz/hop-docs-md/blob/main/modules/ROOT/pages/metadata-types/pipeline/transforms/pipeline-logging.53l6nFZrCd) transform. Other than that, the logging pipeline is "just another pipeline". In this logging pipeline, you can process the logging information and e.g. write to a relational or NoSQL database, a Kafka topic etc

### Samples

The samples project comes with an example pipeline log.

Check the metadata perspective for the pipeline log `pipeline-log-example`. This pipeline log is configured to send logging information for the pipeline `${PROJECT_HOME}/reflection/generate-fake-books.hpl` to the logging pipeline `${PROJECT_HOME}/reflection/pipeline-log-example.hpl`.

<figure><img src="/files/6gz6eH1N5u0tE5ZMx1Z2" alt=""><figcaption></figcaption></figure>

### Related Plugins

* [Pipeline Logging](/data-shaper-1.21/knowing-the-data-shaper-designer/pipelines/transforms/pipeline-logging.md)

### Options

| Option                                 | Default                                   | Description                                                                                                                                                    |
| -------------------------------------- | ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name                                   | The name to be used for this pipeline log |                                                                                                                                                                |
| Enabled?                               | true                                      |                                                                                                                                                                |
| Logging parent pipelines only          | false                                     | If you enable this, only the parent pipelines, executed by Hop Run, GUI, Server or API will be logged. When disabled, every pipeline execution will be logged. |
| Pipeline executed to capture logging   |                                           | the pipeline to process the logging information for this pipeline log                                                                                          |
| Execute at the start of the pipeline?  | true                                      | Should this pipeline log be executed at the start of a pipeline run                                                                                            |
| Execute at the end of the pipeline?    | false                                     | Should this pipeline log be executed at the end of a pipeline run                                                                                              |
| Execute periodically during execution? | true                                      | Should this pipeline log be executed periodically during a pipeline run                                                                                        |
| Interval in seconds                    | 30                                        | if executed periodically, indicates the interval at which the pipeline log is executed                                                                         |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.primeur.com/data-shaper-1.21/knowing-the-data-shaper-designer/index-2/pipeline-log.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
