Dapr and .NET Aspire - A New Era for Observability
summary
Demo shows a .NET Aspire app extended with two branches (Dapr CLI and Aspire integration), running sidecars and apphost via dotnet run, sending OpenTelemetry traces to New Relic and using a local Kafka broker for publish/subscribe with a poison/dead-letter topic for failed messages. Observability surfaces include correlated traces, logs and a developer dashboard; Dapr 1.14 uses OpenTelemetry for tracing and metrics are slated to migrate to OpenTelemetry in 1.15 (Dec 2024); custom attributes include end_user_id and order_id and reveal ~200 error occurrences.
AI-written summary · about
chapters (13)
- 0:00Dapr and .NET Aspire intro
- 1:04Dapr solves dev challenges
- 2:51OpenTelemetry future standard
- 7:28What .NET Aspire brings
- 9:55Demo setup overview
- 13:47Running app and dashboard
- 15:13Analyzing traces in New Relic
- 18:25Tracing Kafka scenario
- 20:30Custom trace attributes value
- 21:54Diagnosing errors with user data
- 24:46Adding OpenTelemetry conventions
- 25:07Future of OpenTelemetry + Dapr
- 26:32Q&A
related talks
02h 33m.NET Aspire: Let's build a cloud application with baked in observability
10mIntroducing .NET Aspire: Revolutionizing Cloud-Native Development
54mKeynote: Introducing .NET Aspire – Cloud Native Development for .NET
48mKeynote: Introducing .NET Aspire – Cloud Native Development for .NET
01h 14mEffortless Distributed Systems With .NET Aspire
01h 08mCode to cloud with .NET Aspire
46mDemystify cloud-native development with .NET Aspire
01h 19mAsk Me Anything - Demystify Cloud-Native Development with .NET Aspire