Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[BUG] window.appInsights.properties is marked private
See original GitHub issueDescription/Screenshot
README.md says that window.appInsights.properties.context.telemetryTrace.traceID is the way to get/set the trace ID, however the properties field is marked private in the types so I can’t access it in my code. Either it’s wrongly marked private, or I need a different way to get trace ID.
Thanks for your help! Use case is to show the trace ID in the error message that we show the user after a service call failure.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Azure Application Insights for ASP.NET Core applications
Monitor ASP.NET Core web applications for availability, performance, and usage.
Read more >Azure Application Insights not showing data - Stack Overflow
Go to Properties for the Application Insights resource and under WORKSPACE there is a Change workspace link. Thank you for this answer though, ......
Read more >microsoft/applicationinsights-properties-js - Yarn
Fast, reliable, and secure dependency management.
Read more >Application Insights – Part 2 - Shiv Shankar Kumar
If you have not checked that out then you can read about it here. ... There are two ways, you can log to...
Read more >Custom Events and Metrics :: Application Insights (5 of 6)
ObjectiveThis course demonstrates the processes for configuring a web application to use Application Insights for performance tracking, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
There was an issue with the way this value was propagated to the snippet, which I’ve fixed with the #1236 PR, this will be included in the next release
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.