Incident Blast Radius
How did one incident travel across regions and services?
How to read this example
- Facets
- Each coloured face belongs to a region.
- Levels
- Control plane, regions, clusters and services extend from centre to outer shell.
- Dashed path
- The explicit incident path connects the affected services across regions.
Try thisFollow authz-cache in Frankfurt through session-api and checkout to billing-ledger in Virginia. Select a node for its relationships and incident context.
Open the chart without page chrome ↗Drawing width at least 1,100 px. Scroll within the chart on smaller screens.
This example builds its charts with page controls and helpers, so there is no single options object to show. Open the standalone example to read its source.
import WestCoastCharts from 'west-coast-charts'
import types from 'west-coast-charts/types'
import premium from 'west-coast-charts/premium'
import networkFacet from 'west-coast-charts/layers/network-facet'
WestCoastCharts.use(types).use(premium).use(networkFacet)
const WestCoastChartsPremium = premium
const WestCoastChartsLayer_networkFacet = networkFacet
WestCoastCharts.setLicenseKey(LICENCE_KEY) // paid production licence; localhost evaluation needs no key Waiting for the chart.
Open Data & agent view to read this chart through chart.describe().
Read from the running library through its optional agent/describe module. Text, table and JSON share the same snapshot. Demo data only.
$ wcc chart export network-facet-incident.json --out network-facet-incident.svg --with-table Public agent tools 0.2.3, tested with Library 1.1.5; available from the versioned GitHub release and npm. Save a JSON spec first and check the loaded runtime and supported modules before rendering. Command reference
Loading /gallery/network/facet-incident/index.md … This example uses Premium modules. Compare licences · Embedding in a distributed product?