Be the first to know when your microservices are having issues in Production and get everything sorted out way before your customers even start noticing.
Microservices Troubleshooting Essentials
Microservices Troubleshooting Essentials is a 29-lesson 4 hours 23 minutes self-paced course by Julio Casal. Be the first to know when your microservices are having issues in Production and get everything sorted out way before your customers even start noticing.
Course facts
- Lessons
- 29
- Duration
- 4 hours 23 minutes
- Level
- All levels
- Language
- English
- Updated
- Instructor
- Julio Casal
- Price
- Premium
Who teaches Microservices Troubleshooting Essentials? Julio Casal
Julio Casal is a US software engineer and one of the more active independent .NET / C# educators publishing course material on the modern .NET stack. His courses focus on the production-engineering side of .NET microservices and the cloud-native patterns that show up in real .NET applications running on Azure and AWS.
The course catalog covers ASP.NET Core, .NET microservices with Docker and Kubernetes, Azure cloud deployment patterns, the testing tracks, and the broader cloud-native .NET work that separates Julio's material from generic .NET tutorial content. Course material is taught at the level of a working senior .NET engineer.
The CourseFlix listing under this source carries 9 Julio Casal courses spanning that range. Material is paid and aimed at intermediate-and-up .NET developers building production microservices and cloud-native applications.
What lessons are included in Microservices Troubleshooting Essentials?
| # | Lesson Title | Duration | Access |
|---|---|---|---|
| 1 | Introduction Demo | 00:34 | |
| 2 | Introduction to Logging | 02:46 | |
| 3 | Writting logs via ILogger | 25:29 | |
| 4 | Standing up a Seq Docker container | 04:52 | |
| 5 | Sending logs to Seq in your local box | 11:39 | |
| 6 | Generalizing the Seq configuration | 09:51 | |
| 7 | Deploying Seq to Kubernetes | 07:13 | |
| 8 | Adding Seq support to the microservice helm chart | 07:26 | |
| 9 | Sending logs to Seq in AKS | 06:05 | |
| 10 | Introduction | 00:38 | |
| 11 | Introduction to Distributed Tracing | 04:33 | |
| 12 | Upgrading the Common library to MassTransit v8 | 04:25 | |
| 13 | Upgrading all microservices to MassTransit v8 | 10:47 | |
| 14 | Using OpenTelemetry to collect and export distributed traces | 14:25 | |
| 15 | Standing up a Jaeger Docker container | 04:27 | |
| 16 | Exporting distributed traces to Jaeger | 11:19 | |
| 17 | Generalizing the distributed tracing configuration | 10:38 | |
| 18 | Adding distributed tracing to all microservices | 12:43 | |
| 19 | Deploying Jaeger to Kubernetes | 13:11 | |
| 20 | Adding Jaeger support to the microservice helm chart | 05:34 | |
| 21 | Sending distributed traces to Jaeger in AKS | 07:09 | |
| 22 | Introduction | 00:44 | |
| 23 | Introduction to Monitoring | 02:44 | |
| 24 | Using OpenTelemetry to collect and export metrics | 19:51 | |
| 25 | Standing up a Prometheus Docker container | 13:02 | |
| 26 | Generalizing the monitoring configuration | 11:00 | |
| 27 | Deploying Prometheus and Grafana to Kubernetes | 16:50 | |
| 28 | Letting Prometheus discover microservices in AKS | 10:23 | |
| 29 | Getting a microservice monitored by Prometheus and Grafana in AKS | 13:06 |
Get instant access to all 28 lessons in this course, plus thousands of other premium courses. One subscription, unlimited knowledge.
Learn more about subscriptionBooks
What courses are similar to Microservices Troubleshooting Essentials?
-
Updated 1y ago.NET Diagnostics Expert
By: Sebastian SolnicaHave you ever encountered issues debugging applications in production? Or maybe spent hours trying to reproduce a bug on your local machine?27h 6m -
FreeClassicDesign Patterns in C# and .NET
By: UdemyLearn design patterns in C#. You see clear steps to use each pattern in .NET. This course helps you write clean code with proven design ideas.20h 15m5/5 -
Updated 2y ago.NET Logging Done Right: An Opinionated Approach Using Serilog
By: PluralsightEstablishing a foundational framework for logging can save hours in troubleshooting and provide valuable insights to both utilization and performance within all5h 2m