[HAProxy]: Fix parsing of logs containing <BADREQ> in the request line

[hellqvio86]

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

[shmsr]

Thank you for fixing the issue as I was about to say that you have to handle and not BADREQ

[ishleenk17]

Thanks for adding tests.

[shmsr]

@hellqvio86 Let's not "Update branch" again and again, let us wait for all CI checks to finish; otherwise it will take a lot of time. Let's wait for this one and when buildkite/integrations is done, do merge it. Also it is set to Auto Merge, no need to Update Branch then.

Just wait the CI checks to finish, and it would merge on its own.

[hellqvio86]

@shmsr buildkite/integrations has been stuck in one pending check for over three weeks now, anything I can do? 🙂

[shmsr]

@shmsr buildkite/integrations has been stuck in one pending check for over three weeks now, anything I can do? 🙂

This is weird. I am sorry I did not see this before. Let me get this checked today. I have re-run the jobs; let's see.

[shmsr]

buildkite test it

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 5eab46d

cc @hellqvio86

[elastic-vault-github-plugin-prod]

Package haproxy - 1.17.2 containing this change is available at https://epr.elastic.co/package/haproxy/1.17.2/