What could cause the stream analytics job to go into degraded status?
Following is the screenshot. I have checked each Input and Output - all it says is Additional details are temporarily unavailable
No output produced. In Azure portal checked the audit logs - nothing helpful there. How do we troubleshoot this?
If there is no additional information in the logs, please open support ticket or send subscription id to askasa#microsoft.com
Related
I am trying to graph the IncomingLogEvents or IncomingBytes or PutLogEvents or whatever metric that would help me understand which log streams are the ones sending the most logs to a specific log group in Cloudwatch
Did anyone run into this? I was able to graph the IncomingBytes metric for log groups but not for logstreams within those log groups
I have several containers in my environment and each container sends their logs through a separate log stream within the same log group
Suddenly costs started rising due to errors on the containers and was able to identify which log group is causing it but I cannot find a way to identify which logstream is
Docker does not help either and of course I can check container logs but I want to be able to alert on an increase, hence detect when a logstream is sending more logs than normal as it will alert me on cost increase as on errors
I know I can monitor log errors with other log centralization tools or even with CloudWatch but need to know from Cloudwatch which container is the one sending the highest amount of logs
There used to be a metric that got deprecated and I cannot find any documentation that would help me use whatever metric or solution they replaced it with
The metric was "storedBytes": 0 which from now on, and since deprecation it will always be 0
Thank you for any help that you can provide me with and hope this question help others achieve their goals too
Eu
Cloudwatch dashboard but can make it for log groups only
this question is mostly for DevOps experts, in app insights.
So I found I have an issue on my app, it seems some threads are being created and not released, causing the thread count to increase and ending at some point in the "CGI error", which usually happens when you exceed your quota in any resource.
I already identified the exceeded resource is thread count thanks to this Metrics option, which gives you a graphical representation on how it is being consumed (and released when an app restart happens)
I would like to have some details on this, not the grouped information but the actual information that is giving this graph, any lead would help me to understand which place is creating and not releasing threads, a namespace, a class name, anything.
Is there another place where I could get this information in a very detailed way? AppInsight queries seems to lack this metric.
Thanks in advance.
AFAIK there is no direct way to do this. The only way that I can see is by adding custom logging inside your application and sending the logs to a Log Analytics Workspace.
Inside your function app in the portal go to 'Diagnostic settings' and connect to your log analytics workspace (if it doesn't exist create one).
Inside the log analytics workspace you will find your custom logs either under a 'Custom Logs' tab or under 'Application Insights' tab, after this find the correct field and parse, something like:
customMetrics
| extend d=parse_json(customDimensions)
| extend processSessionId=d.processSessionId
For Azure related topics there is also a decent Q&A platform here:
https://learn.microsoft.com/en-us/answers/products/azure?product=all
For KSQL this is a handy page:
https://learn.microsoft.com/en-us/azure/data-explorer/kusto/query/tutorial?pivots=azuremonitor
Hope this helps somewhat
I am using the logging extension framework in an asp.net core function app. I have following code:
log.LogMetric("TESTER", 0);
log.LogInformation($"{{logTypeStart}}: {service.GetType()}", logTypeStart);
await service.Run(log);
log.LogInformation($"{{logTypeEnd}}: {service.GetType()}", logTypeEnd);
In log analytics I query following:
AppTraces
AppMetrics
The LogInformation logs traces to the AppTraces in Log Analytics. But AppMetrics does not provide any results. Any pointers on how to troubleshoot this?
I tested it with Function V3, the metrics can be sent to both AI and the connected Log Analytics.
Please check the things below:
1.Test your code first locally(please follow this thread to see how azure function and application insights works locally), and see if the metrics can be shown in visual studio output. The screenshot is as below:
2.Please make sure the Azure log Analytics is actually connected with the AI you're using.
3.In Azure log Analytics, when query in AppMetrics table, make sure you have selected the proper time range. Here is the screenshot of my metrics:
Please let me know if any more issues.
In Worklight v6.1, analytics search view has "contextual search". It runs a new search that will return events that occurred in the same time frame. This is useful for trouble shooting of fatal or error logs.
In MFP Foundation v7.0, I see just "Download all logs for this device". It's tough to find related events.
Does MFP Foundation the have same function? If not, is there any way to run similar search?
It seems I should change my question more specifically.
In the analytics 7.0 console, it seems we can limit the logs only by date. Is there any way to limit the logs by minute?
In the analytics 7.0 console you can go to the search tab. There you can search on client logs or server logs. For client you have the option to filter on keywords, application, environment, level, packages, and date range. For server you can filter on keywords, server, level, and date range.
Seems like contextual search is mostly just find your error and put in the date range to limit the logs.
You can submit request for enhancements at https://developer.ibm.com/mobilefirstplatform/help
My work flow is showing error while run, I dont know how to see the error description
somebody please tell me how to see the error
Look your logs with ULS Viewer. You can filter message level by click the icons in the middle. This can tell you what is going on inside SharePoint.
Look into SharePoint's ULS logs. You can change the granularity of information being logged from the Central Administration. However, errors such as unhandled exceptions are usually logged by default anyway.