microsoft / microsoft/ApplicationInsights-JS

[BUG] Documentation and functionality does not match with what is on Microsoft's website

Open
#1,797 10 comments 0 reactions 0 assignees View on GitHub
documentation
Dominant language
TypeScript
Stars
685
Forks
261
Avg merge
21h 33m
Merged PRs (30d)
5

Description

**Description/Screenshot**
I am trying to implement the change that Microsoft brought out of the discontinuation of Instrumentation Key and use Connection String instead. On https://docs.microsoft.com/en-us/azure/azure-monitor/app/javascript it shows the Connection String field is required. But on your documentation it shows Instrumentation Key is still required and when I downloaded and tried

**Steps to Reproduce**
Download package
Set the config with just connectionstring: 'you connection string'
on applicationInsight.loadAppInsights(); it errors saying 'InstrumentationKey is require.'

**Expected behavior**
InstrumentationKey is not required and should work without InstrumentKey and can work with only ConnectionString

**Additional context**

Contributor guide

Open the contributing guide

Research direction

Read the package's configuration handling around applicationInsights.loadAppInsights() and compare its required-field behavior with Microsoft's JavaScript documentation. Reproduce the issue with only connectionstring set, then verify that the documentation and runtime behavior agree and that the existing instrumentation-key path remains covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, typescript
Domain
observability
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.