Coldstart Processor creating broken traces for cold start and next invocation

Aperta
  • Qualcosa non va?
#2,099 2 commenti 5 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
38/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
aws, nodejs
Ambito
cloud, observability

Direzione di ricerca

Inizia riproducendo lo scenario a quattro richieste con i layer Node.js e collector 0.19.0, usando la configurazione coldstart di collector.yaml mostrata. Confronta le trace risultanti e l’output del collector, incluso lo span di init della prima invocation; il lavoro è completato quando arrivano quattro trace complete e distinte e la trace coldstart include i dati di inizializzazione previsti.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug processor/cold_start

Describe the bug
I was unable to get the coldstart processor to do what is says that it does on the tin. If i submit 4 requests to a helloworld function behind an api gateway I only end up with 3 traces in my observability platform. Two of these traces will use the same internal spans, have missing spans and appears to be related to the cold start. One trace goes missing. Invocations from coldstart + 3 appear normal.

Steps to reproduce

  • Create a hello world Lambda function fronted by either a REST or HTTP api in AWS
  • Deploy the api and function with the otel collector and nodejs layers bundled with a custom collector.yaml that enables the coldstart processor. ie.
processors:
  coldstart:
  resource:
    attributes:
      - key: deployment.environment.name
        value: '${env:ENVIRONMENT_NAME}'
        action: upsert

Additional configure the collector.yaml to send to your observability platform of choice.
I had the following env variables set for the function:

      // OpenTelemetry configuration
      AWS_LAMBDA_EXEC_WRAPPER: '/opt/otel-handler',
      OPENTELEMETRY_COLLECTOR_CONFIG_URI: '/var/task/collector.yaml',
      OTEL_TRACES_SAMPLER: 'always_on',
      OTEL_PROPAGATORS: 'tracecontext,baggage',
      OTEL_LAMBDA_DISABLE_AWS_CONTEXT_PROPAGATION: 'true',
      OTEL_NODE_ENABLED_INSTRUMENTATIONS: 'aws-sdk,aws-lambda,http,undici',
      OTEL_SERVICE_NAME: serviceName,
      OPENTELEMETRY_EXTENSION_LOG_LEVEL: 'INFO',

I tried active tracing on, passthrough and off.
I tried the insights layer on and off.

  • Manually trigger a http get request to the api/function endpoint four times
  • Check traces that arrive in the observability platform

What did you expect to see?
I expected to see 4 traces arrive in my observability platform (grafana cloud). I expected the first trace that would have triggered a cold start to have a trace that includes a span for the init phase and be of a longer duration than the other three.

What did you see instead?

  • Only three traces arrived.
Image

  • One trace went missing

  • The first two traces are broken

    • trace 1
    Image
    • trace 2
    Image
    • trace 3
    Image

What version of collector/language SDK version did you use?

  • 0.19.0 (collector layer)
  • 0.19.0 (nodejs layer)

What language layer did you use?
nodejs

Additional context
I tried a few different things to try and get this to work:

  • bundling to commonjs and esm
  • using a http or rest api gateway
  • removing the batch and decouple processors
  • putting the coldstart processor first/last in order of execution
  • setting the function active tracing to on, passthrough and off.
  • removing the insight lambda layer

Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.

Lingua principale
Go
Stelle
433
Fork
249
Merge medio
1g 12h
PR unite (30g)
39

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di open-telemetry/opentelemetry-lambda

Tutte le issue di open-telemetry/opentelemetry-lambda

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.