Mohammed Abdessetar Elyagoubi
Software Engineer | OpenTelemetry Java Contributor | Developer Tooling & Observability
Rabat, Morocco
Actions
I’m a software engineer at Sofrecom, part of Orange Group, working mainly with Java, backend systems, and developer tooling. I contribute to OpenTelemetry Java, with four merged changes spanning metrics, configuration, and HTTP transport behavior.
I’m especially interested in the parts of observability that break quietly: missing telemetry, misleading signals, SDK behavior, and the low-level details developers usually only meet when something goes wrong.
Outside my day job, I experiment with open source, browser automation, security, and developer tools. I like taking confusing bugs apart, tracing them down to the implementation, and turning that investigation into something other developers can actually use.
Area of Expertise
Topics
When Observability Lies: Debugging Real Bugs in OpenTelemetry Java
A metric silently loses data. A sampler setting is accepted but ignored. An HTTP sender has a failure mode you would not expect from infrastructure code.
In this Java-focused talk, we debug real issues from OpenTelemetry Java: asynchronous-metric data loss, ignored sampler configuration, and HTTP telemetry-export reliability or security problems. We will trace the relevant SDK code, reduce each failure, and look at how fixes and tests address them.
The goal is not to teach OpenTelemetry setup or Spring Boot instrumentation. It is to show Java developers how small implementation and configuration bugs inside a dependency can undermine the telemetry they trust, and how to investigate infrastructure libraries instead of treating them as black boxes. The examples are grounded in issues and fixes I contributed to OpenTelemetry Java. Basic Java knowledge is enough; no OpenTelemetry experience is required.
Delete Your Selectors: Automating the Web Through the Accessibility Tree
Browser automation usually depends on CSS selectors, XPath, or test IDs.
But browsers already build another representation of the page: the accessibility tree.
So I am trying something weird: automate websites using only that tree.
No CSS selectors. No XPath. No test IDs.
Instead of looking for `#checkout-button`, the tool looks for “button named Checkout.”
In this talk, I will build and break that idea on real interfaces, including bad ARIA, fake buttons, dynamic content, and other cases where the browser's semantic view falls apart.
The goal is not to prove this is better automation.
The goal is to see how far we can push the browser before it stops understanding the page.
Debugging the Debugging Tools: Inside OpenTelemetry Java
Your Java service is running. The dashboard looks normal. But some telemetry never arrives, and nothing clearly tells you why.
This session goes inside OpenTelemetry Java to examine how telemetry can fail in less obvious ways: asynchronous metric collection, configuration that does not behave as expected, and HTTP sending paths where reliability depends on details below application instrumentation. We will use real OpenTelemetry Java contribution work to show how to trace a suspicious symptom through SDK code, tests, configuration, and data flow.
This is not an OpenTelemetry introduction, a dashboard tour, or a vendor observability pitch. It is a Developer Tools session about debugging the tool that developers rely on to debug everything else.
Attendees will learn a practical way to reason about missing or unexpected telemetry, identify which layer to inspect, read unfamiliar Java infrastructure code, and turn a failure hypothesis into a focused test and fix.
Mohammed Abdessetar Elyagoubi
Software Engineer | OpenTelemetry Java Contributor | Developer Tooling & Observability
Rabat, Morocco
Actions
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top