Skip to main content
Gleap allows you to monitor network requests for a better understanding of what’s happening within your app.

​
Configure network logs

Managed .NET has no global HTTP interception, so — unlike the native SDKs — only traffic routed through a Gleap handler is captured. Add the handler returned by CreateNetworkLoggingHandler() to the HttpClient instances you want to monitor. backend is the ManagedBackend returned by the platform attach call (for Windows: GleapMessenger.Backend).
You can toggle capture at runtime:

​
Filtering network logs

Gleap allows you to strip specific key/value pairs from network logs. This lets you remove sensitive data like tokens, passwords or usernames before anything leaves the client. Log in to the Gleap dashboard, open the visual widget configurator, and enable the network log filters option (in the advanced options tab). Every key you add is loaded with the widget configuration; before sending a feedback item the SDK strips all matching key/value pairs from the request headers, JSON header payloads and JSON response bodies.

​
Set filter with code

​
Blacklisting URLs

If a network request matches an entry in the blacklist, it won’t be included in the network logs. You can maintain the list in the dashboard under Developer options, or set it by code.