I'm calling both logEvent and logError, but only see the former in the Flurry console. Do errors show up somewhere else?
Flurry.logError("DataUpdater_Error", message: causeOfError, error: nil)
Flurry.logEvent("DataUpdater_Event")
In the portal I'm looking under "Events". Are errors somewhere else? Or is it just not working?
Flurry's new UI does not have all the features supported yet. I assume they will add these soon...Specific Crashes and user-defined Errors don't seem to be there right now.
Related
I am getting the below exception and would like to know what is the "SystemTracker" that is mentioned in the exception. Also, the namespace in the message entity and in the System Tracker are different. Why could those be different? One has "stage1c" and the other is "1a". If 1c is a failover for "1a", then could it log exception like this?
Azure.Messaging.ServiceBus.ServiceBusException: Put token failed. status-code: 404, status-description: The messaging entity 'sb://c0000hwabt-stage1c.servicebus.windows.net/becm.job.summary.response' could not be found. To know more visit https://aka.ms/sbResourceMgrExceptions. TrackingId:3123b33a-315a-40d5-a1e7-243b2611335e_G9, SystemTracker:c0000hwabt-stage1a.servicebus.windows.net:becm.job.summary.response, Timestamp:2022-10-20T15:56:04. (MessagingEntityNotFound)
These are set by the Service Bus service for use with correlating logs and troubleshooting from the service-side. They're helpful information to include when opening a support ticket but are otherwise not useful. Your application should treat them as opaque values and not assume any meaning to the client.
We call REST based APIs hosted by Azure Functions and fail to implement a consistent error handling supporting App Insights and wonder what can be done about it:
If we don't handle exceptions of the function, then App Insights
reports a 'failure', but the service returns only the the error code to the caller, but no error content:
Hence, the client receives a 500 and thats it.
If we handle the exception and log it (to AppInsights) then App Insights stops reporting a 'failure' hence monitoring on function level is broken. We can query for the exception, but they are out-of-context (i.e. we can see the exception by a custom query only) and we don't know which function is impacted actually.
How to marry up the two needs:
Let the function fail so that AppInsights reports the failure (and monitor can alert)
Return a bit more meaningful error message to the caller than 500.
Example on how it looks in AppInsights:
Exception is visible on the Exceptions tab, but the underlying operation has not failed
UPDATE:
According to Microsoft, App Insight Failures are exclusive to unhandled exceptions. Still, open whether there is a way to at least pass-through an error message.
If don't handle exceptions of the function, then App Insights reports a 'failure', returns the error code, but no error content. Hence, the client receives a 500 and thats it.
App Insights doesn't return anything, so what do you mean with returns the error code?
If we handle the exception, LOG it (to AppInsights), return simple error message in code 500, then App Insights doesn't log this as 'failure' hence monitoring is not possible.
Can you show how you do the logging? Because as soon as you log an exception using App Insights you should see it under failures.
This should work:
try
{
...
}
catch(Exception e)
{
logger.LogError(e, e.Message);
return httpRequest.CreateResponse(HttpStatusCode.InternalServerError, e.Message);
}
I created a topic "Messages" in my service bus instance, and added a new subscription to it. I can send messages to this topic and the Azure Function v3 trigger is activated just fine. The message is received and displayed in an instant.
When I add an sql filter to filter messages for a subscription it is not working anymore.
What I did so far.
Created an sql filter in the azure portal:
sys.Label = "Test" -> Not working as no messages are received anymore, even though I verified that the Label attribute is set.
sys.Label != "Test" Not working as no messages are received anymore, even though I verified that the Label attribute is set and not matching "Test"
sys.To = "Test" -> Not working, no messages are received. Verified that the messages contain the To member.
sys.Label is not Null -> This is strangely working.
What am I doing wrong here?
As stated in the comment, the solution to this question can be found in the Microsoft Q&A.
To prevent a loss of this solution I am going to post it here too:
The SQL filter value should be in single quotes 'test'
Example : sys.To = 'test'
Make sure that you are defining the message system properties while
sending the message to topic.
Source
If someone is caught off guard by the red single quotes. They are just red, but don't indicate that something is wrong with it. It will just work fine.
According to documentation when trial is expired and user opens the app, a message would be shown. But my app closes after showing splash screen without any message in this case.
There is the same question on the Microsoft's forum, but I can't write anything there (it returns me unexpected error when I try to submit my question) and there is no answer.
I get the following line in my event log:
App failed with error: No applicable app licenses found. See the Microsoft-Windows-Twin/Operational log for additional information.
Additional information:
< Data Name="ErrorCode" >-1058406399< /Data >
This is Microsoft's bug and they promise to fix it. You can get more details on the msdn-forum.
I have setup Azure Diagnostics and using Trace to log any messages.
The problem is that when I go to the Azure WADLogsTable, I see that in addition to my messages there is a lot of crap that I want to eliminate.
How do I remove mesages like these?
IDependencyResolver.GetService<ASP._Page_Views_Account_Login_cshtml>() = ASP._Page_Views_Account_Login_cshtml
IDependencyResolver.GetService<System.Web.Mvc.ModelMetadataProvider>() = null
The only thing that I want to show are the things that I put there like this:
Trace.WriteLine("This is not good", "Information");
Make sure that your web.config does not contain any Trace config statements that send system messages to trace.