SigNoz
Why SigNozDocs
PricingCustomer Stories
Docs
IntroductionContributingMigrate from DatadogSigNoz API
OpenTelemetry
What is OpenTelemetryOpenTelemetry Collector GuideOpenTelemetry Demo
Community
Support
Slack
X
Launch Week
Changelog
Dashboard Templates
DevOps Wordle
Newsletter
KubeCon, Atlanta 2025
More
SigNoz vs DatadogSigNoz vs New RelicSigNoz vs GrafanaSigNoz vs Dynatrace
Careers
AboutTermsPrivacySecurity & Compliance
SigNoz Logo
SigNoz
All systems operational
HIPAASOC-2
SigNoz Cloud - This page applies to SigNoz Cloud editions.
Self-Host - This page applies to self-hosted SigNoz editions.

Logs Pipelines Overview

Logs Pipelines transform your raw logs into structured, queryable data before storage. Extract fields, parse JSON, normalize attributes, and enrich your logs from the SigNoz UI without redeploying your applications.

Why Use Logs Pipelines?

Raw logs contain valuable information, but it's often buried in unstructured text. Without parsing, you can only search the full log body, making filtering and aggregation difficult or impossible.

With Logs Pipelines, you can extract fields like user agent, status code, or IP address into structured attributes. These attributes become queryable columns you can filter, group by, and aggregate.

Nginx Log with/without parsing
Nginx Log with/without parsing

Once fields are extracted, you can build dashboards and reports like tracking requests by user agent or analyzing error rates by endpoint.

Pipelines

Rules for transforming logs are configured by creating Logs Processing Pipelines in SigNoz UI.
A pipeline is typically dedicated to a single preprocessing responsibility. For example, extraction of attributes from nginx text logs would happen in its own pipeline, and there would be another pipeline for parsing application logs and yet another for dropping PII fields from log attributes.

A list of pipelines, each addressing a single responsibility

A list of pipelines, each addressing a single responsibility

Logs get preprocessed by passing them through the chain of logs pipelines one by one. If a log matches a pipeline's filter, it gets processed (transformed) by that pipeline, before moving on to test the log against the next pipeline's filter and so on.

In the example above, each incoming log would first get tested for "nginx logs parser" pipeline's filter, and if it is a match, it will be transformed by that pipeline. The transformed log will then be tested for a match with the "Application Logs Parser" pipeline, followed by other pipelines in the chain one by one.

Processors

Apart from specifying a filter to identify the logs it can process, a pipeline is composed of a chain of log processors. Each processor takes care of a particular type of log transformation.
When a log matches a pipeline's filter, it is processed through its chain of processors one by one.

Processors for an Nginx pipeline

Processors for an Nginx pipeline

SigNoz provides a variety of processors for achieving desired log transformations.

Next Steps

  • Logs Parsing — Learn to create pipelines and choose the right parser
  • All Processors — Complete list of available log processors

Last updated: May 4, 2026

Edit on GitHub

Was this page helpful?

Your response helps us improve this page.

Prev
Parse Multiline Logs
Next
Introduction
On this page
Why Use Logs Pipelines?
Pipelines
Processors
Next Steps

Is this page helpful?

Your response helps us improve this page.