Software Catalog
Relationships
Trace ownership, follow dependencies, and understand what’s connected in your software catalog.
Overview
The Relationship graph provides a map that visualizes how services, resources, people, and teams are connected across your engineering system. Relationships are auto-inferred based on existing Tempest deployments or can be manually defined for every individual component of your catalog.Explicit relationships
Within any resource, project, recipe, team, and people entity, you can now set explicit, user-defined relationships to other entities in your organization. This is in addition to existing, bespoke relationship mapping like ownership and governance. To get started, select any entity and click “Add Relationships” in the bottom righthand sidebar. From there, you can select a relationship and its associated entity.Inferred relationships
Inferred relationships are automatically discovered as you you deploy through Tempest recipes, attach owners, and build out your software catalog. These relationships are inferred using a lightweight graph model and AI to connect the dots. Some of these relationships are considered “soft relationships” and can be removed. Others, like the relationship between a project ad its deployed resources, persist throughout the lifecycle of both entities and cannot be removed.Graphs
A tree graph representation of your software is available on the Apps, Products & Features, Resources, Projects, Recipes, Teams, and People pages. When viewing an entity, click the “Relationships” tab in the main content area. By default, entities that have two degrees of relation to the root entity (the entity from which you are exploring the graph) will be displayed in a horizontal layout. Every relationship graph consists of **nodes **(the individual entities like resources, teams, people, projects, and recipes) and their **edges **(the relationship between two nodes).Navigating the Graph
The relationship graph uses a bi-directional, hierarchical layout to make dependencies easy to follow.- The root node (the resource you’re currently viewing) is centered in the graph.
- Child and downstream relationships flow to the right.
- Parent and upstream relationships flow to the left.
- Reciprocal relationships are grouped on the same side as the related node.
Available Relationships
| Relationship Type | Definition |
|---|---|
| API for | One resource exposes an API that another resource, project, or recipe relies on. |
| Authenticates | Used when one service or resource provides authentication for another. |
| Caches | A resource stores or serves cached data for another resource. |
| Connects to | One resource or recipe establishes a connection with another. |
| Contains | One project or recipe includes other resources or components within its structure. |
| Database for | A resource serves as the data store for another resource. |
| Depends on | A resource, recipe, or project relies on another to function correctly. |
| Deployed on | A resource is hosted on or deployed to another infrastructure resource. |
| Exposes | A resource exposes another internal service or component to the network. |
| Hosts | An infrastructure resource hosts another service or job. |
| Monitors | A monitoring resource tracks performance or availability of another resource. |
| Owned by | A resource, recipe, or project is owned by a team or individual owner. |
| Related to | A general-purpose relationship for semantically linked entities. |
| Routes to | One resource or recipe forwards traffic to another. |