Create a Logging Pipeline
A logging pipeline refers to an instance of the logging service set up to receive, process, and store log data from various sources.
To create a logging pipeline, you need to follow these steps:
1. In the DCD, go to Menu > Observability > Logging Service.
2. Click Create logging pipeline from the Logging Service overview page.
3. Configure the following details for a logging pipeline:
4. Click Create to create a logging pipeline.

Result: The logging pipeline is successfully created. An authorization key is provided which is needed to configure your logging agent's (FluentBit) configuration to send logs.
Define logging pipeline properties
To define the logging pipeline properties, enter the following details:
1. Name: Enter a name for the logging pipeline. The name is only for your reference and does not have to be unique. Example, my-logging-pipeline
.
2. Region: Select a region from the drop-down list to create the logging pipeline in that specific region. The region determines where your logs will be processed and stored.

Define log sources
The log sources refer to the origins from which the log agent will collect logs. You can define multiple log sources for a single logging pipeline, and each log source can be configured with specific settings.
To define the log sources for a logging service, enter the following details:
1. Source Type: Select the log source type from the drop-down list. It defines the source from which you want to send logs. The available options are:
Kubernetes: For sending logs from Kubernetes cluster.
Docker: For sending logs from Docker containers.
Systemd: For sending logs from systemd journal.
Generic: For sending logs from any other source that is not covered by the above options.
2. Tag: Enter a unique tag for the log source. The tag is used to identify the log source and can be used for filtering and searching logs later. Example, myk8s
.
3. Protocol: Select one of the protocols from the drop-down list for sending logs. The available options are:
TCP: For sending logs over TCP.
HTTP: For sending logs over HTTP.
4. Retention: Choose the retention period for the logs collected from this source. The retention period determines how long the logs will be stored before they are automatically deleted. The available options are:
7 days
14 days
30 days
Unlimited
5. Click Add source to define another log source. Repeat the steps from step 1 to step 4 to add the log source and click Create. You can add up to 5 log sources per logging pipeline.

Warning: The Unlimited retention can lead to high storage costs and performance issues. It is advisable to set a reasonable retention period based on your logging requirements.
Note: You will receive a key upon successful pipeline creation. Ensure the key is saved in a secure place, as you will receive it only upon pipeline creation.

Last updated
Was this helpful?