Service Topology & Dependencies

What calls what, inferred from span parentage rather than from a diagram somebody drew once and stopped updating
Services

38

+2
Dependencies

112

edges
Unhealthy edges

5

2 critical
Single points of failure

3

no fallback

Critical paths

The chains a single failure takes the most services down with

Checkout
4 hops
edgeapi-gatewaycheckout-apiorders-db

orders-db has no read replica in the write path

Sign-in
5 hops
edgeapi-gatewayauth-serviceuser-servicesessions-cache

sessions-cache is single-node

Nightly load
4 hops
talendstaging-s3databrickswarehouse

no retry between staging and Databricks

Search
4 hops
edgeapi-gatewaysearch-apielasticsearch

three replicas, degrades to cached results

Most depended on

Fan-in: how many services break if this one does

ServiceCallersCalls (1h)Health
api-gateway142.4M99%
auth-service11840K99%
orders-db7612K82%
user-service6431K98%
sessions-cache51.1M91%
notifications496K97%

Dependency edges

Caller → callee, with the volume and error rate of that specific pair

ServiceDepends onCalls (1h)p99Error rateStatus
checkout-api

synchronous

orders-db612K2.9s4.10%Degraded
api-gateway

synchronous

checkout-api418K1.4s1.80%Watch
api-gateway

synchronous

auth-service840K86ms0.04%Healthy
auth-service

cache

sessions-cache1.1M310ms0.90%Watch
auth-service

synchronous

user-service431K54ms0.02%Healthy
orders-worker

asynchronous

notifications96K120ms0.10%Healthy
search-api

synchronous

elasticsearch288K71ms0.03%Healthy
databricks

batch

warehouse1.2K18s0.00%Healthy

No matching results

LoveHeartBeat - A Product from RootVyana.

v1.24.0

Theme Customizer

Explore different styles according to your preferences

Color Scheme
RTL

Change text direction

Support Chat

Toggle support chat

Navigation Type
Vertical Navbar Appearance
Horizontal Navbar Shape
Horizontal Navbar Appearance
Purchase template
customize