---
title: "Discussion on \"Plugin logging in Dataverse: ILogger + Application Insights\" | Hashnode"
description: "Discussion on \"Plugin logging in Dataverse: ILogger + Application Insights\". Dataverse plugins have two logging destinations: the built-in PluginTraceLog table and Azure Application Insights via the ILogger interface. Neither on its own is enough in production. The combination, wired correctly, is what lets us debug"
url: "https://hashnode.com/posts/plugin-logging-in-dataverse-ilogger-application-insights/6a127bc902c892c4d522d7ca"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Plugin logging in Dataverse: ILogger + Application Insights](https://sapotacorpvn.hashnode.dev/plugin-logging-in-dataverse-ilogger-application-insights?utm_source=hashnode&utm_medium=feed)

Dataverse plugins have two logging destinations: the built-in PluginTraceLog table and Azure Application Insights via the ILogger interface. Neither on its own is enough in production. The combination, wired correctly, is what lets us debug

May 24 · 6 min read · sapotacorpvn.hashnode.dev  
Read the article

-   [#power-platform](https://hashnode.com/tag/power-platform)
-   [#dataverse](https://hashnode.com/tag/dataverse)
-   [#plugin](https://hashnode.com/tag/plugin)
-   [#application-insights](https://hashnode.com/tag/application-insights)
-   [#observability](https://hashnode.com/tag/observability)

## Written by

[SapotaCorp](https://hashnode.com/@sapotacorpvn)

@sapotacorpvn · Hanoi, Vietnam

  
[View profile](https://hashnode.com/@sapotacorpvn)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.