Tracing cross-service HTTP calls across a Go microservices codebase

[DeusData]

One of the features I find most useful is cross-service HTTP linking. If you have multiple services that call each other via REST, the graph discovers those connections automatically.

After indexing two services:

query_graph(query="MATCH (a)-[r:HTTP_CALLS]->(b) RETURN a.name, b.name, r.url_path, r.confidence ORDER BY r.confidence DESC LIMIT 20")

This shows which functions in Service A call endpoints in Service B, with a confidence score. High confidence (>0.8) means the URL path was found directly in the code. Lower confidence means it was inferred from config files or partial matches.

The trace goes deeper too:

trace_call_path(function_name="CreateOrder", direction="both", depth=3)

This shows not just the direct HTTP call, but the full chain: which handler receives the request → what business logic it calls → which downstream HTTP calls it makes.

For anyone with a microservices architecture: what's your experience with the HTTP linking accuracy? The confidence scoring helps filter noise, but I'm curious about edge cases.