Reasoning:

• Patch-level upgrade, but introduces new optional configuration that affects metric label sets and defaults. Code changes are advisable to expose/configure these options and keep docs/tests in sync.

What changed between 2.7.6 and 2.7.8:

• New Prometheus metrics configuration options:
  • extra_resource_labels (target_info)
  • extra_span_resource_labels (span metrics), with a non-empty default set:
    • k8s.cluster.name
    • k8s.namespace.name
    • service.version
    • deployment.environment
• Behavior: default span metrics now include those resource labels when present in OTEL_RESOURCE_ATTRIBUTES, increasing label cardinality.

Evidence (from this PR’s docs and changelog):

• CHANGELOG: “Update Beyla component to 2.7.8.”
• Docs updated to include new options and defaults:

  extra_resource_labels: List of OTEL resource labels to include on target_info.
  extra_span_resource_labels: List of OTEL resource labels to include on span metrics.
  Default: ["k8s.cluster.name", "k8s.namespace.name", "service.version", "deployment.environment"]
  

Code updates required (and already included in this PR):

• Add the new fields to the component config schema and pass-through to Beyla’s Prometheus config.
• Adjust tests to reflect new defaults.

Minimal code diffs to adopt 2.7.8 and surface new options:

• Schema additions:

--- a/internal/component/beyla/ebpf/args.go
+++ b/internal/component/beyla/ebpf/args.go
@@ -117,6 +117,8 @@ type Metrics struct {
 	Instrumentations                []string `alloy:"instrumentations,attr,optional"`
 	AllowServiceGraphSelfReferences bool     `alloy:"allow_service_graph_self_references,attr,optional"`
 	Network                         Network  `alloy:"network,block,optional"`
+	ExtraResourceLabels             []string `alloy:"extra_resource_labels,attr,optional"`
+	ExtraSpanResourceLabels         []string `alloy:"extra_span_resource_labels,attr,optional"`
 }

• Wiring to Prometheus config:

--- a/internal/component/beyla/ebpf/beyla_linux.go
+++ b/internal/component/beyla/ebpf/beyla_linux.go
@@ -444,6 +444,12 @@ func (args Metrics) Convert() prom.PrometheusConfig {
 		p.Instrumentations = args.Instrumentations
 	}
 	p.AllowServiceGraphSelfReferences = args.AllowServiceGraphSelfReferences
+	if args.ExtraResourceLabels != nil {
+		p.ExtraResourceLabels = args.ExtraResourceLabels
+	}
+	if args.ExtraSpanResourceLabels != nil {
+		p.ExtraSpanResourceLabels = args.ExtraSpanResourceLabels
+	}
 	return p
 }

• Tests updated to assert defaults and pass-through:

--- a/internal/component/beyla/ebpf/beyla_linux_test.go
+++ b/internal/component/beyla/ebpf/beyla_linux_test.go
@@ -821,16 +821,37 @@ func TestConvert_Prometheus(t *testing.T) {
 		Features:                        []string{"application", "network"},
 		Instrumentations:                []string{"redis", "sql"},
 		AllowServiceGraphSelfReferences: true,
+		ExtraResourceLabels:             nil,
+		ExtraSpanResourceLabels:         []string{"service.version"},
 	}
@@
 	expectedConfig.AllowServiceGraphSelfReferences = true
+	expectedConfig.ExtraSpanResourceLabels = args.ExtraSpanResourceLabels
@@
+	args = Metrics{
+		Features:                        []string{"application", "network"},
+		Instrumentations:                []string{"redis", "sql"},
+		AllowServiceGraphSelfReferences: true,
+		ExtraResourceLabels:             []string{"service.version"},
+	}
@@
+	expectedConfig.ExtraResourceLabels = args.ExtraResourceLabels
+	expectedConfig.ExtraSpanResourceLabels = []string{"k8s.cluster.name", "k8s.namespace.name", "service.version", "deployment.environment"}

Operational consideration:

• If you rely on strict label sets, note the added default extra_span_resource_labels can increase metric cardinality. You can explicitly set extra_span_resource_labels (including to []) to control this.

No other breaking API changes were identified for this bump.

Summary:

• The replace directive is updated from v1.3.7 to v1.3.10.
• No code changes in this repository were required; the PR contains no import or usage changes tied to this bump.

Notes:

• This module is commonly used transitively by Beyla. With no direct APIs referenced in this repo (no related diffs), the upgrade is non-impacting for Alloy’s code.
• Run CI/tests to validate runtime behavior as usual.

Changelog reference:

• No breaking API changes were surfaced in this PR; upgrade appears to include fixes/improvements only. No code modifications in Alloy were necessary.