docs: screenshot do trace distribuído no README

[thomasmoreira]

Screenshot do killer detail

Adiciona a captura real do trace distribuído no dashboard do .NET Aspire ao README — o artefato mais convincente do lab.

Uma request GET /storefront/{id} aparece como um único trace cruzando os serviços:
GET /storefront (gateway) → HTTP GET → GET /products/{id} (catalog) → redis GET + postgresql + redis SETEX → HTTP GET → GET /price/{id} (pricing).

Recursos: 5 · Profundidade: 4 · Spans: 8 · ~36ms. Capturado num run real (dotnet run --project src/AppHost), com tráfego gerado no gateway.

Summary by CodeRabbit

• Documentation
  • Added visual documentation of distributed tracing across the system architecture. The new example illustrates how a real request flows through multiple interconnected services including the API Gateway, Catalog service, and data storage layers. This provides insight into system interactions and helps visualize end-to-end request propagation patterns.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 50265e41-e7a9-4d40-b6dd-df09896e3986

📥 Commits

Reviewing files that changed from the base of the PR and between 04ed0ca and f44abfc.

⛔ Files ignored due to path filters (1)

• docs/images/distributed-trace.png is excluded by !**/*.png

📒 Files selected for processing (1)

• README.md

---

📝 Walkthrough

Walkthrough

README.md is enhanced with a new distributed trace screenshot in the "O killer detail — trace distribuído" section. The image illustrates how a single GET /storefront/{id} request flows as a distributed trace across the Gateway, Catalog, Redis/Postgres, and Pricing services.

Changes

Documentation Update

Layer / File(s)	Summary
Distributed Trace Screenshot README.md	New image and caption added to the distributed trace section showing a real GET /storefront/{id} request traced across Gateway → Catalog → Redis/Postgres → Pricing services.

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A screenshot worth a thousand words so fine,
The trace flows through in one clear line,
From Gateway's gate to Pricing's call,
Distributed tracing captures it all! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and accurately describes the main change: adding a screenshot of a distributed trace to the README documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/trace-screenshot

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}