tag:support.appharbor.com,2010-11-23:/discussions/problems/82749-healthmonitoring-trace-events-not-written-to-appharbor-logAppHarbor: Discussion 2016-06-05T04:20:02Ztag:support.appharbor.com,2010-11-23:Comment/400179982016-06-02T06:45:58Z2016-06-02T06:45:58ZhealthMonitoring trace events not written to appharbor log<div><p>Hi Roger,</p>
<p>AppHarbor can only log unhandled exceptions emitted by the
application and the test error page you linked to is actually
handling the exception; In all likelyhood it's being handled by the
<code>HandleErrorAttribute</code> filter, which by default will
show the error message. Take a look <a href="https://support.appharbor.com/discussions/problems/79944-error-an-error-occurred-while-processing-your-request#comment_38688924">
at my response in this discussion</a> for more information.</p>
<p>With regards to the Health monitoring/tracing configuration I
took a look at the <code>web.config</code> and noticed that the
trace event provider configuration appears includes an HTML encoded
line feed. I'm not sure if this is accepted, but you might want to
try and remove it. Here's the relevant element (note the encoded
value after the type declaration): <code><add
name="TraceEventProvider"
type="System.Web.Management.TraceWebEventProvider,&#xA;
System.Web,Version=4.0.0.0,
Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" /></code></p>
<p>If that doesn't help it'd be great if you could try and push a
build that doesn't include the listener configuration (that
configures indentation and adds/removes listeners).</p>
<p>Best,<br>
Rune</p></div>runetag:support.appharbor.com,2010-11-23:Comment/400179982016-06-04T17:25:00Z2016-06-04T17:25:00ZhealthMonitoring trace events not written to appharbor log<div><p>Thanks for your help Rune. Working now.</p>
<blockquote>
<blockquote>
<p>AppHarbor can only log unhandled exceptions emitted by the
application and the test error page you linked to is actually
handling the exception</p>
</blockquote>
</blockquote>
<p>This was useful in explaining why I wasn't seeing exceptions
under Errors.</p>
<p>It also helped me figure out why my exception was not appearing
in the AH<br>
log session — my mistake: Locally I was running, well
locally, and my<br>
mode was not set, defaulting to RemoteOnly. This is used by<br>
the HandleErrorAttribute filter telling it to not handle my local
requests.<br>
End result: locally my exception was not handled and so was traced
by<br>
healthMonitoring, while remotely (hosted on AH) my exception was
handled,<br>
and therefore was not traced by healthMonitoring.</p>
<p>(line break in config and trace listener config I think not a
problem).</p>
<p>thanks again.<br>
Roger</p></div>rgrmrtntag:support.appharbor.com,2010-11-23:Comment/400179982016-06-05T04:20:00Z2016-06-05T04:20:00ZhealthMonitoring trace events not written to appharbor log<div><p>Hi Roger,</p>
<p>OK great, thanks for the feedback and I'm glad to hear you
figured out a solution!</p>
<p>Best,<br>
Rune</p></div>rune