[receiver/gelfreceiver] Added Support for GELF log receiver.

[BharatKJain]

Description:

Added support for GELF based logs - please read this document to understand GELF implementation.

Tremor's implementation for GELF receiver

Otel-collector's GELF implementation document: https://docs.google.com/document/d/1P9JcrXrORqI0wsnRgrcUroluutf3rVrcUCIgLeSpFm0/edit?usp=sharing

Link to tracking Issue: #33861

Testing:

• Tested the functionality of the code locally.
• Will create the unit-tests for it.

Documentation: Work-in-progress.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: BharatKJain / name: Bharat Kumar Jain (8eb1579, b101d65, 986db9e, c5fcf42, ef3b178, 682d179, 046f1b1, 885e2d4, f04bfc4, 41e0463)

[djaglowski]

In order to accept a new component you must formally propose it in an issue and find a sponsor.

[BharatKJain]

In order to accept a new component you must formally propose it in an issue and find a sponsor.

@djaglowski I don't have a sponsor, is it possible for you to help with that part? or is there a process to get sponsor, then please share the readme/doc for it?

I know about the list of sponsors mentioned here: Link - but how do I ask someone to become sponsor/reviewer for this PR? I guess it's voluntary so I cannot really ask randomly.

Also there's a Slack thread running for it, we can communicate there as well: thread link

[djaglowski]

I don't have capacity to voluntarily sponsor any additional components. Hopefully someone else is interested. Otherwise, you can always host the component elsewhere and others can still build it into their collectors using the Collector Builder.

[BharatKJain]

@djaglowski Instead of creating a separate receiver, if I add this as a part of UDP receiver then will that be okay in terms of sponsorship as you're the contributor? GELF will be like a CODEC.

[djaglowski]

I don't believe GELF support should be a concern of the UDP receiver.

[github-actions]

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

[hughesjj]

I don't see any tests, could you please add some to ensure the receiver works as expected?

[github-actions]

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

[BharatKJain]

I don't see any tests, could you please add some to ensure the receiver works as expected?

@hughesjj I tried talking to folks in SIG otel-collector meeting, they said that we need sponsor for this PR and that it won't be accepted unless there's someone sponsoring this, so before I spend more effort on it - wanted to know if you would be able to sponsor this PR or get this accepted given that all comments are fixed?

I don't want my efforts to go into vain. 😞

(Also I didn't realize there were more comments, sorry for the late response, missed notifications on it.)

[atoulme]

Suggested change

	return nil, fmt.Errorf("missing required parameter 'listen_address'")
	return nil, errors.New("missing required parameter 'listen_address'")

[BharatKJain]

I am not sure but if you check ../udp/config.go, they are using fmt...I didn't wanted to diverge from it, let me know your thoughts.

[github-actions]

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

[BharatKJain]

• Added the suggested fixes, please re-check once.
• Added unit-test, will add more in sometime

Let me know if there's anything else!

[github-actions]

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