ወደ ይዘቱ ይሂዱ

ዋና የመድረክ አቅም

ሶፍትዌርዎ እንዴት
እንደተገናኘ ይመልከቱ።

Zof የአገልግሎቶችዎን፣ APIዎችን እና ጥገኝነቶችን ካርታ ይሠራል፣ ስለዚህ አንድ ነገር ሲለወጥ ቡድንዎ ምን መፈተን እንዳለበት ያውቃል።

  • የማረጋገጫ ማስረጃ እና ቁጥጥር
  • ፖሊሲ በሚፈልግበት ቦታ የሰው ፈቃድ
  • Works with GitHub

ጊዜን የሚከታተል

ምን እንዳለ፣ ምን እንደተለወጠ፣ መቼ እና በማን

የተጽእኖ ስፋት

እርምጃው ከመፈጸሙ በፊት የሚወሰን

ፖሊሲዎች

ከሚጠብቋቸው ሥርዓቶች ጋር የተገናኙ

ወሰኑ የተወሰነ

በተፈቀዱ ሥርዓቶች እና መዳረሻ ላይ

What the graph holds

Entities, relationships, and time

ከማከማቻዎችዎ አገልግሎቶች፣ የመጨረሻ ነጥቦች፣ የመረጃ ማከማቻዎች፣ ጥገኝነቶች እና ባለቤቶች።

  • 01

    Relationships that carry consequence

    DEPENDS_ON, CALLS, READS, WRITES, DEPLOYS_TO, OWNED_BY, PROTECTED_BY, VERIFIED_BY, AFFECTS, GENERATED_BY, APPROVED_BY, USES_MODEL, USES_TOOL, SATISFIES, and VIOLATES.

  • 02

    Temporal by design

    What exists, what changed, when it changed, who or what changed it, what depended on it, what evidence existed, what policies applied, what decision was made, and what happened afterward.

  • 03

    Blast radius before action

    Every proposed change resolves to affected systems, criticality tier, applicable controls, historical incidents, and the verification required.

  • 04

    Shared by the whole loop

    Verification, evidence, and control all read from the same graph, so every decision is grounded in one understanding of the enterprise.

የአጠቃቀም ሁኔታዎች

ቡድኖች የሚለኩዋቸው ውጤቶች

  • Size the blast radius before shipping

    See exactly which systems, data, and customers a change can affect, and how critical they are, before it is allowed to run.

    Tier 0

    criticality resolved
  • Require the right verification

    Controls mapped to affected systems determine the evidence a change must produce, so verification is targeted rather than exhaustive.

    Policy

    selects the evidence
  • Reconstruct any decision

    Walk back from an incident to the change, the evidence that existed, the policies that applied, and who approved it.

    Temporal

    history stays queryable
  • Give leadership one risk view

    One graph shows where risk concentrates, where controls apply, and what changed recently.

    One

    source of truth
Platform integration

The substrate of the control loop

The System Graph is not a standalone feature. Verification reads it to decide what must be proven, Evidence writes to it, and Control relies on it to size risk.

መድረክ

Verification Engine

Selects the evidence each change requires from the systems and controls the graph resolves.

መድረክ

Evidence

Every bundle, approval, and outcome is written back to the graph, so history is queryable.

መድረክ

Control Plane

Policy decisions are grounded in criticality, affected systems, and incident history from the graph.

የአስተዳደር ቁጥጥር

በእያንዳንዱ ወሳኝ ደረጃ የሰው ማጽደቅ ያለበት በቁጥጥር ስር የሚካሄድ ማረጋገጥ።

መቆጣጠሪያዎች
  • በእርስዎ የቁጥጥር ንብርብር ስር ቀጣይ ማረጋገጥ
  • System Graph ለውጦች ከመለቀቃቸው በፊት ጥገኝነቶችን በካርታ ያሳያል
  • ለተገዢነት ግምገማዎች ለኦዲት የሚመጥን ማስረጃ
የማረጋገጫ ማስረጃ · የሰው ማጽደቅ · የኦዲት መዝገቦች

Detailed guide · English

In practice

Turn dependency context into a testing decision

