[HAProxy] Fix the Grok pattern for parsing TCP logs

[devamanv]

Proposed commit message

The PR contains changes to fix the Grok Pattern for parsing the HAProxy TCP logs. Currently, the Grok patterns in the ingest pipelines don't conform to the official TCP log format. The change is in the existing Grok pattern to add some optional fields, as well some sample raw logs for the ingest pipeline tests.

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.

Author's Checklist

• Grok pattern is able to parse the TCP log format
• Pipeline tests pass

How to test this PR locally

• Clone the integrations repository
• Install elastic-package locally
• Spin up an elastic stack using elastic-package
• Run elastic-package test pipeline -v from the integrations/packages/haproxy directory

Related issues

• Closes Fix TCP Logs Grok pattern for HAProxy Integration package #8125

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-10-26T12:43:41.656+0000

• Duration: 16 min 52 sec

Test stats 🧪

Test	Results
Failed	0
Passed	37
Skipped	0
Total	37

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (1/1)	💚
Files	100.0% (1/1)	💚 3.837
Classes	100.0% (1/1)	💚 3.837
Methods	90.476% (19/21)	👎 -1.636
Lines	97.238% (176/181)	👍 8.644
Conditionals	100.0% (0/0)	💚

[ishleenk17]

haproxy log format is only TCP? Or is it one of them?

[devamanv]

@ishleenk17 HAProxy supports multiple log formats, TCP is just one of them.

[aliabbas-elastic]

Testing Details

Test Case Scenarios

Test Case Summaries	Status
Verify by ingesting a log matching the TCP log format according to official documentation	Pass 💚
Check that the TCP logs are getting ingested when the optional fields are not present	Pass 💚
Verify that all the fields are getting mapped with their respective fields with correct type of the fields	Pass 💚
Verify that there are no conflicting fields after upgrading the package and ingesting TCP logs	Pass 💚
Verify that the visualizations are loading properly under the "[Logs HAProxy] Overview" dashboard after ingesting TCP Logs	Pass 💚

[HGS9761]

It is cristal clear!

[ishleenk17]

Looks good!

[elasticmachine]

Package haproxy - 1.10.1 containing this change is available at https://epr.elastic.co/search?package=haproxy

[HGS9761]

It is still not OK!
It still does not match the missing format

I suggested a new GROK pattern

#6605