I have a ASP.NET Web API controller that provides a saveAndNew operation.
This class is derived from System.Web.Http.ApiController as expected.
Application Insights is correctly configured using version 2.1.0 of the SDK and the default settings in ApplicationInsights.config.
If a request to the mentioned operation fails - for example with status code 400 - the request is recorded correctly in App Insights.
The problem is that if the operation SUCCEEDS (status code 200) nothing is recorded in Application Insights.
I've used Fiddler to see if the request is made to the App Insights track service and it is not. So the problem is not in the configuration of Application Insights on the Azure portal.
I can't figure out what is preventing ALL requests to my Web API controllers operations from being recorded.
Can anyone help?
You might want to try removing/commenting out TransferRequestHandler in ApplicationInsights.config file.
GitHub issue "REST API app can have all requests filtered out" here states that: "commenting out the one line in the ApplicationInsights.config caused successful requests to start getting logged. Web API 2 project.
<!--<Add>System.Web.Handlers.TransferRequestHandler</Add>-->
Related
I have used this https://github.com/Azure-Samples/active-directory-aspnetcore-webapp-openidconnect-v2/tree/master/2-WebApp-graph-user/2-1-Call-MSGraph,
but when I publish it to Azure I get an error after some time (probably 1 hour) with http error 500. It seems the token isn't refreshing automatically? When running the app locally it doesn't happen as often, but it have happened there as well. What can be done to fix this issue?
Redirect URIs are set as shown in the github example (https://websitename.azurewebsites.net/signin-oidc).
I have created an app in the testing project and all worked fine, now when I am trying to replicate it in the production project in Firebase, it's throwing the following error. I cannot seem to find anything related online. Any help would be appreciated. Thanks
error message
I am expecting to be able to add the web app into my project.
The Firebase support team has helped me to resolve this issue:
We need to override the bad OAuth client directly (the bad client may still exist, but will not be used for web apps anymore):
Create a new web OAuth client in Cloud Console with URIs and Authorized redirect specified (your project ID + firebaseapp.com)
In the Firebase console, Auth -> GoogleSignIn details -> Set the web client ID and secret from the new client
This worked for me.
I have multiple RESTful APIs that are hosted in azure web app / azure service plans and covered by application insights
I have setup availability tests on top of these API using application insights which when triggered call an azure function
There is an auto resolve setting for availability tests which lets your hook up alerting when the availablity issue has been resolved.
However I didn't find anything on similar lines for Failure Anomalies
Question:
How do I setup a webhook call back on azure application insight failure anomaly detection ?
I am trying to use the WorkFront API. I got the API key created and am able to create a project with a name and status. However, what we need is creation of Project Request with request type being a drop down of one of the Request Queues. Does Workfront APIs support this. If so, can anyone provide guidance on this. I went through API Basics and API Explorer and do not see any objects for Project Request under API Explorer.
I figured it out later. A project request is nothing but an issue. We just needed to use the issue API to create the project request.
I have a ASP.NET Web API controller that provides a saveAndNew operation.
This class is derived from System.Web.Http.ApiController as expected.
Application Insights is correctly configured using version 2.1.0 of the SDK and the default settings in ApplicationInsights.config.
If a request to the mentioned operation fails - for example with status code 400 - the request is recorded correctly in App Insights.
The problem is that if the operation SUCCEEDS (status code 200) nothing is recorded in Application Insights.
I've used Fiddler to see if the request is made to the App Insights track service and it is not. So the problem is not in the configuration of Application Insights on the Azure portal.
I can't figure out what is preventing ALL requests to my Web API controllers operations from being recorded.
Can anyone help?
You might want to try removing/commenting out TransferRequestHandler in ApplicationInsights.config file.
GitHub issue "REST API app can have all requests filtered out" here states that: "commenting out the one line in the ApplicationInsights.config caused successful requests to start getting logged. Web API 2 project.
<!--<Add>System.Web.Handlers.TransferRequestHandler</Add>-->