Process Analytics · Intermediate

Observability for Integration Teams

Name: Observability for Integration Teams
Price: 560000 KRW

Live online · 4 weeks · 13 live hours

Instrument brittle integrations: file drops, FTP bridges, and aging SOAP endpoints. You'll define SLOs that reflect business hours in Korea and practice incident narratives that operations teams trust.

Tuition (informational)

₩560,000

No checkout here—request details via Contact. See Money-Back Policy.

Structured log viewer with trace identifiers highlighted

Owen Shin

Observability consultant for legacy stacks; focuses on integration SLO labs.

What you build and discuss

Trace propagation through batch and sync paths
SLO math with seasonal traffic for retail peaks
Error budget policies that include vendor dependencies
Runbook quality checklist used by mentors
Dashboard anti-patterns: metric walls vs actionable tiles
Post-incident review template with blameless tone

Outcomes we assess

01 Ship a tracing diagram for a hybrid integration path
02 Propose an SLO set with explicit exclusion notes
03 Facilitate a 30-minute incident recap using the cohort template

Participant notes

“Observability for Integration Teams reframed our 'metric wall' as a risk. Still tuning SLOs, but the narrative structure helps.”
— Yohan

Logistics & candor

Includes a limitation-focused FAQ item per program requirements.

Examples use OpenTelemetry concepts; vendor-specific agents are your responsibility.