microsoft / microsoft/ApplicationInsights-JS
DisableFetchTracking default with 2.8.x lead to significant Azure consumption
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 685
- Forks
- 261
- Avg merge
- 21h 33m
- Merged PRs (30d)
- 5
Description
I know it was in the release notes and we didn't fully realize the scope of the change. However, when you changed **disableFetchTracking** default to false instead of true, it lead to more than a 10x increase in logging on one of my instances. I had Ajax tracking disabled explicitly already but not this one since it was previously defaulted to false. It went a while before anyone noticed, but we're looking at a cost impact of more than $10k per month. I haven't finished full analysis but this affects us on 100+ customers of varying size. I admit we should have caught it in testing, but this change hurt.
Contributor guide
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 reading the 2.8.x release notes and tracing the implementation and tests for disableFetchTracking. Compare the default behavior with the prior release and assess the resulting fetch-tracking and logging volume. Done means the default behavior and its regression coverage prevent unintended tracking and the associated Azure consumption.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100