---
title: "Discussion on \"Observability in .NET Microservices: Seeing What's Actually Happening\" | Hashnode"
description: "Discussion on \"Observability in .NET Microservices: Seeing What's Actually Happening\". The hardest incidents I've dealt with weren't the ones with obvious causes. They were the ones where a request slowed down somewhere across four or five services, and nobody could say exactly where, b"
url: "https://hashnode.com/posts/observability-in-net-microservices-seeing-what-s-actually-happening/6a756f3ed2c0e64826b71f94"
---

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

Discussion

# [Observability in .NET Microservices: Seeing What's Actually Happening](https://tundehub.dev/observability-in-net-microservices-seeing-what-s-actually-happening?utm_source=hashnode&utm_medium=feed)

The hardest incidents I've dealt with weren't the ones with obvious causes. They were the ones where a request slowed down somewhere across four or five services, and nobody could say exactly where, b

Aug 7 · 5 min read · tundehub.dev  
Read the article

## Written by

[Esanju Babatunde](https://hashnode.com/@Teesofttech)

@Teesofttech

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

## Responses 1

Markdown supported · ⌘↵ to post

[Julian Neagu](https://hashnode.com/@julianneagulab)

[Aug 12](https://hashnode.com/posts/observability-in-net-microservices-seeing-what-s-actually-happening/6a756f3ed2c0e64826b71f94/comment/6a7c252cf76e955c0f3ad4ff)

Health checks are one of those things people leave until later. Then the first outage happens and suddenly they become the most useful page in the whole app.
