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.
Disable IP address collection
See original GitHub issueI’m using app insights to add telemetry to our VS Code extensions. Things work really well, but there is one issue:
How can I disable the collection of the Client IP address per event? And I guess I’d really also like to not collect City and “State or province”. I already have a filter running that I added via addTelemetryProcessor, but the envelope I get there doesn’t have those fields, they must be added at some later point in the pipeline.
I don’t want to collect that information because it potentially is user-identifying (because it would give away the client machine IP address where someone is running VS Code), so from a privacy point of view I don’t want that data, plus we also really don’t need it.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Closing this, as IP is now always sanitized to 0.0.0.0 at ingestion time (although after City/Location is extracted). Forcing a dummy IP like @Dmitry-Matveev described will disable City/Location as well.
That’s correct, in IPv4 the last octet is always removed. Similar rules are applied for IPv6 data (though with many more segments removed due to IPv6 potentially being more identifiable).
@Dmitry-Matveev Do you know if this is becoming more aggressive for further protection or if there’s a way for users to disable this collection done by our backend?