Observability incident graph
Latest stable Based on Graph release 0.5.1
Problem and backend
Section titled “Problem and backend”This example correlates dependencies, owners, and alerts instead of treating telemetry as unrelated records. It uses TinkerGraph to isolate modeling from container and network variance. Read core model and TinkerPop first; use the selection guide before production.
- Nodes: Service/Api/Team/Alert/Incident
- Edges: DEPENDS_ON/OWNED_BY/ALERTS_ON/ROOT_CAUSE
- Key properties: serviceId, apiId, teamId, alertId, incidentId, severity, status
Prerequisites and release boundary
Section titled “Prerequisites and release boundary”Use JDK 21, commit 3e0fa7cb9e3bc70c2743aeebda2487f3e45e4907, and the checked-in wrapper. Examples are not published; run this release fixture as a Gradle project from the release source checkout. In a consumer application, select only bluetape4k-dependencies:<ecosystem-version> and add the required graph module without an individual version.
Run and observe
Section titled “Run and observe”./gradlew :observability-graph-examples:test --tests "io.bluetape4k.graph.examples.observability.TinkerGraphObservabilityIncidentTest"The tests assert downstream dependencies, upstream impacted services and public APIs, the shared alert boundary, and owning teams. A failure should be read as a broken telemetry relation or correlation path, not as proof that the whole observability model failed.
Reading order
Section titled “Reading order”Continue from network-topology, then read data-lineage. Also see paired APIs, testing, and operations.
Exercises and production gaps
Section titled “Exercises and production gaps”Add one result-changing edge and assertion; repeat through the suspend API; then run a persistent-backend concrete test serially. Add disconnected and malformed inputs as diagnostics. This fixture does not prove throughput, clustering, authorization, tenant isolation, migration, backup, remote-driver timeout, or index quality.
Release diagrams
Section titled “Release diagrams”These diagrams are loaded directly from README assets published with the 0.5.1 release and pinned to its immutable commit. They describe this manual’s released structure and runtime flows, not later Snapshot changes. Select a preview to open the SVG at the same release commit.
observability graph examples architecture
Section titled “observability graph examples architecture”Release README: examples/observability-graph-examples/README.md
observability graph examples data flow
Section titled “observability graph examples data flow”Release README: examples/observability-graph-examples/README.md
observability graph examples ERD
Section titled “observability graph examples ERD”Release README: examples/observability-graph-examples/README.md


