Log Architecture & Structural Overview

The Kubernetes Kubelet Node Daemon Log Parser is an essential telemetry stream within the Containers & Kubernetes ecosystem. Parse Kubelet node daemon logs with system severity levels, source files, and container lifecycle events.

This schema defines a structure of 8 extracted attributes, including 4 numeric metrics and 4 string dimensions. In production observability architectures, these tokens provide high-cardinality indexing keys for telemetry pipelines before shipping to storage backends such as ClickHouse, Elasticsearch, Amazon S3, or Datadog.

Raw Telemetry Ingestion Profile

A typical raw event line for kubelet-system-log averages 111 bytes across 8 tokens. Modern collectors such as Fluent Bit and Vector require zero-backtracking regular expressions to avoid CPU spikes during traffic surges.

Extracted Field Schema & Data Types

The transpiled Grok pattern extracts the following schema fields from each raw event line. Data collectors cast these values according to the typed mappings below.

Field Name	Inferred Type	Description & Collector Semantics
severity	string	Single-character severity: I=Info, W=Warning, E=Error, F=Fatal.
month	integer	Month integer.
day	integer	Day integer.
time	string	Time of log entry.
pid	integer	Kubelet process ID.
file	string	Go source code filename.
line	integer	Go source code line number.
message	string	Lifecycle event message.

Common Regex Traps & Production Edge Cases

Engineers frequently encounter ingestion failures or pipeline drops due to subtle variations in real-world event logs. Watch out for these verified pitfalls:

1Kubelet uses standard Google klog formatting, where severity character precedes date without delimiter.

2Fatal logs (F) trigger immediate kubelet termination.

Production Collector Setup & Configurations

Pre-configured parser definitions ready to be dropped into your infrastructure repository.

Fluent Bit (parsers.conf)

Format: regex

# ==============================================================================
# Fluent Bit Parser Configuration (parsers.conf)
# ==============================================================================
[PARSER]
    Name        logpipeline_parser
    Format      regex
    Regex       ^(?<severity>[IWEF])(?<month>[0-9]{2})(?<day>[0-9]{2}) (?<time>(?:(?:(?:2[0123]|[01]?[0-9])):(?:(?:[0-5][0-9]))(?::(?:(?:(?:[0-5]?[0-9]|60)(?:[:.,][0-9]+)?))))) (?<pid>(?:[+-]?(?:[0-9]+))) (?<file>\S+):(?<line>(?:[+-]?(?:[0-9]+)))\] (?<message>.*)$
    Time_Key    time
    Time_Format %Y-%m-%dT%H:%M:%S%z
    Types       pid:integer line:integer

# ==============================================================================
# Fluent Bit Pipeline Filter (fluent-bit.conf)
# ==============================================================================
[FILTER]
    Name         parser
    Match        *
    Key_Name     log
    Parser       logpipeline_parser
    Reserve_Data On

Vector.dev (Remap VRL)

parse_regex!

# ==============================================================================
# Vector.dev Remap Language (VRL) Transform
# Use inside a 'remap' transform in vector.yaml
# ==============================================================================
.parsed, err = parse_regex(.message, r'^(?<severity>[IWEF])(?<month>[0-9]{2})(?<day>[0-9]{2}) (?<time>(?:(?:(?:2[0123]|[01]?[0-9])):(?:(?:[0-5][0-9]))(?::(?:(?:(?:[0-5]?[0-9]|60)(?:[:.,][0-9]+)?))))) (?<pid>(?:[+-]?(?:[0-9]+))) (?<file>\S+):(?<line>(?:[+-]?(?:[0-9]+)))\] (?<message>.*)$')

if err == null {
    . = merge(., .parsed)
    del(.parsed)

    # Type coercions
    .pid = to_int!(.pid)
    .line = to_int!(.line)

} else {
    log("LogPipeline parsing warning: " + err, level: "warn")
}

