Activity overview
Latest activity by AlexanderMz
Hi @Russell D , during our tests we often see a lot of exceptions including internal unity exceptions related to illegal registrations. They are caught and suppressed internally (so we could no catch them) but they affect performance so we would like to track rate of exceptions and group them by type, i.e. unity exceptions rate, application defined exception rate, etc. We have automated performance testing framework that tests more than hundreds services per day but could not track first chance exceptions so we would like to reuse RedGate's ability to do that (Red Gate command line perf profiling is one of the steps in our testing pipeline and in case we have alert we open profiling results file and investigate it). So we actually need list of exceptions in any format (json preferable), so that we could post process them and raise alerts during automated testing if required.
/ comments
Hi @Russell D , during our tests we often see a lot of exceptions including internal unity exceptions related to illegal registrations. They are caught and suppressed internally (so we could no cat...
@JasonBock for the latter exception, find LineLevelBlacklist.xml file (%LocalAppData%\Red Gate\ANTS Performance Profiler 10\LineLevelBlacklist.xml) and put the following line there:
<assemblyName>System.Net.Http</assemblyName>
/ comments
@JasonBock for the latter exception, find LineLevelBlacklist.xml file (%LocalAppData%\Red Gate\ANTS Performance Profiler 10\LineLevelBlacklist.xml) and put the following line there:
<assemblyName...
Hi Jason, most likely your SQL server uses Windows/AD authentication. You should run you profiler under account having access to Sql.
Check "Show server options/Manually specify ASP account details" setting when starting profiling.
/ comments
Hi Jason, most likely your SQL server uses Windows/AD authentication. You should run you profiler under account having access to Sql.
Check "Show server options/Manually specify ASP account detail...
Is it possible to extract exceptions during command line profiling to a separate file?
Please see picture below. What it takes to implement feature allowing exceptions extraction to a separate file during command line profiling? Any chance this can be done in the nearest future?