[florianl]

Proposed commit message

Add new OTel profiling input integration.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

[github-actions]

✅ Vale Linting Results

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[florianl]

Friendly ping for review @elastic/integrations-triaging

[jsoriano]

LGTM as initial version.

Would it be possible to add tests?

Policy tests should be easy to add and they would be specially relevant now that we are stabilizing latest changes in Fleet for OTel integrations, and I think this one would be the first one for profiles.

[florianl]

I have skipped tests, as they fail with an error that seems unrelevant to the package:

ERROR: there was an apply error: could not add package policy "test-with-samples-per-second-profiling_otel-24460" to agent policy "test-with-samples-per-second-24460": could not create package policy (req {"name":"test-with-samples-per-second-profiling_otel-24460","description":"","namespace":"ep","policy_id":"6338e69c-3ccf-4b94-9fa5-d1cd5b29a5ba","package":{"name":"profiling_otel","version":"0.0.1"},"inputs":{"profilingreceiver-otelcol":{"enabled":true,"streams":{"profiling_otel.profilingreceiver":{"enabled":true,"vars":{"data_stream.dataset":"profilingreceiver","samples_per_second":73}}}}},"force":false}); API status code = 400; response body = {"statusCode":400,"error":"Bad Request","message":"unexpected data stream type profiles"}

This package does not set or define datastreams.

[macroscopeapp]

🟢 Low policy/test-with-samples-per-second.expected:6

The elasticsearch/componentid-0 exporter references beatsauth/default (line 6), but no extension by that name exists. The actual extension defined is beatsauth/componentid-0 (line 10), and that's what's registered in service.extensions (line 42). This mismatch causes the OpenTelemetry Collector configuration validation to fail at startup with an unknown extension reference error.

Suggested change

	authenticator: beatsauth/default
	authenticator: beatsauth/componentid-0

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file packages/profiling_otel/_dev/test/policy/test-with-samples-per-second.expected around line 6:

The `elasticsearch/componentid-0` exporter references `beatsauth/default` (line 6), but no extension by that name exists. The actual extension defined is `beatsauth/componentid-0` (line 10), and that's what's registered in `service.extensions` (line 42). This mismatch causes the OpenTelemetry Collector configuration validation to fail at startup with an unknown extension reference error.

[florianl]

@elastic/integrations-triaging is this expected?

[jsoriano]

This is expected, but for the fingerprint diff found in CI you will have to wait for a release of elastic-package with elastic/elastic-package#3467 (coming soon).

To unblock this skip the policy test by now, and we will remove the skip after releasing the next elastic-package version.

[florianl]

not sure if c5d8f8a is the correct way to skip this test. looking at other packages this seems to be the only way - didn't find documentation.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: c5d8f8a

History

• 💔 Build #41445 failed 695aae6
• 💚 Build #41040 succeeded 596e996
• 💚 Build #41038 succeeded 5d0edfa