Get service map topology
Return the outbound dependency graph around a host, discovered by live network observation.
Restrictions
Usage
- ServiceMap is an optional subsystem: a deployment without
redis.servicemapconfigured returnsServiceUnavailable. atcurrently only acceptsnow(or empty, which behaves identically).directioncurrently only acceptsoutbound(or empty).anchor.host_idmust already be known to ServiceMap (have a current or recently retired graph); otherwise this returnsResourceNotFound.depth(max 3),max_nodes(max 500), andmax_edges(max 1000) bound the traversal; when a bound is hit,truncated=trueandtruncation_reasonsexplains why.unresolved_mode=summary(vs. the defaultfull) omits unresolved edges fromedgesand returns only a bounded sample inunresolved_endpoints.
Authorizations
App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.
Body
Query parameters for the outbound topology traversal.
Host (and optional entity) to start the traversal from.
Optional integrity check: if set, must match the network scope already associated with anchor.host_id, or the request is rejected with InvalidParameter.
Time selector for the query. Only now is currently supported; omitting the field behaves the same.
now Traversal direction. Only outbound is currently supported; omitting the field behaves the same.
outbound Maximum traversal depth from the anchor. Default 1, maximum 3.
x <= 3Maximum number of nodes to return before truncating. Default 100, maximum 500.
x <= 500Maximum number of edges to examine before truncating. Default 200, maximum 1000.
x <= 1000Whether to include the raw per-edge metrics payload in the response. Default false.
How unresolved edges are projected. full (default) includes them in edges and unresolved_endpoints; summary omits them from edges and returns only a bounded sample in unresolved_endpoints.
summary, full Response
Success
Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.