Diginsight.Diagnostics 3.2.5

INTRODUCTION

Diginsight telemetry provides automatic observability for dotnet applications.<br> In particular, the full application flow is made available to local text based streams such as traditional file logs, the Console Log or the Azure Streaming Log and also to remote analysis tools such as Azure Monitor and Prometheus/Grafana.

Diginsight telemetry is produced by standard ILogger<> and System.Diagnostic activity classes so it integrates (without replacing) other logging systems telemetry. Also, diginsight telemetry fully integrated with Opentelemetry and the W3C Trace Context Specification so traceids are preserved across process invocations of a distributed system.

Diginsight telemetry targets all dotnet framework versions starting from netstandard2.0.<br>Samples are available on telemetry_samples repository to demonstrate use of telemetry on .net 4.8 up to [blazor webassembly,].net6 and .net8+ assemblies. <br><br>

Articles:

• Diginsight telemetry documentation: explains diginsight telemetry concepts and how it extends ILogger<> and System.Diagnostics API.
• HOWTO - Send telemetry to the local text based streams: explores how to send diginsight telemetry to the local text based streams (eg. a local file or a AKS console log).
• HOWTO - Send telemetry to the remote analysis tools: explores how to send diginsight telemetry to the remote analysis tools (eg. Azure monitor or Prometheus and Grafana).
• HOWTO - Use diginsight telemetry with no impact on Application performance an telemetry cost: explores how we can do this ensuring no impact on application performance.