make test
make test exit=0 last=PASS: lab6 public API scenario; infrastructure and grading evidence remain separate.
upload chain
attachment bf19675a-7d93-4379-a708-1e5efc7366a7 status=ready
accepted trace_id=d27d941c741436ad51a3b35c2921ca4d
trace d27d941c741436ad51a3b35c2921ca4d spans=14
  messenger-api http post /api/v1/chats/{chatId}/attachments parent=- dur_ms=15.4
  messenger-api attachments.process publish parent=http post /api/v1/chats/{chatId}/attachments dur_ms=16.5
  messenger-api s3.PutObject parent=http post /api/v1/chats/{chatId}/attachments dur_ms=6.8 STATUS_CODE_OK
  jdbc query parents {"http post /api/v1/chats/{chatId}/attachments": 5}
transient retry
retry attachment ac1e1581-4d24-4789-a887-c14a1852581a status=ready
retry trace_id=5540712fa2d49096df09db864f9ad9a8
trace 5540712fa2d49096df09db864f9ad9a8 spans=15
  messenger-api s3.PutObject parent=http post /api/v1/chats/{chatId}/attachments dur_ms=47.7 STATUS_CODE_OK
  messenger-api attachments.process publish parent=- dur_ms=66.9
  messenger-api attachments.process publish parent=http post /api/v1/chats/{chatId}/attachments dur_ms=88.5
  jdbc query parents {"http post /api/v1/chats/{chatId}/attachments": 5}
retry process spans=0 publish spans=2
latency before faults p50_s=0.039146836
latency before faults p95_s=0.1319807649
latency before faults p99_s=0.13377033457999998
slow database vs slow handler
slow-db trace_id=36ade98779e9df3c78189a912ceb8d03
trace 36ade98779e9df3c78189a912ceb8d03 spans=3
  messenger-api http post /internal/demo/slow-db parent=- dur_ms=3088.5
  jdbc query parents {"http post /internal/demo/slow-db": 1}
slow-db longest jdbc query ms=3013.3
slow-handler trace_id=575746a2026457fbcaec75fee2f4f794
trace 575746a2026457fbcaec75fee2f4f794 spans=1
  messenger-api http post /internal/demo/slow-handler parent=- dur_ms=3025.8
slow-handler server ms=3025.8 longest jdbc query ms=0.0
queue lag incident
queued while worker stopped 5c74e9f3-babc-424e-82df-55d025469ede
queue age after wait s=15.321
queue alert while stopped=Alerting age_s=75.484
queue recovered 5c74e9f3-babc-424e-82df-55d025469ede status=ready
queue alert after recovery=Normal age_s=0
error rate incident
demo 500 responses=608
error alert during burst=Alerting ratio=1
error alert after quiet=Normal ratio=0
telemetry backends down
mem before messenger-lab6-otel-collector-1 100MiB / 320MiB | messenger-lab6-api-1 495.2MiB / 1GiB | messenger-lab6-api-2 514.4MiB / 1GiB | messenger-lab6-worker-1 387.6MiB / 1GiB
message while stores down status=201 id=c5f2bfe7-8bfc-4eae-b74e-9cca38a4ccf2
attachment while stores down 9a27a451-d677-4ed9-9684-a440620bb017 status=ready
mem during messenger-lab6-otel-collector-1 99.99MiB / 320MiB | messenger-lab6-api-1 495.1MiB / 1GiB | messenger-lab6-api-2 514.5MiB / 1GiB | messenger-lab6-worker-1 394.8MiB / 1GiB
mem 20s later messenger-lab6-otel-collector-1 98.87MiB / 320MiB | messenger-lab6-api-1 495.6MiB / 1GiB | messenger-lab6-api-2 515MiB / 1GiB | messenger-lab6-worker-1 392.3MiB / 1GiB
collector export failure lines in last 2m=32

complete tempo read after worker spans arrived
upload bf19675a-7d93-4379-a708-1e5efc7366a7 trace d27d941c741436ad51a3b35c2921ca4d spans=38
  api http post /api/v1/chats/{chatId}/attachments
  api s3.PutObject parent=http post
  api attachments.process publish parent=http post
  worker attachments.process process parent=attachments.process publish
  worker s3.GetObject and four s3.PutObject parent=attachments.process process
  jdbc queries: 5 under the http span, 11 under the process span
api log: event=attachment.accepted trace_id=d27d941c741436ad51a3b35c2921ca4d attachment id=bf19675a-7d93-4379-a708-1e5efc7366a7
worker log: event=job.ready trace_id=d27d941c741436ad51a3b35c2921ca4d attachment id=bf19675a-7d93-4379-a708-1e5efc7366a7
loki {service_name="messenger-api"} | trace_id="d27d941c741436ad51a3b35c2921ca4d"
  event=http.completed method=POST route=/api/v1/chats/{chatId}/attachments status=202
  event=attachment.accepted attachment accepted id=bf19675a-7d93-4379-a708-1e5efc7366a7

retry ac1e1581-4d24-4789-a887-c14a1852581a trace 5540712fa2d49096df09db864f9ad9a8 spans=51
  api http post parent of first attachments.process publish and s3.PutObject
  worker first attachments.process process parent=first publish
  api second attachments.process publish parent=first process
  worker second attachments.process process parent=second publish
  s3.GetObject and four s3.PutObject only on the second process
  jdbc queries: 5 under the http span, 17 under process spans
worker log: event=job.retry trace_id=5540712fa2d49096df09db864f9ad9a8 span_id=fbb2b88869169e94
worker log: event=job.ready trace_id=5540712fa2d49096df09db864f9ad9a8 span_id=34731a347680c0b7
loki {service_name="messenger-worker"} | trace_id="5540712fa2d49096df09db864f9ad9a8"
  event=job.retry
  event=job.ready

The first Tempo GET in this file saw only API spans. Worker spans were already in the same trace a few seconds later.
