elastic / elastic/integrations

[haproxy]: Truncated log lines break pipeline

Open
#14,345 1 comment 0 reactions 0 assignees View on GitHub
Integration:haproxy needs:triage Stalled Team:Obs-InfraObs
Dominant language
Handlebars
Stars
333
Forks
647
Avg merge
3d 4h
Merged PRs (30d)
209

Description

### Integration Name

HAProxy [haproxy]

### Dataset Name

haproxy.log

### Integration Version

1.17.0

### Agent Version

8.18.3

### Agent Output Type

elasticsearch

### Elasticsearch Version

8.18.3

### OS Version and Architecture

Ubuntu 22.04.5 LTS (x86_64)

### Software/API Version

haproxy 2.4.24-0ubuntu0.22.04.2

### Error Message

error.message: cannot access method/field [ip] from a null def reference

### Event Original

Jun 27 08:33:05 host01.examp.le haproxy[3118780]: 123.45.123.45:57196 [27/Jun/2025:08:33:04.851] http-in~ be_knweb12/knweb12 0/0/1/450/451 301 3181 - - ---- 69/64/0/0/0 0/0 {www.examp.com} "GET /?within=x%3C/k&custom_klass=x%3C/k&Galerie=x%3C/k&listing_category=x%3C/k¬icesGrid-dir=x%3C/k&xlr=x%3C/k&qsd=x%3C/k&nian=x%3C/k&fullview=x%3C/k&EA=x%3C/k&paginacao=x%3C/k&reset_filter=x%3C/k&bfg=x%3C/k&$original_url=x%3C/k&group_ids=x%3C/k&jobKind=x%3C/k&krf=x%3C/k&edit_individual_id=x%3C/k&bf_idx=x%3C/k&action_todo=x%3C/k&fokategoria=x%3C/k&tfz=x%3C/k&SCCRoutingCode=x%3C/k&wlh=x%3C/k&cust_id=x%3C/k&ooh=x%3C/k&repDgs=x%3C/k&showTxtTermin=x%3C/k&XID=x%3C/k&enmse_av=x%3C/k&amea=x%3C/k&vxv=x%3C/k&categoryno=x%3C/k&pathc=x%3C/k&SERVICE=x%3C/k&zql=x%3C/k&showsearch=x%3C/k&rxm=x%3C/k&go_city=x%3C/k&nse=x%3C/k&OE=x%3C/k&selCard=x%3C/k&Article_id=x%3C/k&t6=x%3C/k&avk=x%3C/k&blog-page=x%3C/k&startsz=x%3C/k&FY=x%3C/k&sref_id=x%3C/k&srcCruiseDurationMin=x%3C/k&unc=x%3C/k&xwz=x%3C/k&namefrom=x%3C/k&catnew_id=x%3C/k&cio=x%3C/k&ayw=x%3C/k

### What did you do?

Default integration usage. No special config

### What did you see?

No extracted data like source.address or http.version

### What did you expect to see?

Extracted informations like source.address or http.version

### Anything else?

The reason looks pretty clear to me. The Log line seems truncated by haproxy and therefore the GROK pattern did not match anymore.

Suggested solution: separate some extractions to extra pipeline steps with their own failure handling to get at least SOME information.

For example separate the extraction of the (user controlled) URL Path information extraction as this could be truncated. (in my case, the HTTP version is missing for example)

PS.: The Log line was generated by a security scanning solution or "researcher" most likely...

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.