trace-a-request-id
Trace one request identifier across services, queues, retries, and downstream calls to reconstruct its outcome. Use when a distributed operation failed, slowed, duplicated, or became ambiguous.
소스 정보
- 저장소
- protosphinx/sphinxstack
- 최근 소스 활동
- 2026년 7월 29일 13:55
- 감지된 SKILL.md 언어
- 영어
- 스타
- 3
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
2 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- trace-a-request-id
- category
- code
- description
- Trace one request identifier across services, queues, retries, and downstream calls to reconstruct its outcome. Use when a distributed operation failed, slowed, duplicated, or became ambiguous.
# trace-a-request-id
Follow one bounded operation end to end without assuming every component propagated context correctly.
## Procedure
1. Confirm the identifier type, source, environment, time, and expected user action.
2. Find the ingress record and capture route, caller-safe context, deployment, and instance.
3. Follow parent, child, correlation, job, and downstream request identifiers.
4. Order spans and logs by synchronized time while accounting for retries and asynchronous handoffs.
5. Mark each boundary's input, output, latency, status, and missing evidence.
6. Separate the original attempt from duplicate, hedged, or retry attempts.
7. Compare the path with one successful request of the same operation.
8. Save a request-path report with the supported failure boundary and next check.
## Guardrails
- Request identifiers are search keys, not authorization credentials.
- Do not infer a complete path when context propagation has gaps.
- Redact associated user, token, payload, and URL data before sharing.
## Done
- A chronological request-path report is saved
- Each service and asynchronous handoff is verified or marked missing
- The final outcome reconciles with user-visible and downstream state
GitHub에서 보기