Αποτελέσματα Αναζήτησης
7 Μαρ 2018 · In Application insights i can can only see bad requests for StatusCode: 500 but 400 Bad requests gets logged as Successful requests. And also the TrackException functionality doesn't log any of the custom properties...
12 Δεκ 2016 · when trying to call application insights api service with this url it gave me 400 Bad request. https://api.applicationinsights.io/beta/apps/appID/events/pageViews?timespan=P30D& $filter=contains (pageView/url,'valid-url')&$count=true.
23 Ιουλ 2018 · I have also returned 400+ http status code from web api action method, filter and delegate handler. In each case, in application insights failure section's Top 3 response codes section, the status code is enlisted.
31 Ιαν 2024 · You can correlate failed requests with exceptions and other events on both the client and server so that you can quickly diagnose the causes. In this article, you'll learn how to set up exception reporting, report exceptions explicitly, diagnose failures, and more.
21 Ιουν 2022 · Start timestamp and response code can make it like a real request and different response code, for example 400 and 500 for failed requests can help when we want to identify different failure reasons.
12 Δεκ 2014 · The Application Insights HTTPModule captures server side Request telemetry, and it also captures any unhandled exceptions when the HTTPResponse has status code 400 and above.
28 Ιουν 2018 · ApplicationInsights SDK does not read request/response bodies and never logs them, i.e. there is no 'standard' way to achieve it. Depending on your code you may just call TelemetryClient.TrackTrace (body) from your controller where you actually read request stream so you don't have to read it twice.
