## Go compile time instrumentation Przemysław Delewski February 18, 2025 Warsaw, Poland ## Agenda 1. Short bio 2. Observability domain 3. OpenTelemetry 4. History of OpenTelemetry go compile time time instrumentation 5. Demo 6. Some code walkthrough 7. Current status and future 8. Questions ## Short bio I’m a founding engineer at Quesma, where we work on a data gateway. Before that, I spent member of the OpenTelemetry Go compile-time instrumentation project https://github.com/open-telemetry/community/blob/main/projects/go-compile-instrumentation.md ![Image](/uploads/documents/3/d/9/6/3d

## Zero instrumentation monitoring with your first steps in eBPF eBPF Summit ## What will we be doing?  ## How are we going options make it easier: ☐ First approach: C, LLVM/CLANG, tc ☐ Second approach: gobpf, bcc - Non-instrumentation monitoring 

iOS, Android, WASM $ ^{*} $ ) Hybrid profiling capabilities (sampling and/or instrumentation) (CPU and GPU instrumentation) Tracing capabilities (values, messages, plots, allocations, ...) Hassle-free Linux, macOS, iOS, Android, WASM $ ^{*} $ ) Hybrid profiling capabilities (sampling and/or instrumentation) Tracing capabilities (values, messages, plots, allocations, ...) Free and Open source PAY Linux, macOS, iOS, Android, WASM $ ^{*} $ ) Hybrid profiling capabilities (sampling and/or instrumentation) Tracing capabilities (values, messages, plots, allocations, ...) Free and Open source VISA

iOS, Android, WASM $ ^{*} $ ) Hybrid profiling capabilities (sampling and/or instrumentation) (CPU and GPU instrumentation) Tracing capabilities (values, messages, plots, allocations,...) Hassle-free Linux, macOS, iOS, Android, WASM $ ^{*} $ ) Hybrid profiling capabilities (sampling and/or instrumentation) Tracing capabilities (values, messages, plots, allocations, ...) Free and Open source ! Linux, macOS, iOS, Android, WASM $ ^{*} $ ) Hybrid profiling capabilities (sampling and/or instrumentation) Tracing capabilities (values, messages, plots, allocations, ...) Free and Open source VISA

see how AddressSanitizer works behind the scenes (compiler and ASan runtime) and analyze the instrumentation impact, both in perf and memory footprint. We’ll examine a handful of examples diagnosed by ASan impact: depending on tool, from 2x up to 10x) extra-memory usage (for memory related tools/instrumentation), 2x or more sometimes difficult to map error reports into source code for Release/optimized impact: depending on tool, from 2x up to 10x) extra-memory usage (for memory related tools/instrumentation), 2x or more sometimes difficult to map error reports into source code for Release/optimized

baseUnit: String?): String { return ... } } Spring Boot also configures built-in instrumentation that you can control through configuration or dedicated annotation markers. ##### 13.6.2. Supported events. meter names. ## Task Execution and Scheduling Metrics Auto-configuration enables the instrumentation of all available ThreadPoolTaskExecutor and ThreadPoolTaskScheduler beans, as long as the underlying which is derived from the bean name. ## Spring MVC Metrics Auto-configuration enables the instrumentation of all requests handled by Spring MVC controllers and functional handlers. By default, metrics

RuntimeWiringConfigurer, JsonComponent, Converter, GenericConverter, DataFetcherExceptionResolver, Instrumentation and GraphQLSourceBuilderCustomizer. Regular @Component and @ConfigurationProperties beans are baseUnit: String?): String { return ... } } Spring Boot also configures built-in instrumentation that you can control through configuration or dedicated annotation markers. ##### 13.7.2. Supported events. meter names. ## Task Execution and Scheduling Metrics Auto-configuration enables the instrumentation of all available ThreadPoolTaskExecutor and ThreadPoolTaskScheduler beans, as long as the underlying

RuntimeWiringConfigurer, JsonComponent, Converter, GenericConverter, DataFetcherExceptionResolver, Instrumentation and GraphQLSourceBuilderCustomizer. Regular @Component and @ConfigurationProperties beans are baseUnit: String?): String { return ... } } Spring Boot also configures built-in instrumentation that you can control through configuration or dedicated annotation markers. ##### 13.7.2. Supported events. meter names. ## Task Execution and Scheduling Metrics Auto-configuration enables the instrumentation of all available ThreadPoolTaskExecutor and ThreadPoolTaskScheduler beans, as long as the underlying

RuntimeWiringConfigurer, JsonComponent, Converter, GenericConverter, DataFetcherExceptionResolver, Instrumentation and GraphQLSourceBuilderCustomizer. Regular @Component and @ConfigurationProperties beans are baseUnit: String?): String { return ... } } Spring Boot also configures built-in instrumentation that you can control through configuration or dedicated annotation markers. ##### 13.7.2. Supported events. meter names. ## Task Execution and Scheduling Metrics Auto-configuration enables the instrumentation of all available ThreadPoolTaskExecutor and ThreadPoolTaskScheduler beans, as long as the underlying

RuntimeWiringConfigurer, JsonComponent, Converter, GenericConverter, DataFetcherExceptionResolver, Instrumentation and GraphQLSourceBuilderCustomizer. Regular @Component and @ConfigurationProperties beans are baseUnit: String?): String { return ... } } Spring Boot also configures built-in instrumentation that you can control through configuration or dedicated annotation markers. ##### 13.7.2. Supported events. meter names. ## Task Execution and Scheduling Metrics Auto-configuration enables the instrumentation of all available ThreadPoolTaskExecutor and ThreadPoolTaskScheduler beans, as long as the underlying