nodeshift / nodeshift/faas-js-runtime
Add support for distributed tracing
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
When a CloudEvent function receives an incoming POST from a Knative event source, the CloudEvent's distributed tracing extension is not used (probably for good reason, as it's still a bit in flux). It would be nice if this framework could examine the incoming non-CE headers to look for a trace context, and if so, propagate that context in the response.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the framework handles an incoming POST to a CloudEvent function and how it constructs the response. Read the distributed-tracing and W3C Trace Context specifications referenced in the issue, then determine how incoming non-CloudEvent headers should be recognized and propagated. Done means a valid trace context from a Knative event source is preserved in the response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100