[connector/metricsaslogsconnector] first version of metricsaslogs connector

[kyo-ke]

Description

First version of metricsaslogs connector.
this connector connect metric pipeline to log pipeline
what it do is
create LogRecord per DataPoint

attributes are mapped to

Metric Resource -> Log Resource
Metric Scope -> Log Scope
datapoint -> logrecord

Link to tracking issue

Fixes #40938

Testing

unit test with over 90% coverage

Documentation

[kyo-ke]

unit test output

$ go test -cover
{"level":"warn","msg":"Unknown metric type","type":"Empty"}
PASS
coverage: 99.2% of statements
ok github.com/open-telemetry/opentelemetry-collector-contrib/connector/metricsaslogsconnector 0.507s

[aarvee11]

@kyo-ke : Kindly visit the Contributing Guidelines found at CONTRIBUTING.md

To make things faster, find the quick fixes below, but I insist you to kindly go through the link above for a smooth process

Steps to fix all the failing checks:

1. build-and-test / check-collector-module-version (pull_request) - patch the /connector/metricsaslogsconnector/go.mod file as per the runner output from lines 94 to 143
2. build-and-test / checks (pull_request) - Run make goporto from the root of the repo and stage the changes
3. build-and-test / lint (pull_request) - Will auto resolve when all checks have passed
4. build-and-test / lint-matrix (linux, connector) (pull_request) - License generation has failed. Run make addlicense from the root of the repo and stage the changes
5. build-and-test / lint-matrix (windows, connector) (pull_request) - same as point#4 above
6. changelog / changelog (pull_request) - Changelog missing. Check the Chnagelog generation steps
7. codeowners / check-codeowners (pull_request_target) - Mention only the sponsor's github ID here. If you have not found one, follow the steps from link
8. scoped-test / scoped-tests (pull_request) - Same as Point#4

After fixing all the above, make a push to the same branch of your fork, and allow all the above checks to PASS

Cheers...

[aarvee11]

Kindly make the necessary changes, follow the steps in my comment above and also the contributing guidelienes

[kyo-ke]

@aarvee11 Thank you for he review.
I updated the PR.

[aarvee11]

@kyo-ke Please resolve the comments above that are open for the CI to kick in and finish the tests

[kyo-ke]

sure
all comments are resolved

[atoulme]

Update to latest main, then run make genotelcontribcol'. Then run ./.github/workflows/scripts/check-collector-module-version.shandmake tidylist` and push your changes.

[kyo-ke]

@atoulme Thank you for review!
PR updated

[kyo-ke]

@atoulme
should I update versions.yaml to pass the check?

[atoulme]

@atoulme should I update versions.yaml to pass the check?

CI says:

verifyAllModulesInSet failed: Module github.com/open-telemetry/opentelemetry-collector-contrib/connector/metricsaslogsconnector (defined in /home/runner/work/opentelemetry-collector-contrib/opentelemetry-collector-contrib/connector/metricsaslogsconnector/go.mod) is not listed in any module set.

Please add it to the list.

[github-actions]

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

[kyo-ke]

hello @atoulme
versions updated.
could you re-run the test ?

[github-actions]

Welcome, contributor! Thank you for your contribution to opentelemetry-collector-contrib.

Important reminders:

• Please review our Contributing Guidelines.
• Don't forget to sign the Contributor License Agreement (CLA) if you haven't already.

A maintainer will review your pull request soon. Thank you for helping make OpenTelemetry better!

[edmocosta]

Could you please update the go.mod so it uses the same collector dependencies versions other components are using. We also need to run make generate-chloggen-components to add it to the change log component list. Thanks!

[github-actions]

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

[atoulme]

I hope we get this in now. I am around to merge after CI concludes.

[otelbot]

Thank you for your contribution @kyo-ke! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out this survey. If you are getting started contributing, you can also join the CNCF Slack channel #opentelemetry-new-contributors to ask for guidance and get help.