Azure / Azure/azure-functions-host

Enable Auto Dependnecy Tracking on Javascript worker

Open
#5,901 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
2k
Forks
482
Avg merge
2d 12h
Merged PRs (30d)
38

Description

#### What problem would the feature you're requesting solve? Please describe.
A customer want to track dependency telemetry on the Azure Functions with node. Even if we configured AppInsights by our selves, I doesn't inject the header related correlation.

#### Describe the solution you'd like
Currently, we can get TraceContext on the context object. I suppose, `setCurrentContext()` method might be required for tracking dependency telemetry for this class.
https://github.com/microsoft/ApplicationInsights-node.js/blob/5bf1848be22418b74e67a422f6daed651314c2a5/AutoCollection/CorrelationContextManager.ts#L60

The ideal behavior is , dependency http outgoing request is automatically tracked with injecting correlation header info according to the config of Distributed Tracing on functions host side.

#### Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
If it is not tracked, I'd like to configure AppInsigths by my self and can track the dependency telemetry with correlation.

#### Additional context
Add any other context or screenshots about the feature request here.
This issue might be related.
https://github.com/microsoft/ApplicationInsights-node.js/issues/585

Contributor guide

Open the contributing guide

Research direction

Start by locating the JavaScript worker entry point that exposes TraceContext on the context object, then compare it with CorrelationContextManager.ts in ApplicationInsights-node.js. Confirm the desired behavior by checking that outgoing HTTP dependency telemetry injects correlation headers according to the Functions host distributed-tracing configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, javascript, node.js
Domain
backend, cloud, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.