The useful output of a graph is an explanation of why a change deserves attention. Start with a specific revision and follow the relationships that connect it to behavior your customers depend on. Treat missing relationships as an investigation task.

  1. 01

    Establish the starting point

    Identify the repository, base revision and proposed revision. Include configuration and dependency changes in the review scope, even when the application code diff is small.

  2. 02

    Follow the consequential paths

    Compare the reported affected areas with what the service owner expects. Ask which shared libraries, API consumers and background jobs could experience different behavior. Connected data sources determine which of these relationships are available.

  3. 03

    Choose checks and retain the rationale

    Use the dependency paths to select tests and reviewers. Record why each critical path was included. Keep a broader regression suite when unresolved dependencies make a narrower selection unreliable.

Illustrative scenario · not a customer result

A shared authentication library

A token parser changes in a library used by a web application and a background worker. A graph can help identify consumers represented in its inputs. Test valid, expired and malformed tokens in those consumers. If the worker relationship is absent, add it to the investigation rather than treating it as unaffected.

Questions to resolve before you begin

Is this a complete map of production?

Coverage depends on the connected sources and the relationships they describe. Static imports do not reveal every runtime call. Review source freshness and unresolved edges before relying on the map.

Does the graph replace observability?

Dependency context helps decide where to investigate and test. Production telemetry answers what is happening at runtime. Use both when assessing a release or investigating an incident.

ቀጣይ እርምጃ

የራስዎን System Graph ይመልከቱ

Reliability Sprint ይቀጥሩ፤ Zof መበላሸቱን ሊሸከሙት የማይችሉትን አንድ ሥርዓት ካርታ መሥራት ይጀምራል፣ ወሳኝ መንገዶችን እና ስጋት ያለባቸውን ቦታዎች ይለያል።

  • መዳረሻን እና ወሰንን ይመርምሩ
  • አንድ ወሳኝ ሥርዓት ይገምግሙ
  • የግል ማሰማራት አማራጮች
ቀጥታ ማሳያ · ናሙና ውሂብ

ምን እንደተለወጠ ይወቁ። ምን መሞከር እንዳለበት ይወቁ።

የቶፖሎጂ-ግንዛቤ ያለው የተጽዕኖ ትንታኔ የአገልግሎት ለውጦችን ከተነኩ የስራ ፍሰቶች ጋር ያገናኛል እና በስርዓት ጥገኝነቶች ላይ የተመሰረቱ የማረጋገጫ እቅዶችን ይመክራል።

ማረጋገጥን ቅድሚያ ለመስጠት የስርዓት አውድ ይጠቀሙ።

01System Graph

የእያንዳንዱን ለውጥ ውጤት ይረዱ።

The System Graph maps services, endpoints, datastores, dependencies and owners from your repositories, so Zof knows what a proposed change could affect.

ውጤት

የተጽእኖ ስፋት

የተነኩ ስርዓቶች፣ ወሳኝነት እና ቁጥጥሮች ለእያንዳንዱ ለውጥ ይለያሉ።

ጊዜያዊ ግንኙነት

ምን ተለወጠ፣ መቼ፣ በማን

ታሪክ፣ ማስረጃ እና ውሳኔዎች ሊጠየቁ የሚችሉ ሆነው ይቆያሉ።

መሠረት

አንድ ግራፍ፣ ሙሉ ዑደት

ማረጋገጫ፣ ማስረጃ እና ቁጥጥር ተመሳሳይ ሞዴል ያነባሉ።

MAPPED · LIVE/system-graph
የZof System Graph ንድፍ በauth-service ላይ ለውጥን ይለያል፦ Payment API፣ Checkout፣ Ledger እና Customer API እንደተነኩ ተደምቀዋል፣ ከTier 0 ወሳኝነት፣ 7 የተነኩ ስርዓቶች፣ 4 ተፈጻሚ ቁጥጥሮች፣ 2 ያለፉ ክስተቶች እና 6 አስፈላጊ ማረጋገጫዎች ማሳያ ጋር።
System Graph · የለውጥ ሊኖር የሚችል ተጽእኖ የሚያሳይ ንድፍ።