You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Debugging memory issues using process dumps is invaluable, as no other tool provides the same level of insight. However, heap dumps often contain sensitive data, making it difficult for customers in on-premise environments to share them for troubleshooting.
Is there currently a way to anonymize data, particularly strings, within a dump? If not, would it be possible to introduce an anonymization option in dotnet-dump or dotnet-monitor to address this concern? This would help users diagnose memory issues while ensuring sensitive information remains protected.
Looking forward to any suggestions or potential solutions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Debugging memory issues using process dumps is invaluable, as no other tool provides the same level of insight. However, heap dumps often contain sensitive data, making it difficult for customers in on-premise environments to share them for troubleshooting.
Is there currently a way to anonymize data, particularly strings, within a dump? If not, would it be possible to introduce an anonymization option in dotnet-dump or dotnet-monitor to address this concern? This would help users diagnose memory issues while ensuring sensitive information remains protected.
Looking forward to any suggestions or potential solutions.
Beta Was this translation helpful? Give feedback.
All reactions