Node.js layer v0.24.0 does not work with @opentelemetry/winston-transport v0.35.0

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

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
57/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
aws, go, javascript, node.js
Ambito
backend-api-design, observability

Direzione di ricerca

Start by reading the Node.js layer's log export and instrumentation setup, then compare its OpenTelemetry log API dependencies with @opentelemetry/winston-transport 0.35.0; the issue names no source files or tests. Reproduce with the listed Lambda, Winston, and transport versions, then confirm logs export or that a clear warning appears for an unsupported version.

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

Descrizione

bug javascript

Describe the bug
We're using the nodejs-layer 0.24.0 and the @opentelemetry/winston-transport for logging.
With the recently released @opentelemetry/winston-transport 0.35.0 however, logs are no longer exported by the nodejs-layer. Previously, with @opentelemetry/winston-transport 0.34.0, this was working great.

I suppose this is with the recent switch in @opentelemetry/winston-transport 0.35.0 to use @opentelemetry/api 1.10.0. In 0.34.0, it used the dependency @opentelemetry/api-logs 0.223.0. (Note "api-logs" instead of "api")

Steps to reproduce

  1. Create an AWS Node.js 24 Lambda with the nodejs-layer 0.24.0.
  2. Install winston 3.x and @opentelemetry/winston-transport 0.35.0.
  3. Deploy some code which creates a default winston logger and produces some logs.

What did you expect to see?
I expect the nodejs-layer to export logs as it used to do.

If that is not possible because of a version mismatch, I expect to see some kind of warning/error log in CloudWatch, instead of it being silently broken.

What did you see instead?
I did not see logs being exported, neither did I get any warning/error.

Additional context
Add any other context about the problem here.

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.