[edot] add statsD as an extended receiver

[jlind23]

What does this PR do?

Add statsD receiver to EDOT

Why is it important?

Allows users of statsD to forward data to Elastic through the EDOT Collector.

Checklist

• I have read and understood the pull request guidelines of this project.
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool
• I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Relates elastic/integrations#17109

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[mergify]

This pull request does not have a backport label. Could you fix it @jlind23? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[jlind23]

@nimarezainia @perk shall this be backported to 9.3?

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[pierrehilbert]

@jlind23 could you please update NOTICE.txt?

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: cc64200

Failed CI Steps

• Ubuntu:2404:amd64:sudo
• Win2022:sudo:install-uninstall
• Start ESS stack for FIPS integration tests

History

• 💔 Build #34322 failed 1e3d31b
• 💔 Build #34319 failed f5c07c7

cc @jlind23

[perk]

shall this be backported to 9.3?

That depends on when the StatsD input package will be available.
Will it be available on serverless before the 9.4 release?
If yes, what EDOT version serverless uses?
If 9.3 then we need to backport.

[github-actions]

@Mergifyio backport 9.2 9.3

[mergify]

backport 9.2 9.3

✅ Backports have been created

Details

• #12639 [9.2] (backport #12628) [edot] add statsD as an extended receiver has been created for branch 9.2 but encountered conflicts

Cherry-pick of 16b19fe has failed:

On branch mergify/bp/9.2/pr-12628
Your branch is up to date with 'origin/9.2'.

You are currently cherry-picking commit 16b19fe69.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   changelog/fragments/1770366462-add-statsd-receiver-to-edot-collector.yaml
	modified:   internal/edot/go.mod
	modified:   internal/edot/go.sum
	modified:   internal/edot/otelcol/components.go
	modified:   internal/pkg/otel/README.md

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   NOTICE-fips.txt
	both modified:   NOTICE.txt
	both modified:   internal/pkg/otel/testdata/all-components.yml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

• #12640 [9.3] (backport #12628) [edot] add statsD as an extended receiver has been created for branch 9.3