# ==============================================================================
# vector.yaml Pipeline Component
# ==============================================================================
transforms:
  parse_logs:
    type: remap
    inputs: ["source_logs"]
    source: |
      .parsed, err = parse_regex(.message, r'^(?<severity>[IWEF])(?<month>[0-9]{2})(?<day>[0-9]{2}) (?<time>(?:(?:(?:2[0123]|[01]?[0-9])):(?:(?:[0-5][0-9]))(?::(?:(?:(?:[0-5]?[0-9]|60)(?:[:.,][0-9]+)?))))) (?<pid>(?:[+-]?(?:[0-9]+))) (?<file>\S+):(?<line>(?:[+-]?(?:[0-9]+)))\] (?<message>.*)$')
      if err == null {
        . = merge(., .parsed)
        del(.parsed)
      }

Datadog Log Pipeline Grok Parser

match_rules

# ==============================================================================
# Datadog Log Processing Pipeline Grok Parser
# Navigate to: Logs -> Configuration -> Pipelines -> Add Processor -> Grok Parser
# ==============================================================================

# Match Rule:
rule (?<severity>[IWEF])(?<month>[0-9]{2})(?<day>[0-9]{2}) %{TIME:time} %{INT:pid} %{NOTSPACE:file}:%{INT:line}\] %{GREEDYDATA:message}

# Complete Datadog Pipeline Processor JSON:
{
  "type": "grok-parser",
  "name": "LogPipeline Grok Parser",
  "is_enabled": true,
  "source": "message",
  "samples": [],
  "grok": {
    "match_rules": "rule (?<severity>[IWEF])(?<month>[0-9]{2})(?<day>[0-9]{2}) %{TIME:time} %{INT:pid} %{NOTSPACE:file}:%{INT:line}\\] %{GREEDYDATA:message}",
    "support_rules": ""
  }
}

# Target Fields Created:
# time (string), pid (integer), file (string), line (integer), message (string), severity (string), month (string), day (string)

OpenTelemetry Collector (transform processor)

regex_parser

# ==============================================================================
# OpenTelemetry Collector Configuration (otel-collector-config.yaml)
# Option 1: Filelog Receiver with regex_parser Operator
# ==============================================================================
receivers:
  filelog:
    include: [ /var/log/**/*.log ]
    start_at: beginning
    operators:
      - type: regex_parser
        id: logpipeline_regex_parser
        regex: '^(?<severity>[IWEF])(?<month>[0-9]{2})(?<day>[0-9]{2}) (?<time>(?:(?:(?:2[0123]|[01]?[0-9])):(?:(?:[0-5][0-9]))(?::(?:(?:(?:[0-5]?[0-9]|60)(?:[:.,][0-9]+)?))))) (?<pid>(?:[+-]?(?:[0-9]+))) (?<file>\S+):(?<line>(?:[+-]?(?:[0-9]+)))\] (?<message>.*)$'
        timestamp:
          parse_from: attributes.time
          layout: '%Y-%m-%dT%H:%M:%S%z'

# ==============================================================================
# Option 2: Transform Processor (OTel Transformation Language - OTTL)
# ==============================================================================
processors:
  transform:
    error_mode: ignore
    log_statements:
      - context: log
        statements:
          - merge_maps(attributes, extract_patterns(body, "^(?<severity>[IWEF])(?<month>[0-9]{2})(?<day>[0-9]{2}) (?<time>(?:(?:(?:2[0123]|[01]?[0-9])):(?:(?:[0-5][0-9]))(?::(?:(?:(?:[0-5]?[0-9]|60)(?:[:.,][0-9]+)?))))) (?<pid>(?:[+-]?(?:[0-9]+))) (?<file>\\S+):(?<line>(?:[+-]?(?:[0-9]+)))\\] (?<message>.*)$"), "insert")

service:
  pipelines:
    logs:
      receivers: [filelog]
      processors: [transform]
      exporters: [otlp]

Logstash Filter Configuration

filter.grok

# ==============================================================================
# Logstash Pipeline Configuration (/etc/logstash/conf.d/logpipeline.conf)
# ==============================================================================
filter {
  grok {
    match => { "message" => "(?<severity>[IWEF])(?<month>[0-9]{2})(?<day>[0-9]{2}) %{TIME:time} %{INT:pid:integer} %{NOTSPACE:file}:%{INT:line:integer}\] %{GREEDYDATA:message}" }
    tag_on_failure => [ "_grokparsefailure" ]
  }

  date {
    match => [ "time", "ISO8601", "dd/MMM/yyyy:HH:mm:ss Z" ]
    target => "@timestamp"
    remove_field => [ "time" ]
  }
}