Skip to content

Conversation

@hellqvio86
Copy link

@hellqvio86 hellqvio86 commented Nov 28, 2025

Current HAProxy integration do not support BADREQ, e.g:

"message": "127.0.0.1 [29/Sep/2025:08:33:00.277] f_foobar~ f_foobar/<NOSRV> -1/-1/-1/-1/0 400 0 - - CR-- 8/1/0/0/0 0/0 \"<BADREQ>\""

Adding a guard to GROK-parsing of haproxy.http.request.raw_request_line so it does not run for BADREQ.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

How to test this PR locally

Related issues

Screenshots

@hellqvio86 hellqvio86 marked this pull request as ready for review November 28, 2025 11:48
@hellqvio86 hellqvio86 requested a review from a team as a code owner November 28, 2025 11:48
@andrewkroh andrewkroh added Integration:haproxy HAProxy Team:Obs-InfraObs Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations] labels Nov 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Integration:haproxy HAProxy Team:Obs-InfraObs Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants