~/talk

What OpenTelemetry Users Taught Us About...

links:none on file
links:none on file
slides:none on file

OpenTelemetry users report that getting to production — not hello world — is the hard part, so the SIG collects concrete configs and patterns: Mastodon runs a ~6‑person team, ~300k daily users, and uses one collector per namespace with 0.1% tail sampling plus 100% error traces; Adobe runs thousands of collectors in a three‑tier design (sidecar → deployment collectors per signal → backends) via Helm and the operator; Skyscanner manages 1,000+ services across 24 clusters with a single DNS endpoint, Istio routing, gateway and agent collectors and a base image that disables everything then enables what’s needed. Continuous upgrades and deprecations remain the biggest operational pain.

AI-written summary · about

  1. 0:00Introduction and survey
  2. 1:28Speaker introductions
  3. 2:11Initial assumptions about DevEx
  4. 3:58Surveying end users
  5. 5:45Collecting production stories
  6. 6:30Mastodon’s OpenTelemetry setup
  7. 9:22Adobe’s three-tier collector design
  8. 12:31Skyscanner’s collector architecture
  9. 14:59Key takeaways from interviews
  10. 17:06Lessons learned by the SIG
  11. 18:53OpenTelemetry Blueprints initiative
  12. 20:17Q&A and closing
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.