Skip to content

Add Search AI 360° Troubleshooting Guide (TSG) - #56

Draft
venkatana-kore wants to merge 1 commit into
masterfrom
cursor/search-ai-tsg-document-5b4a
Draft

Add Search AI 360° Troubleshooting Guide (TSG)#56
venkatana-kore wants to merge 1 commit into
masterfrom
cursor/search-ai-tsg-document-5b4a

Conversation

@venkatana-kore

Copy link
Copy Markdown
Collaborator

Summary

Adds a comprehensive Search AI Troubleshooting Guide (docs/SEARCH_AI_TROUBLESHOOTING_GUIDE.md) covering the full pipeline across all services observed in Groundcover.

What's covered

  • Architecture — XO11/Findly (RabbitMQ) and ABL Platform (BullMQ) stacks
  • Service catalog — 40+ workloads: crawl, extraction, indexing, embeddings, encryption, schedulers, connectors
  • Queue reference — All Findly RabbitMQ queues + ABL BullMQ queues with consumer mappings
  • Module-by-module TSG — Step-by-step debug, root causes, fixes, and immediate next steps per service
  • Scenario playbooks — Slow crawl/extract/index, queue degradation, pod crashes, realtime sync, missing search results
  • Client-side integration TSG — SSO crawler, custom extraction SDK, connectors, embeddings service
  • Groundcover observability — gcQL and PromQL cookbook with copy-paste queries
  • Escalation matrix — Severity levels and information to collect

Source

Built from Groundcover entity/log/metric analysis (kore.ai tenant across 8 backends) and SearchAssist Toolkit integration docs.

Test plan

  • Document renders correctly as Markdown
  • All service names verified against Groundcover entity queries
  • Queue names verified against production scheduler logs

Slack Thread

Open in Web Open in Cursor 

Document covers all Search AI services discovered in Groundcover including
crawling, extraction, indexing, queue health, realtime processing, and
client-side integration utilities. Includes step-by-step debugging, fixes,
Groundcover gcQL/PromQL queries, and escalation guidance.

Co-authored-by: Divi Venkata Naresh <venkatana-kore@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants