Incident record
T-219Intermittent connectivity
Reported against C-14. Keep the recorded symptoms, timestamps, and investigation notes together.
SQL · structured context All industries See the service
Telecommunications
See the service
behind the circuit.
Connect network inventory, service relationships, and operational knowledge for investigation and customer-support applications.
Follow the recorded relationships
From one circuit to its service context.
Model the dependencies your team knows, then retrieve the records and runbooks an investigator needs.
Investigation question
Which services depend on circuit C-14?
SiteNorth exchange
S-03CircuitAccess circuit
C-14ServiceBranch connectivity
SV-09Customer accountHarbor retail
A-27Declared dependencies: site → circuit → service → account
Runbook source
R-07Access-circuit checks
Retrieve passages by exact terms or similar descriptions of the reported problem.
Full-text + vector candidatesYour investigation application
A source-linked case view
- Related service and account
- Ticket and source records
- Runbook passages for review
Your application combines these separate queries. A stored dependency identifies context for review; it does not establish that a circuit caused an incident or that a customer is currently affected.
Explore graph queriesFor operations and service teams
Keep the investigation connected.
Trace the relevant dependencies.
Start from a site, circuit, or service ID. Traverse declared relationships, fetch the linked records, and review related tickets. Your ingestion process supplies inventory updates and observations from existing systems.
FindRelated assets and services
ReviewEvidence, ownership, and freshness
Query connected records Bring the runbook into the case.
Look up authorized account and service details with SQL. Use keyword and semantic retrieval to find troubleshooting guidance. Show source versions so an engineer can assess the next step before taking action.
RetrieveCurrent guidance and prior cases
PresentContext an agent can verify
Build knowledge retrieval Four models, defined responsibilities
Build from your inventory outward.
Choose stable asset IDs and record when each dependency was observed. Keep retrieval orchestration and operational actions in your application.
Write rows, vectors, and full-text entries separately. Re-index changed runbooks and verify access before passing customer context to a model or agent.
Read structured facts.
Model inventory, cases, service ownership, and source versions.
Define the schemaFollow known dependencies.
Declare relationships between your records and choose the traversal depth for each investigation.
Create a relationshipFind similarly described issues.
Generate embeddings in your pipeline; test retrieval against cases your team has reviewed.
Index embeddingsKeep exact terms searchable.
Index runbook passages for product names, fault descriptions, and operational terminology.
Add keyword retrievalStart with a known service path