SigNoz/signoz · error

couldn't generate nil check for field to be removed by op %s

Error message

couldn't generate nil check for field to be removed by op %s: %w

What it means

While building a log parsing pipeline, SigNoz generates an OTTL-style `if` condition that verifies the target field is non-nil before a `remove` operator runs. This error means fieldNotNilCheck could not produce that check for operator.Field, almost always because the field path has an unsupported/invalid prefix or syntax. The pipeline is rejected at PreparePipelineProcessor/getOperators time, so no pipeline with that operator can be created.

Source

Thrown at pkg/query-service/app/logparsingpipeline/pipelineBuilder.go:157

							operator.Name, err,
						)
					}
					if fieldsNotNilCheck != "" {
						operator.If = fieldsNotNilCheck
					}
				}
			} else if operator.Type == "move" || operator.Type == "copy" {
				fromNotNilCheck, err := fieldNotNilCheck(operator.From)
				if err != nil {
					return nil, fmt.Errorf(
						"couldn't generate nil check for From field of %s op %s: %w", operator.Type, operator.Name, err,
					)
				}
				operator.If = fromNotNilCheck
			} else if operator.Type == "remove" {
				fieldNotNilCheck, err := fieldNotNilCheck(operator.Field)
				if err != nil {
					return nil, fmt.Errorf(
						"couldn't generate nil check for field to be removed by op %s: %w", operator.Name, err,
					)
				}
				operator.If = fieldNotNilCheck
			} else if operator.Type == "trace_parser" {
				cleanTraceParser(&operator)
			} else if operator.Type == "time_parser" {
				parseFromNotNilCheck, err := fieldNotNilCheck(operator.ParseFrom)
				if err != nil {
					return nil, fmt.Errorf(
						"couldn't generate nil check for parseFrom of time parser op %s: %w", operator.Name, err,
					)
				}
				operator.If = parseFromNotNilCheck

				if operator.LayoutType == "strptime" {
					regex, err := pipelinetypes.RegexForStrptimeLayout(operator.Layout)
					if err != nil {

View on GitHub (pinned to 5069bf80b0)

Solutions

1. Fix the field path to start with a valid root, e.g. attributes.foo, resource.foo, or body
2. Verify the exact spelling/case of the key against the actual log record
3. If the key is dynamic, wrap or guard differently instead of remove on a non-standard path

Example fix

// before
{"type":"remove","field":"user_id"}
// after
{"type":"remove","field":"attributes.user_id"}

var fieldRootRe = regexp.MustCompile(`^(attributes|resource|body)(\.[A-Za-z0-9_.-]+)?$`)
func validFieldPath(f string) bool { return fieldRootRe.MatchString(f) }
for _, op := range pipeline.Operators {
  if op.Type == "remove" && !validFieldPath(op.Field) { return fmt.Errorf("bad field %q", op.Field) }
}

func isRemoveOp(op postprocess.Operator) bool { return op.Type == "remove" && validFieldPath(op.Field) }

If pipeline create/update returns an error, surface the operator name from the message to the user for correction rather than retrying.

When it happens

Trigger: Creating/updating a parsing pipeline whose operators array contains {"type":"remove","field":"<invalid path>"} — e.g. field "foo", "attr.x", or a path not starting with a recognized root like attributes./resource./body. POST/PUT to the pipelines API fails with this wrapped message naming the operator.

Common situations: Typos in field names in pipeline YAML/JSON; assuming any log field can be removed by bare name; copy-pasting pipelines between SigNoz versions with different allowed field roots; referencing nested keys without the attributes. prefix.

Related errors

• couldn't generate nil check for parseFrom of time parser op
• could not create nil check for %s: %w
• couldn't generate layout regex for time_parser %s: %w
• couldn't extract log fields referenced in expr %s: %w
• could not parse expr: %w

AI-assisted analysis of SigNoz/signoz@5069bf80b0 (2026-08-28). Data as JSON: /api/errors/8093e68800e48f57. Report an issue: GitHub.