Rate this page:
A component is an output artifact of your engineering team. It could be a service, a library, an application, or something else.
A component’s catalog listing in Compass is the unified view of all information about the component. The first step to build a component catalog is to create components.
To create a new component manually:
We’ll add your component to the catalog and take you to the component’s details page, where you can add detailed information such as links to repositories and documentation, chat channels, dependencies, and more.
You can also create components while you are on your team’s dashboard or on one of the components list pages. When you're there, select + Create component, provide the component's details, and select Create.
You can also create components using the Compass GraphQL API. Learn how to create components using the API
A component's details page is the single place in Compass where you’ll find everything you want to know about your component. In the details page, you’ll find what the component does, who owns it and how to contact them, its links and dependencies, scores, and more.
To view your component’s details, use any of the following methods:
A component’s URL never changes. Bookmark the URL of a component’s details page and use it as an easy reference in the future.
When you view a component, you'll first see the Overview page. This page groups the key details about the component.
Basic details: This section is the first place the users look when they view a component’s details. It shows the component’s basic details such as its name and description. For service-type component's the tier appears here.
Scorecards: This section shows the scorecards you apply to a component. Scorecards show a component’s health based on set criteria.
Owner team: This card shows the owner team’s information. An owner team has a defined responsibility towards managing a component. You can assign or change a component’s ownership from this section.
Component contacts: This card shows links to the owner team’s chat channel. Users can reach out to the component's owner team for information about the component.
On-call: This card shows links to a component's on-call roster. The on-call links are available only for service-type components. These links give you access to the people who can provide help with the component or support you during an incident.
Custom fields: This card shows all custom fields associated with the specific component type. With custom fields, you can add valuable information to a component that’s not available using Compass’s default fields.
Resource links, labels, and metrics: Links to a component’s resources, such as repositories, documentation, projects, and more, appear in their respective sections. More details, such as labels and metrics are also available in the own sections on the Overview page.
Component navigation: Pages providing more information about the component appear in the component navigation. Some of these pages are available by default, for example Activity or Dependencies. Whereas, some pages become available when you install different apps on Compass, for example, Swagger UI or Statuspage.
Every component has a type, so you can categorize components based on their capabilities. You set a component’s type when you create it, and can change its type at any time.
There are four types of components:
Service — An independently-deployable software unit that is usually is operated by a person or a team. Services can be as large as monoliths or smaller microservices.
Library — A reusable collection of objects, functions, and methods. A library is typically used by other components.
Application — A fully-packaged application, like a mobile application, desktop application, or a CLI-type tool.
Other — A component that doesn’t match the service, library, or application type.
|Name||Service, Library, Application, Other|
|Owner team||Service, Library, Application, Other|
|Description||Service, Library, Application, Other|
|Repositories||Service, Library, Application, Other|
|Documentation||Service, Library, Application, Other|
|Projects||Service, Library, Application, Other|
|Dashboards||Service, Library, Application, Other|
|Links||Service, Library, Application, Other|
|Chat channels||Service, Library, Application, Other|
|Metrics||Service, Library, Application, Other|
|Scorecards||Service, Library, Application, Other|
|Custom fields||Service, Library, Application, Other|
If your component is managed by a configuration file, you can't change its type. We're working on adding this feature for components like this.
For now, delete the component and recreate it with the correct type.
Go to the component's Overview page.
Select More actions > Change component type.
Choose the component type you want to change to.
If you change from a service to a library, application, or other type, the current service tier and on-call schedules will no longer be visible. Custom fields and scorecards will be reapplied based on the component type you change to.
If you change from a library, application, or other type to a service, a service tier of 4 will be applied, as well as service-based custom fields and scorecards.
If you change between a library, application, or other type, custom fields and scorecards will be reapplied based on the component type you change to.
If you change back to a component type you previously used, you’ll get back the original information that was associated to it.
If you delete a component, any information that was ever associated with it will be deleted.
You can delete a component’s catalog listing from Compass. Deleting a component permanently deletes the component’s associated data from Compass. You can’t undo the deletion.
We don’t delete any component data from other systems outside Compass.
If your component is managed by a configuration file, you can’t delete it from Compass.
You must first disconnect the component from the configuration file before deleting it.
To delete a component from Compass:
Rate this page: