Application Insights-记录异常 [英] Application Insights - Logging exceptions

查看:95
本文介绍了Application Insights-记录异常的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在我的应用程序中为Application Insights编写了一个自定义记录器.在Azure Portal中查看App Insights时,我看不到任何异常或任何事件.这是记录器类的代码,当我调试代码时,我确实看到分配给InstrumentationKey属性的键,我在这里做错了什么主意吗?我是否需要将其他信息附加到客户端或配置?

I wrote a custom logger for Application Insights in my app. I don't see any exceptions or ANY events when viewing App Insights in Azure Portal. Here is the logger class code, when I debug the code I do see a key assigned to the InstrumentationKey property, any ideas what I am doing wrong here? Do I need to attach other info to the client or configuration?

public class AppInsightsLogger:ILogger
{
    private TelemetryClient ai;

    public AppInsightsLogger()
    {
        ai = new TelemetryClient();
        if (string.IsNullOrEmpty(ai.InstrumentationKey))
        {
            // attempt to load instrumentation key from app settings
            var appSettingsTiKey = AppSettings.InsightsKey;
            if (!string.IsNullOrEmpty(appSettingsTiKey))
            {
                TelemetryConfiguration.Active.InstrumentationKey = appSettingsTiKey;
                ai.InstrumentationKey = appSettingsTiKey;
            }
            else
            {
                throw new Exception("Could not find instrumentation key for Application Insights");
            }
        }
    }
    public void LogException(Exception ex)
    {
        ai.TrackException(ex);
    }
}

推荐答案

我创建了一个新的控制台应用程序,安装了最新的稳定的ApplicationInsights SDK,并保留了您的示例,但有一些微小但重要的区别-我要么让它等待,然后再关闭在调用TrackException或添加TelemetryClient.Flush()

I created a new Console Application, installed latest stable ApplicationInsights SDK and pretty much kept your example, with minor but important difference - I either let it wait before shutting down after calling TrackException or added TelemetryClient.Flush()

namespace logtest
{
    class Program
    {
        static void Main(string[] args)
        {
            AppInsightsLogger logger = new AppInsightsLogger();
            logger.LogException(new InvalidOperationException("Is data showing?"));

            // either wait for a couple of minutes for the batch to be sent of add ai.Flush() after ai.TrackException() to send the batch immediately
            Console.ReadLine();
        }
    }

    public class AppInsightsLogger
    {
        private TelemetryClient ai;

        public AppInsightsLogger()
        {
            ai = new TelemetryClient();
            if (string.IsNullOrEmpty(ai.InstrumentationKey))
            {
                // attempt to load instrumentation key from app settings
                var appSettingsTiKey = "<ikey>";
                if (!string.IsNullOrEmpty(appSettingsTiKey))
                {
                    TelemetryConfiguration.Active.InstrumentationKey = appSettingsTiKey;
                    ai.InstrumentationKey = appSettingsTiKey;
                }
                else
                {
                    throw new Exception("Could not find instrumentation key for Application Insights");
                }
            }
        }
        public void LogException(Exception ex)
        {
            ai.TrackException(ex);
            // ai.Flush();
        }
    }
}

首先,我可以在Visual Studio调试输出窗口中看到发送的遥测项目:

First I could see telemetry item sent in Visual Studio debug output window:

然后我可以看到遥测技术将机器留在Fiddler中,也可以看到它已被我们的数据收集端点成功接受.

Then I could see telemetry leaving my machine in Fiddler, I also could see it was successfully accepted by our data collection endpoint.

最后我可以在门户网站中看到它:

And finally I could see it in the portal:

这篇关于Application Insights-记录异常的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