Add components for supporting APM functions

[lahsivjar]

What does this PR do?

Adds the following component to support https://github.com/elastic/opentelemetry-dev/issues/372:

• lsmintervalprocessor
• elastictraceprocessor
• signaltometricsconnector - replaces both spanmetricsv2 and count connector

* [spanmetricsconnectorv2](https://github.com/elastic/opentelemetry-collector-components/tree/main/connector/spanmetricsconnectorv2) - this component will be removed in favor of a new component soon * [countconnector](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/connector/countconnector)

Why is it important?

Required for https://github.com/elastic/opentelemetry-dev/issues/372

Related issues

Closes https://github.com/elastic/opentelemetry-dev/issues/390

[mergify]

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

• backport-./d./d is the label to automatically backport to the 8./d branch. /d is the digit

[mergify]

backport-v8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

[lahsivjar]

This is blocked by dependency upgrade PRs, there are some dependency issues with EA - some dependencies are on v0.109.0 whereas others at v0.110.0. Even the latest update PR doesn’t upgrade all of them.

[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 add-new-components upstream/add-new-components
git merge upstream/main
git push upstream add-new-components

[elasticmachine]

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

[rogercoll]

LGTM, this will unblock 8.16 Auto-instrumentation testing.

[lahsivjar]

I am at a loss here on what is failing in the pipeline and the logs are not very helpful. Can someone point me in the correct direction or give me a clue?

[lahsivjar]

(windows-amd64-2022-fleet-privileged) Test output (sudo) (stdout): === Failed
  | >>> (windows-amd64-2022-fleet-privileged) Test output (sudo) (stdout): === FAIL: testing/integration TestFleetManagedUpgradePrivileged (246.47s)
 

Looks like this is the culprit... not sure if it is related to my changes. I have triggered a retry 🤞

[rogercoll]

@lahsivjar Seems the CI succeed after the retry, is there any other blocker?

[lahsivjar]

@rogercoll No blockers but require reviews from the codeowners (merging is currently blocked).

[pchila]

There's just a small inconsistency for one indirect otel-collector dependency, looks good otherwise

[lahsivjar]

There's just a small inconsistency for one indirect otel-collector dependency, looks good otherwise

Good catch! It looks like collector-components has some pending PRs for component updates. Let me merge those and bump the version.

[lahsivjar]

We already have the replacement for spanmetricsconnectorv2 merged and ready to be released. Pausing this PR for a bit to add that component.

UPDATE: Done!

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube