[edot] add prometheus remote write receiver

[VihasMakwana]

What does this PR do?

Add prometheus remote write receiver to EDOT

Why is it important?

Allows users of Prometheus to forward data to Elastic through the EDOT Collector without requiring them to adapt their collection architecture.

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

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 @VihasMakwana? 🙏
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.

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b prw-receiver upstream/prw-receiver
git merge upstream/main
git push upstream prw-receiver

[ycombinator]

@VihasMakwana Could you please add back and populate the "Why is it important?" section of this PR's description, especially there is no issue related to this PR either? Thanks.

[AlexanderWert]

@VihasMakwana Could you please add back and populate the "Why is it important?" section of this PR's description, especially there is no issue related to this PR either? Thanks.

added the "Why is it important" section above

[theletterf]

@AlexanderWert I take this won't be a Core component. Any annotation we'd like to add to this one in components.yml?

[ycombinator]

LGTM but not sure if @theletterf's question is blocking or not.

[theletterf]

@ycombinator It's not blocking, just nice to have :) We can proceed from my point of view if we deem this is complete.

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b prw-receiver upstream/prw-receiver
git merge upstream/main
git push upstream prw-receiver

[VihasMakwana]

/test

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 71db82e

History

• 💔 Build #32606 failed b732c95
• 💔 Build #32598 failed b732c95
• 💔 Build #32593 failed bdf81aa
• 💔 Build #32592 failed e33c935
• 💔 Build #32532 failed 7fe41a9

cc @VihasMakwana

[VihasMakwana]

@theletterf I think we should be okay without any additional annotations. For eg. postgresqlreceiver is a part of EDOT, but it is not a core component and not mentioned in components.yml. The prometheus remote write receiver is also an "extended" component and will not be a part of core list.

[VihasMakwana]

@ycombinator Could I get an approval if you're around? The CI is finally green 😄