# [[Pyroscope GitHub Integration (Grafana Pyroscope Community Call - May 2025)]] [in developer-advocacy]() ![[Pyroscope GitHub Integration (Grafana Pyroscope Community Call - May 2025)]] <iframe width="560" height="315" src="https://www.youtube.com/embed/_vQx4Bqk10o" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> Related:: "[[Christian Simon]], [[Tiffany Jernigan]]" ## Talking points [Christian's slides](https://docs.google.com/presentation/d/12kBmcTwKogV35KR-9LiYQDb0LExr-dLkPQrPkvt42XQ/edit?slide=id.g3339b29bbdb_0_10#slide=id.g3339b29bbdb_0_10) - Metrics from profiles: Function level - Example: export garbage collection profiling data for every service - Server-side symbolization, support for line numbers and inline functions - Relax label name validation to align with OTel attributes - Currently dots are converted to underscores - Yes, dashboards will need to be reconfigured. But OTLP endpoint is rarely used anyway. Breaking change but necessary and hopefully won't have a big impact. - OTel format for profiles is still changing Source code integration - formerly known as "[[GitHub]] integration" - eBPF currently not supported but it's possible and they plan to do that. - Line numbers shown is language-dependent. Only Go for now. - Maybe Java next? He's not sure and it's not set yet. - Plan: to make it GA this quarter. - Still some tweaking on offset. Sometimes they say there's CPU being used by a comment or empty space. Pyroscope OSS v2.0 - Storage v2, will be default. - Storage v1 deprecated, removed in OSS v1.0 - Currently at v1.13.4 - [[Anton Kolesnikov]] has been working on a new storage layer for the last 13 months. - They found a few limitations regarding how storage works right now. Replication Factor of 3. - They move data out of system volume storage (v1) - ingesters have last hour of profiles... to the object storage a lot faster and sooner and more compacted. We push profiles to the object store within 10 seconds. It's like a WAL in object store. - They're skipping ingester SSD storage completely. They're just going directly to object store. - UI: We are thinking of deprecating the old v0.x UI and replacing it with an embedded Profiles Drilldown app - They can't maintain the old UI so they're not sure exactly what they're going to do with the new one. Maybe just embed, maybe something else. - Clean up command line flags and public API - Diskless microservices mode - Release dashboards/alerts/runbooks - Timeline ~ Autumn 2025 - 10 people on the team. They have to pick and choose! - Function-level profiling is more something to do for profiles not really traces. It won't be seen from Tempo. %% # Text Elements # Drawing ```json {"type":"excalidraw","version":2,"source":"https://github.com/zsviczian/obsidian-excalidraw-plugin/releases/tag/2.0.25","elements":[],"appState":{"theme":"dark","gridSize":null,"viewBackgroundColor":"#ffffff"}} ``` %%