Log Architecture & Structural Overview

The ASP.NET Core Kestrel Hosting Log Parser is an essential telemetry stream within the Application Frameworks & Runtimes ecosystem. Parse ASP.NET Core Kestrel hosting logs with event IDs, categories, and HTTP response codes.

This schema defines a structure of 8 extracted attributes, including 1 numeric metrics and 7 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 aspnet-core-kestrel averages 118 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
level	string	Microsoft logging severity level.
category	string	Logging category namespace.
event_id	integer	Event ID integer.
http_version	string	HTTP protocol version.
method	string	HTTP method.
scheme	string	Scheme (http or https).
host	string	Host header.
path	string	URI path.

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:

1ASP.NET Core formats logs across multiple lines (Request starting, Request finished). Use Serilog to emit structured JSON.

2Kestrel adds six spaces before 'Request starting'.

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       ^(?<level>\S+): (?<category>\S+)\[(?<event_id>(?:[+-]?(?:[0-9]+)))\]\s+Request starting HTTP/(?<http_version>(?:(?:(?:[+-]?(?:[0-9]+(?:\.[0-9]+)?|\.[0-9]+))))) (?<method>\b\w+\b) (?<scheme>\S+)://(?<host>\b(?:[0-9A-Za-z][0-9A-Za-z-]{0,62})(?:\.(?:[0-9A-Za-z][0-9A-Za-z-]{0,62}))*(?:\.?|\b))(?<path>\S+)$
    Time_Key    timestamp
    Time_Format %Y-%m-%dT%H:%M:%S%z
    Types       event_id: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'^(?<level>\S+): (?<category>\S+)\[(?<event_id>(?:[+-]?(?:[0-9]+)))\]\s+Request starting HTTP/(?<http_version>(?:(?:(?:[+-]?(?:[0-9]+(?:\.[0-9]+)?|\.[0-9]+))))) (?<method>\b\w+\b) (?<scheme>\S+)://(?<host>\b(?:[0-9A-Za-z][0-9A-Za-z-]{0,62})(?:\.(?:[0-9A-Za-z][0-9A-Za-z-]{0,62}))*(?:\.?|\b))(?<path>\S+)$')

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

    # Type coercions
    .event_id = to_int!(.event_id)

} 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'^(?<level>\S+): (?<category>\S+)\[(?<event_id>(?:[+-]?(?:[0-9]+)))\]\s+Request starting HTTP/(?<http_version>(?:(?:(?:[+-]?(?:[0-9]+(?:\.[0-9]+)?|\.[0-9]+))))) (?<method>\b\w+\b) (?<scheme>\S+)://(?<host>\b(?:[0-9A-Za-z][0-9A-Za-z-]{0,62})(?:\.(?:[0-9A-Za-z][0-9A-Za-z-]{0,62}))*(?:\.?|\b))(?<path>\S+)$')
      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 %{NOTSPACE:level}: %{NOTSPACE:category}\[%{INT:event_id}\]\s+Request starting HTTP/%{NUMBER:http_version} %{WORD:method} %{NOTSPACE:scheme}://%{HOSTNAME:host}%{NOTSPACE:path}

# Complete Datadog Pipeline Processor JSON:
{
  "type": "grok-parser",
  "name": "LogPipeline Grok Parser",
  "is_enabled": true,
  "source": "message",
  "samples": [],
  "grok": {
    "match_rules": "rule %{NOTSPACE:level}: %{NOTSPACE:category}\\[%{INT:event_id}\\]\\s+Request starting HTTP/%{NUMBER:http_version} %{WORD:method} %{NOTSPACE:scheme}://%{HOSTNAME:host}%{NOTSPACE:path}",
    "support_rules": ""
  }
}

# Target Fields Created:
# level (string), category (string), event_id (integer), http_version (string), method (string), scheme (string), host (string), path (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: '^(?<level>\S+): (?<category>\S+)\[(?<event_id>(?:[+-]?(?:[0-9]+)))\]\s+Request starting HTTP/(?<http_version>(?:(?:(?:[+-]?(?:[0-9]+(?:\.[0-9]+)?|\.[0-9]+))))) (?<method>\b\w+\b) (?<scheme>\S+)://(?<host>\b(?:[0-9A-Za-z][0-9A-Za-z-]{0,62})(?:\.(?:[0-9A-Za-z][0-9A-Za-z-]{0,62}))*(?:\.?|\b))(?<path>\S+)$'
        timestamp:
          parse_from: attributes.timestamp
          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, "^(?<level>\\S+): (?<category>\\S+)\\[(?<event_id>(?:[+-]?(?:[0-9]+)))\\]\\s+Request starting HTTP/(?<http_version>(?:(?:(?:[+-]?(?:[0-9]+(?:\\.[0-9]+)?|\\.[0-9]+))))) (?<method>\\b\\w+\\b) (?<scheme>\\S+)://(?<host>\\b(?:[0-9A-Za-z][0-9A-Za-z-]{0,62})(?:\\.(?:[0-9A-Za-z][0-9A-Za-z-]{0,62}))*(?:\\.?|\\b))(?<path>\\S+)$"), "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" => "%{NOTSPACE:level}: %{NOTSPACE:category}\[%{INT:event_id:integer}\]\s+Request starting HTTP/%{NUMBER:http_version} %{WORD:method} %{NOTSPACE:scheme}://%{HOSTNAME:host}%{NOTSPACE:path}" }
    tag_on_failure => [ "_grokparsefailure" ]
  }

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