correlation
Cross-service error correlation using trace IDs and run IDs across the Lucid platform
- License 许可
- MIT
- 最近更新
- 2026-03-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- correlation
- requires
- { "mcps": [ "sentry" ] }
- description
- Cross-service error correlation using trace IDs and run IDs across the Lucid platform
02 资源文件 2
- 参考文档references/services.md1.6 KB
- 参考文档references/trace-flow.md1.4 KB
03 SKILL.md 正文
Cross-Service Correlation
Correlate errors across services using trace IDs and run IDs to detect cascading failures.
Prerequisites
- Sentry MCP:
search_issues,get_issue_details
Correlation Procedure
Step 1: Extract Correlation IDs
From the issue being investigated, look for these tags:
trace_id— W3C Trace Context ID (32-char hex)run_id— Lucid run UUID (links all operations in a single user request)
If neither exists, correlation is not possible. Check that enrichSentryEvent() is called in beforeSend to attach these tags.
Step 2: Search Across All Projects
Use Sentry MCP search_issues with query trace_id:{id} (or run_id:{id}) for each of these projects:
lucid-weblucid-workerlucid-l2lucid-trustgatelucid-mcpgatejavascript-nextjs
Rate limit strategy: Search 6 projects in a batch (all at once is fine for 6 projects).
Step 3: Deduplicate and Sort
- Deduplicate results by issue ID (same issue may appear in multiple searches)
- Sort by
lastSeendescending (newest first) - Note which services are affected
Step 4: Detect Cascade
If errors appear in more than one service for the same trace:
- Cascade detected — this is a cross-service failure
- Investigate the oldest error first (likely the root cause)
- The error propagation path usually follows the service dependency graph
If errors appear in only one service:
- Isolated failure — no cascade
- Focus diagnosis on that single service
If no errors found:
- Verify
enrichSentryEvent()is called inbeforeSendto attachtrace_idandrun_idtags - The trace may exist in OTel but not have triggered Sentry errors
Step 5: Build Timeline
Present the correlated issues as a timeline:
- Service name + Sentry project
- Issue title and severity
- Event count and user count
- First seen and last seen timestamps
- Analysis: which service was the origin, which were downstream effects
Service Dependencies
See references/services.md for the full service topology and dependency graph.
Trace Flow
See references/trace-flow.md for how traces propagate between services.
04 同仓库更多 Skills
lucid-PLUGIN_NAME
PLUGIN_DESCRIPTION
social-content
Generate short-form video content optimized for social media platforms
personalized-outreach
Generate 1:1 personalized video for sales prospecting and customer success
data-reports
Generate animated data report videos from KPIs, charts, and analytics
lucid-video
Agent-native video generation using Remotion — MCP server + OpenClaw plugin
lucid-veille
Content monitoring, AI digest generation, and multi-platform auto-publishing