> For the complete documentation index, see [llms.txt](https://docs.infraon.io/log-management/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraon.io/log-management/user-guide/infraon-configuration/log-management/pipeline-configuration.md). # Pipeline Configuration Pipeline Configuration allows administrators to create and manage log pipelines that collect, process, and route log data to the appropriate destinations. Administrators can configure input listeners, associate Grok patterns, define output streams, and deploy pipelines to selected log collector hosts. ## How does it work? A log pipeline receives incoming log data through a configured input protocol and port. The pipeline can process logs using Grok patterns and filters before sending them to an OpenObserve stream or a configured secondary destination. Pipeline Configuration supports two types of pipelines: * **Parent Pipeline**: Defines the network listener, including the input protocol, port, and log collector hosts. It can write incoming logs directly to a stream or route them to child pipelines. * **Child Pipeline**: Uses filters to select specific log events or devices and sends the matching logs to its own output stream. It inherits the collector hosts from its parent and does not have its own input listener. The pipeline configuration is deployed to the selected log collector hosts. Saving a parent pipeline triggers deployment, while changes to a child pipeline take effect when its parent is deployed again. ## What you see on the screen The Pipeline Configuration page provides options to search, filter, and manage pipelines. The configuration is divided into two sections: Parent Pipelines and Child Pipelines. The Parent Pipelines section displays the created parent pipelines, while selecting a parent pipeline displays its associated child pipelines in the Child Pipelines section. Pipeline Configuration | **Basic Options**

Label	Action	Description/Example
Search	Enter a search term in the search field.	Searches for pipelines matching the entered keywords.
Filter	Apply the available filters.	Narrows down the displayed pipeline records based on the selected criteria.
Card View	Click the Card View icon.	Displays pipelines as cards with their details and available actions.
Grid View	Click the Grid View icon.	Displays pipelines in a tabular format for easier viewing and management.
Show All Child	Click Show All Child.	Displays all child pipelines instead of only the child pipelines associated with the selected parent pipeline. When this option is selected, the child pipelines are displayed in read-only mode.

### Parent Pipelines The Parent Pipelines section displays the created parent pipelines. Each pipeline card provides the following details and actions. Pipeline Configuration | **Parent Pipelines**

Label	Action	Description/Example
Parent Pipelines	View the section.	Displays the created parent pipelines.
Pipeline Name	View the pipeline card.	Displays the name assigned to the parent pipeline, such as UDP Pipeline.
Description	View the pipeline card.	Displays a brief description of the pipeline's purpose.
Type	View the pipeline card.	Displays the configured input protocol, such as UDP, TCP, Syslog, or Beats.
Log Device Count	Click the displayed count for a configured pipeline.	Opens the Log Device Summary section, which displays details of the log devices associated with the pipeline. The count is available only for configured pipelines.
Enable/Disable	Toggle the switch.	Enables or disables the corresponding parent pipeline.
Select	Select multiple parent pipelines.	Selects pipelines for bulk actions, such as enabling or disabling them.
Child Pipelines	Select a parent pipeline.	Displays the child pipelines associated with the selected parent.
Search Child Pipeline	Enter the child pipeline name in the search field under the Child Pipelines section.	Searches for a specific child pipeline associated with the selected parent pipeline.
Configuration Status	View the colored status dot.	A green dot indicates that the configuration has been completed. A grey dot indicates that the configuration has not yet been completed.
Edit	Click Edit on the parent pipeline card.	Opens the child pipeline configuration for editing.
Delete	Click Delete on the parent pipeline card.	Click the Delete option to delete the required parent pipeline.

When you select a particular parent pipeline, its associated child pipelines are displayed in the Child Pipelines section.

#### Upload Pipeline Configuration After creating or updating a parent pipeline, click Upload on the corresponding pipeline card to deploy its configuration to the Log Collector Server.

Label	Action	Description/Example
Upload	Click Upload on a parent pipeline card.	Initiates the process of uploading the pipeline configuration to the Log Collector Server.
Upload Confirmation	Review the confirmation message.	Displays: “Configuration will be uploaded to Log Collector Server.”
Yes, Upload It	Click the option.	Confirms the action and starts processing the configuration upload.
Cancel	Click the option.	Cancels the upload operation.

#### Upload Result After initiating the upload, click the Info icon to view the upload result and deployment messages. The upload result section displays the progress of the operation, including pipeline preparation, routing configuration, parser availability, connection to the log server, configuration upload, and service restart. For example, the result may contain the following messages:

Label	Action	Description/Example
Info	Click the Info icon.	Opens the upload result section with deployment progress and status messages.
Upload Status	View the upload result.	Displays messages such as Added to Queue, Configuration uploaded successfully, or a deployment failure.
Parser Status	Review parser-related messages.	Identifies parser files that are missing from the Log Collector Server and provides the expected file paths.
Host Upload Summary	View the summary.	Displays the deployment result for each target host, such as Deployed successfully.
Service Restart Status	Review the result message.	Indicates whether the log collector service restarted successfully or failed to restart.

{% hint style="info" %} A successful configuration upload does not necessarily mean that the pipeline is running. The upload result may report that the configuration was uploaded but the log collector service failed to restart. In this case, the pipeline may not be active, and the system administrator should be contacted. Similarly, if a parser is skipped because its file is missing, the upload result identifies the missing file and instructs the administrator to copy it to the specified location on the host before redeploying the configuration. {% endhint %}

### Child Pipelines The Child Pipelines section displays the child pipelines associated with a selected parent pipeline. Each child pipeline shows its name, description, stream name, configuration status indicator, log device count, and available actions. Pipeline Configuration | **Child Pipelines**

Label	Action	Description/Example
Name	View the child pipeline card.	Displays the name of the child pipeline.
Description	View the child pipeline card.	Displays a brief description of the child pipeline.
Stream Name	View the child pipeline card.	Displays the name of the stream associated with the child pipeline.
Configuration Status	View the colored status dot.	A green dot indicates that the configuration has been completed. A grey dot indicates that the configuration has not yet been completed.
Log Device Count	Click the displayed count.	Opens the Log Device Summary section, which displays details of the log devices associated with the pipeline.
Edit	Click Edit on the child pipeline card.	Opens the child pipeline configuration for editing.