[DEMO] The Night Before Shipping: A Sentry + OTEL Story

[smeubank]

Intro

Twas the night before shipping the last ships for our SDKs. Every developer was typing, the sound of their mechanical keyboards would keep anyone awake. If not for all the coffee and stack overflow, no way that would have made, what is sure to impress all who come this way. While the SDKs do all they were designed to do, at least to the extent that the PM wrote the user stories that is. Tech leads stand by, under the watchful eyes of so many SEs, who request, "So uh like what exactly is it that yall did here?"

The team perks up and with a sparkle in their eyes, , if this was a cartoon there would be light bulbs above their heads. "Do not fear our dear customer facing friends! We have a demo prepared and all the answers are held there within!"

The tale:

A customer is browsing for telescopes and telescope paraphernalia, finding their way to our online store.

1. The front page should load and be scrollable

• 3 - remove local #20
• 4 - currency DDLB not quite right
• BE Service Error hidden from UI #21
• 2 - Sentry artwork to FE UI #22

2. The click continue shopping and are pulled down the page to the product list

• 2 - this page load is wonky, only displays image after clicking - cool if we can identify in performance

3. Clicking a product opens that page, where they can select a quantity and add to cart

• 4 - quantity DDLB is also wonky

4. Adding to cart take us to the cart, where info is prefilled which is nice for demo purposes, then the important part "place order"

• [DEMO] Error on place order  #23

Sentry Product:

1. I would expect to find Performance events represent page load events and all requests with the FE and down stream services

• they should be connected by trace
• we can show transactions for that on the performance page and web vitals
• important we avoid having unparameterized transaction as much as possible
• trace view shows all involved services
• looking into space we can find useful information about the type and duration, including any queries on DB

2. Similar with all subsequent page loads.

3. Errors which occur in any service should be connected via trace to relevant transacations, and errors which occur due to them being failed requests from the FE for example

4. If an error is detected during the collection of spans, that should be correctly shown in the Sentry UI with the little flame on the trace view, by setting the status correctly on the Sentry transaction