[traces] spanmetrics and AutomaticLogging unable to get otel span tags as a metric/log tag

[daper]

Grafana agent version: v0.26.1

I have configured the spanmetrics and automatic_logging features for the traces agent. With dimensions and span_attributes respectively.

I am trying to record the otel.library.name. Any other tag is recorded successfully in both pipelines (logs and metrics), for example net.peer.name.

When I inspect the span, its tags for otel including otel.library.name are there but when it comes to log them it fails silently.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had any activity in the past 30 days. The next time this stale check runs, the stale label will be removed if there is new activity. The issue will be closed in 7 days if there is no new activity. Thank you for your contributions!

[daper]

not-stale

[ptodev]

Hello 👋 Would you mind sharing your Agent config please, with secrets redacted? Also, would you mind confirming whether otel.library.name is a resource attribute or a span attribute? Is suspect it is a resource attribute. In that case, I think it should be listed under process_attributes of the automatic_logging config.

There is a more detailed flow example in the docs for otelcol.connector.spanlogs, which is going to be released in the next version of Grafana Agent as an alternative to static mode's automatic_logging processor.

[rfratto]

Hi there :wave:

On April 9, 2024, Grafana Labs announced Grafana Alloy, the spirital successor to Grafana Agent and the final form of Grafana Agent flow mode. As a result, Grafana Agent has been deprecated and will only be receiving bug and security fixes until its end-of-life around November 1, 2025.

To make things easier for maintainers, we're in the process of migrating all issues tagged variant/flow to the Grafana Alloy repository to have a single home for tracking issues. This issue is likely something we'll want to address in both Grafana Alloy and Grafana Agent, so just because it's being moved doesn't mean we won't address the issue in Grafana Agent :)