Azure / Azure/azure-functions-nodejs-opentelemetry
Should examples use BatchSpanProcessor?
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
The ESM examples initialize things using a SimpleSpanProcessor.
The OTel documentation recommends against that for production use:
_NOTE: This SpanProcessor exports every ended span individually instead of batching spans together, which causes significant performance overhead with most exporters. For production use, please consider using the BatchSpanProcessor instead._
Contributor guide
Research direction
Locate the ESM examples that initialize SimpleSpanProcessor and read their current setup alongside the OpenTelemetry guidance quoted in the issue. Update the examples to use the recommended batching approach, then verify that the examples still initialize and run as documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability-sre
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100