
Marc Sanmiquel developed and maintained core profiling and observability features across the grafana/pyroscope and grafana/alloy repositories, focusing on data ingestion, symbolization, and end-to-end reliability. He engineered robust backend components in Go, introducing HTTP ingestion endpoints, system library symbolization using the Lidia binary format, and Prometheus-style relabeling for profile data. Marc improved CI/CD pipelines, enhanced cross-platform compatibility, and delivered detailed documentation to streamline onboarding and integration. His work addressed data validation, error handling, and performance profiling, resulting in more accurate dashboards and scalable profiling workflows. The depth of his contributions ensured production-grade reliability and maintainability throughout the stack.

October 2025 performance snapshot: Delivered core build hygiene, release readiness, and data ingestion robustness, with improved data fidelity and faster deployment readiness.
October 2025 performance snapshot: Delivered core build hygiene, release readiness, and data ingestion robustness, with improved data fidelity and faster deployment readiness.
September 2025 deliverables focused on improving the accuracy, reliability, and performance of Grafana profiling workflows across three repositories. The work enhances diagnosability for developers and operators, improves data integrity in flamegraph visuals, and sets the foundation for scalable rate-based metrics in the backend and UI. Highlights include a backend-driven rate calculation overhaul for cumulative profiles with synchronized step sizes in comparisons, a targeted fix to flamegraph totals rate calculation in the Pyroscope integration, and robust HasFunctions flag handling for profiles with mixed symbolization to preserve location accuracy and accurate flamegraphs.
September 2025 deliverables focused on improving the accuracy, reliability, and performance of Grafana profiling workflows across three repositories. The work enhances diagnosability for developers and operators, improves data integrity in flamegraph visuals, and sets the foundation for scalable rate-based metrics in the backend and UI. Highlights include a backend-driven rate calculation overhaul for cumulative profiles with synchronized step sizes in comparisons, a targeted fix to flamegraph totals rate calculation in the Pyroscope integration, and robust HasFunctions flag handling for profiles with mixed symbolization to preserve location accuracy and accurate flamegraphs.
August 2025 performance summary focused on strengthening data reliability, expanding visualization capabilities, and improving user-facing documentation across Grafana Pyroscope, Alloy, and Grafana repos. Key work targeted data integrity, better metrics, and clearer integration guidance to deliver tangible business value for dashboards and platform adoption.
August 2025 performance summary focused on strengthening data reliability, expanding visualization capabilities, and improving user-facing documentation across Grafana Pyroscope, Alloy, and Grafana repos. Key work targeted data integrity, better metrics, and clearer integration guidance to deliver tangible business value for dashboards and platform adoption.
July 2025 (Month: 2025-07) — Maintained telemetry reliability by updating dependency protocol compatibility for the EBPF-otel example in grafana/pyroscope. Upgraded opentelemetry-ebpf-profiler, otel-collector, and the Pyroscope image to address upstream changes, restoring data collection compatibility and preventing disruption across the telemetry stack. The change was delivered via a single commit that encapsulates the dependency updates, reducing risk and ensuring continuous observability for users.
July 2025 (Month: 2025-07) — Maintained telemetry reliability by updating dependency protocol compatibility for the EBPF-otel example in grafana/pyroscope. Upgraded opentelemetry-ebpf-profiler, otel-collector, and the Pyroscope image to address upstream changes, restoring data collection compatibility and preventing disruption across the telemetry stack. The change was delivered via a single commit that encapsulates the dependency updates, reducing risk and ensuring continuous observability for users.
June 2025 monthly summary highlighting key features delivered, major bugs fixed, and overall impact across grafana/pyroscope and grafana/alloy. Key accomplishments include implementing system library symbolization in the profiling read path (debuginfod client, Lidia format) to improve symbol resolution and profiling analysis, ensuring robustness by skipping already-symbolized locations to preserve existing symbols, and graduating pyroscope.receive_http and pyroscope.relabel to GA with updated docs for production readiness and reliability. These workstreams deliver measurable business value by improving profiling fidelity, data integrity, and production robustness.
June 2025 monthly summary highlighting key features delivered, major bugs fixed, and overall impact across grafana/pyroscope and grafana/alloy. Key accomplishments include implementing system library symbolization in the profiling read path (debuginfod client, Lidia format) to improve symbol resolution and profiling analysis, ensuring robustness by skipping already-symbolized locations to preserve existing symbols, and graduating pyroscope.receive_http and pyroscope.relabel to GA with updated docs for production readiness and reliability. These workstreams deliver measurable business value by improving profiling fidelity, data integrity, and production robustness.
Monthly summary for 2025-05 focusing on feature delivery and data quality improvements in grafana/pyroscope. Implemented a new symbolization diagnosability label and updated the Alloy example configuration to demonstrate release pinning and dynamic data organization. These efforts enhance data reliability, observability, and maintainability, and prepare the groundwork for scalable symbol resolution and configurable ingestion pipelines.
Monthly summary for 2025-05 focusing on feature delivery and data quality improvements in grafana/pyroscope. Implemented a new symbolization diagnosability label and updated the Alloy example configuration to demonstrate release pinning and dynamic data organization. These efforts enhance data reliability, observability, and maintainability, and prepare the groundwork for scalable symbol resolution and configurable ingestion pipelines.
April 2025 monthly summary focusing on Grafana/pyroscope contributions. Delivered two core features that improve symbolization, ingestion metadata, and build reliability. No major bug fixes documented for this period; work emphasized feature delivery and quality assurance. Overall impact: Enhanced data quality and observability by enabling Lidia-based Go profile symbolization and explicit signaling for partially symbolized profiles, which reduces ambiguity in ingestion pipelines and accelerates debugging and instrumented data interpretation.
April 2025 monthly summary focusing on Grafana/pyroscope contributions. Delivered two core features that improve symbolization, ingestion metadata, and build reliability. No major bug fixes documented for this period; work emphasized feature delivery and quality assurance. Overall impact: Enhanced data quality and observability by enabling Lidia-based Go profile symbolization and explicit signaling for partially symbolized profiles, which reduces ambiguity in ingestion pipelines and accelerates debugging and instrumented data interpretation.
March 2025 monthly summary focused on data integrity, security maintenance, and label validation across grafana/pyroscope and grafana/alloy. Key deliverables include preventing duplicate labels in data ingestion, introducing label validation with unit tests, and upgrading dependencies to address CVEs, delivering business value through improved data quality, security posture, and maintainability.
March 2025 monthly summary focused on data integrity, security maintenance, and label validation across grafana/pyroscope and grafana/alloy. Key deliverables include preventing duplicate labels in data ingestion, introducing label validation with unit tests, and upgrading dependencies to address CVEs, delivering business value through improved data quality, security posture, and maintainability.
February 2025 performance summary focused on strengthening observability, cross-platform reliability, and developer experience across Grafana Alloy and Pyroscope projects. Key results include new Pyroscope relabeling capabilities, cross-OS stability improvements, and clearer CPU profiling guidance, driving better data quality, faster incident response, and higher customer value.
February 2025 performance summary focused on strengthening observability, cross-platform reliability, and developer experience across Grafana Alloy and Pyroscope projects. Key results include new Pyroscope relabeling capabilities, cross-OS stability improvements, and clearer CPU profiling guidance, driving better data quality, faster incident response, and higher customer value.
January 2025 monthly summary for grafana/pyroscope focused on CI/CD reliability and OpenTelemetry-related guidance. Delivered stability-enhancing CI changes, improved local OTLP/Tempo configuration, and corrected documentation to reduce confusion around OpenTelemetry support. These efforts improved automation reliability, faster feedback, and developer productivity.
January 2025 monthly summary for grafana/pyroscope focused on CI/CD reliability and OpenTelemetry-related guidance. Delivered stability-enhancing CI changes, improved local OTLP/Tempo configuration, and corrected documentation to reduce confusion around OpenTelemetry support. These efforts improved automation reliability, faster feedback, and developer productivity.
December 2024 monthly summary for Grafana Pyroscope and Alloy repositories. Focused on expanding observability capabilities, stabilizing CI/CD, and improving data labeling/naming to support scalable dashboards and Tempo integrations.
December 2024 monthly summary for Grafana Pyroscope and Alloy repositories. Focused on expanding observability capabilities, stabilizing CI/CD, and improving data labeling/naming to support scalable dashboards and Tempo integrations.
November 2024 saw cross-repo delivery across Grafana Alloy and Grafana Pyroscope that materially improved data enrichment, profiling workflows, and developer experience. Key features include external labels support for AppendIngest in pyroscope.write, a stability-focused documentation overhaul for receive_http, and expanded Alloy integration guidance. The month also delivered end-to-end demonstration capabilities with a rideshare profile ingestion app and OpenTelemetry eBPF profiler examples, plus FlameQL parser improvements to broaden app-name ergonomics. These efforts collectively reduce onboarding time, enable richer observability, and accelerate end-to-end profiling pilots.
November 2024 saw cross-repo delivery across Grafana Alloy and Grafana Pyroscope that materially improved data enrichment, profiling workflows, and developer experience. Key features include external labels support for AppendIngest in pyroscope.write, a stability-focused documentation overhaul for receive_http, and expanded Alloy integration guidance. The month also delivered end-to-end demonstration capabilities with a rideshare profile ingestion app and OpenTelemetry eBPF profiler examples, plus FlameQL parser improvements to broaden app-name ergonomics. These efforts collectively reduce onboarding time, enable richer observability, and accelerate end-to-end profiling pilots.
Concise monthly summary for 2024-10 focused on grafana/alloy. Delivered Pyroscope HTTP Ingestion Endpoint enabling ingestion and forwarding of Pyroscope profiles over HTTP, extended pyroscope.write to handle incoming profile data via HTTP POST, and updated CHANGELOG.md and documentation. No major bugs fixed this period in relation to the new feature.
Concise monthly summary for 2024-10 focused on grafana/alloy. Delivered Pyroscope HTTP Ingestion Endpoint enabling ingestion and forwarding of Pyroscope profiles over HTTP, extended pyroscope.write to handle incoming profile data via HTTP POST, and updated CHANGELOG.md and documentation. No major bugs fixed this period in relation to the new feature.
Overview of all repositories you've contributed to across your timeline