feat: Update Couchbase parsers to use LoggingReceiverMacro

[dyl10s]

Description

This updates the 3 different Couchbase receivers

• General
• GOXCDR
• HTTP Access

Had to do a little bit of additional renaming here but for the most part these were all straight forward.

Related issue

How has this been tested?

Followed flow of generating golden files and checking for consistency

Checklist:

• Unit tests
  • Unit tests do not apply.
  • Unit tests have been added/modified and passed for this PR.
• Integration tests
  • Integration tests do not apply.
  • Integration tests have been added/modified and passed for this PR.
• Documentation
  • This PR introduces no user visible changes.
  • This PR introduces user visible changes and the corresponding documentation change has been made.
• Minor version bump
  • This PR introduces no new features.
  • This PR introduces new features, and there is a separate PR to bump the minor version since the last release already.
  • This PR bumps the version.

[franciscovalentecastro]

Please add a multiline log entry so we can test the "multiline parsing" functionality of this processor.

[dyl10s]

For both cases here I there are multiline entries and they seem to not be parsing. I kept them the same as they were previously and the regex looks like it matches. Do you see what the issue could be here?

[franciscovalentecastro]

Please add a multiline log entry so we can test the "multiline parsing" functionality of this processor.

[dyl10s]

@franciscovalentecastro I updated the regex here to be able to correctly capture multiple lines. I have not had to do this in the past but it seemed to be a bug with the original regex.

[franciscovalentecastro]

Re @dyl10s :

What is the reason that [\s|\S] fixes the regex for multiline parsing ? Is this specific thing for couchbase logs (e.g. trailing whitespace) ?

[franciscovalentecastro]

There is probably another bug in the transformation_test marshall / unmarshall (goccy/goyaml library) of the output goldens or maybe a side-effect of the changes in the regex parsing. I'm going to investigate the cause.

My direct understanding of the failure is that "-" is the actual that is output by the processor for the field "user", but in YAML "-" could mean a blocksequence.

transformation_test.go:389: [13:13] block sequence entries are not allowed in this context
#47 111.7                   10 |     jsonPayload:
#47 111.7                   11 |       host: couchbase.local
#47 111.7                   12 |       message: Request took 5ms
#47 111.7                 > 13 |       user: -
#47 111.7                                    ^
#47 111.7                   14 |     labels:
#47 111.7                   15 |       compute.googleapis.com/resource_name: hostname
#47 111.7                   16 |       logging.googleapis.com/instrumentation_source: agent.googleapis.com/couchbase_http_access
#47 111.7                   17 |      

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[github-actions]

Closed as inactive. Feel free to reopen if this PR is still being worked on.