Following the Correlate results with Grafana Cloud Traces documentation, I’m attempting to enable tracing for my k6 tests.
import tempo from 'https://jslib.k6.io/http-instrumentation-tempo/1.0.0/index.js';
tempo.instrumentHTTP({
propagator: 'w3c'
});
However, I’m getting the following errors when running my tests:
ERRO[0018] Failed to push trace samples to the cloud error="failed to ingest request metadatas batch: code=Unavailable, msg=connection error: desc = \"error reading server preface: http2: frame too large\"" output=cloudv2 t=2.7847398s
I discovered the K6_CLOUD_TRACES_ENABLED
environment variable via a related forums post, but setting that to true
didn’t seem to have any effect (curious that this isn’t in the document I linked above?). I’m also not aware of any proxy settings that would be blocking the endpoint referenced in the aforementioned forum post.
It’s my understanding that calling instrumentHTTP
just adds the necessary headers to the outbound HTTP requests, so I’m not sure what is attempting to be pushed to the cloud.
I’m running my tests locally, making requests to an auto-instrumented .NET service. In Grafana Cloud, I can see the traces, but the “Service” is <root span not yet received>
. My traces are being collected by a Grafana Alloy instance deployed in cluster (managed by the k8s-monitoring Helm chart) and forwarded to Grafana Cloud.