grafana/pyroscope：README 來源編輯指南

grafana/pyroscope 的 README 將專案描述為「Continuous Profiling Platform. Debug performance issues down to a single line of code」。本文只整理倉庫可直接核對的內容，不把 star、Fork 或宣傳語當成品質證明。README 在「🎉 Announcement: Pyroscope 2.0 is here!」下寫到：Pyroscope 2.0 makes the new v2 architecture the default. Profiles are written directly to object storage, removing the need for in-memory ingesters and local disks - simplifying operations and lowering resource usage at scale.。這說明的是專案邊界，不是已完成的生產驗證。

從 README 的「What is Grafana Pyroscope?」與相關條目，可以先判斷它是否處理你的實際問題：Reactive: Quickly resolving incidents with line-level detail and debugging active CPU, memory, or I/O bottlenecks.。若需求不同，不應只因專案熱度就採用。本文保留原始專案名、命令與元件名，方便回到一手來源核對。 README 另外列出一項可核對的資訊：Proactive: Reducing resource consumption, improving application performance, or preventing latency issues.。這類原文條目可用來設計試跑步驟，但不能取代實際環境測試。

README 將運作方式分散在「What is Grafana Pyroscope?」等段落。可確認的線索包括：Grafana Pyroscope is a continuous profiling platform designed to surface performance insights from your applications, helping you optimize resource usage such as CPU, memory, and I/O operations.。本文不把未寫出的架構、效能或安全邊界補成結論；真正的執行鏈仍要配合目錄、設定檔與版本標籤檢查。

第一次安裝應從 README 指出的入口開始。目前可核對的命令是： docker run -it -p 4040:4040 grafana/pyroscope 如果倉庫沒有命令，本文不會自行編造步驟，而是建議先閱讀「What is Grafana Pyroscope?」，確認系統依賴、預設埠與首次初始化。

日常使用取決於專案文件。README 的「What is Grafana Pyroscope?」段落提到：Pyroscope provides powerful tools to give you a comprehensive view of your application's behavior while allowing you to drill down into specific services for more targeted root cause analysis.。設定檔、環境變數、權限與資料目錄只在來源明確時才會記錄；沒有寫出的預設值，應在測試環境驗證並保留回滾副本。 同一部分也提到：Pyroscope Server: Stores and processes profiling data and serves queries.。