Disclaimer: If you are looking for documentation on the experimental new frontend system support, please go here.

Welcome to the catalog graph plugin! The catalog graph visualizes the relations between entities, like ownership, grouping or API relationships.

The plugin comes with these features:

• EntityCatalogGraphCard: A card that displays the directly related entities to the current entity. This card is for use on the entity page. The card can be customized, for example filtering for specific relations.

  CatalogGraphCard.mov

• CatalogGraphPage: A standalone page that can be added to your application providing a viewer for your entities and their relations. The viewer can be used to navigate through the entities and filter for specific relations. You can access it from the EntityCatalogGraphCard.

  CatalogGraphStandaloneViewerV2.mov

• EntityRelationsGraph: A react component that can be used to build own customized entity relation graphs.

To use the catalog graph plugin, you have to add some things to your Backstage app:

1. Add a dependency to your packages/app/package.json:

   # From your Backstage root directory
   yarn --cwd packages/app add @backstage/plugin-catalog-graph

2. Add the CatalogGraphPage to your packages/app/src/App.tsx:

   <FlatRoutes>
     …
     <Route path="/catalog-graph" element={<CatalogGraphPage />} />…
   </FlatRoutes>

   You can configure the page to open with some initial filters:

   <Route
     path="/catalog-graph"
     element={
       <CatalogGraphPage
         initialState={{
           selectedKinds: ['component', 'domain', 'system', 'api', 'group'],
           selectedRelations: [
             RELATION_OWNER_OF,
             RELATION_OWNED_BY,
             RELATION_CONSUMES_API,
             RELATION_API_CONSUMED_BY,
             RELATION_PROVIDES_API,
             RELATION_API_PROVIDED_BY,
             RELATION_HAS_PART,
             RELATION_PART_OF,
             RELATION_DEPENDS_ON,
             RELATION_DEPENDENCY_OF,
           ],
         }}
       />
     }
   />

3. Bind the external routes of the catalogGraphPlugin in your packages/app/src/App.tsx:

   bindRoutes({ bind }) {
     …
     bind(catalogGraphPlugin.externalRoutes, {
       catalogEntity: catalogPlugin.routes.catalogEntity,
     });
     …
   }

4. Add EntityCatalogGraphCard to any entity page that you want in your packages/app/src/components/catalog/EntityPage.tsx:

   <Grid item md={6} xs={12}>
     <EntityCatalogGraphCard variant="gridItem" height={400} />
   </Grid>

Copy the default implementation DefaultRenderNode.tsx and add more classes to the styles:

const useStyles = makeStyles(
    theme => ({
        node: {
            …
            '&.system': {
                fill: '#F5DC70',
                stroke: '#F2CE34',
            },
            '&.domain': {
                fill: '#F5DC70',
                stroke: '#F2CE34',
            },
        …
);

Now you can use the new classes in your component with className={classNames(classes.node, kind?.toLowerCase(), type?.toLowerCase())}

return (
  <g onClick={onClick} className={classNames(onClick && classes.clickable)}>
    <rect
      className={classNames(
        classes.node,
        kind?.toLowerCase(),
        type?.toLowerCase(),
      )}
      width={paddedWidth}
      height={paddedHeight}
    />
    <text
      ref={idRef}
      className={classNames(classes.text, focused && 'focused')}
      y={paddedHeight / 2}
      x={paddedWidth / 2}
      textAnchor="middle"
      alignmentBaseline="middle"
    >
      {displayTitle}
    </text>
  </g>
);

Once you have your custom implementation, you can follow these steps to modify the required components:

• In the app.tsx update the CatalogGraphPage component to include your custom styles:

<Route path=“/catalog-graph” element={<CatalogGraphPage renderNode={MyCustomRenderNode} />} />

• In the Entity.tsx file, update the EntityCatalogGraphCard component to this:

<EntityCatalogGraphCard variant=“gridItem” renderNode={MyCustomRenderNode} height={400} />

Run yarn in the root of this plugin to install all dependencies and then yarn start to run a development version of this plugin.