chore: bump opentelemetry-ebpf-instrumentation to 0.1.25

[github-actions]

opentelemetry-ebpf-instrumentation Bump Summary

Version: 0.1.25

Charts

Chart	Status	Notes
otel-integration	✅ OK

Changelog

Changes from opentelemetry-ebpf-instrumentation 0.1.25:

• [Feature] Enable peer name resolution by default with name_resolver.sources: [k8s, rdns]: peer/host IPs resolve to names from the Kubernetes informer metadata and from the DNS answers OBI already captures. Both sources are in-memory and generate no lookups; the active dns source stays disabled since it issues blocking PTR queries from the span pipeline

Changes from opentelemetry-ebpf-instrumentation 0.1.24:

• [Feature] Add a presets.runtimeMetrics preset, exporting application runtime metrics (Go memory limits, completed GC cycles, GOMAXPROCS and GOGC; HotSpot JVM heap used/committed/limit; Node.js event loop). It is enabled by default for every language OBI supports, adding the application_runtime metrics feature. presets.runtimeMetrics.languages narrows it to a list of detected languages, named as OBI names them, by giving every discovery.instrument selector a language-scoped copy carrying the feature, so it never widens the set of instrumented processes; a selector that already sets languages is left untouched. Note that Node.js runtime metrics are collected by injecting a JavaScript agent into every discovered Node.js process through the Node.js inspector, and that agent writes progress lines to the process' own stdout: languages: [go, java] leaves Node.js processes alone, and nodejs.enabled: false turns the injector off entirely
• [Change] The runtimeMetrics.go.enabled / runtimeMetrics.jvm.enabled values are replaced by presets.runtimeMetrics, and runtime metrics are now exported by default. runtimeMetrics.jvm.samplingInterval moves to presets.runtimeMetrics.jvm.samplingInterval. The previous per-language split was cosmetic: both flags mapped to the single application_runtime feature, and the jvm_runtime_metrics.enabled key the chart rendered does not exist in the OBI configuration
• [Feature] Add a presets.logEnricher preset, injecting the active trace context into the logs written by the instrumented processes. It is disabled by default; enabling it enriches the workloads selected by config.data.discovery.instrument, and presets.logEnricher.plainText.enabled: false keeps the enrichment to JSON logs only, leaving plain-text output untouched
• [Fix] Enabling stats no longer drops application metrics. The chart appended stats to an empty feature list, rendering features: [stats], which replaced the OBI default of [application]

---

Generated by bump-otel-collector-version.sh

Source: coralogix/opentelemetry-helm-charts#513

✅ Changelog: Includes all entries from current to target version.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}