Set up Compass
Learn how to set up Compass and integrate it with Atlassian products and applications.
Compass comes with features, like activity feed and attention board, that help your team maintain individual components in your catalog.
Tools in your software development toolchain contain essential component information, such as deployment information from source code repositories or incident details from incident reporting tools. This information is vital for you to own, develop, and maintain these components efficiently. You often need to check multiple locations to get complete information about your components and require specialization to gather information from these tools.
The activity feed in Compass provides a platform to display events from any tool and provides a way to rapidly assess what has happened to your component during a window of interest.
For example, the activity feed can show deployment events from a component’s connected Bitbucket repository to help you assess the recency of the production build and see the frequency of deployment activity right from within Compass.
A component’s activity feed can also show you the events from your component's upstream dependencies, which are the components your component depends on, enabling you to assess the impact of events on your software infrastructure.
The activity feed has two visual presentations:
Timeline view: A visual and interactive view showing events plotted on a timeline. The timeline ranges from the current day up to six months in the past, and shows the relative time distances between the events. The timeline also shows events from upstream dependencies allowing you to correlate between dependent components.
List view: A tabular view with events listed in reverse chronological order, providing a highly scannable list of events and event details in a single view. You can choose to hide or show events from the component’s upstream dependencies in context with your current component.
Get events from tools to show on the activity feed by using at least one of the following methods:
To view the activity feed:
If you are not already there, go to your component’s details page in Compass.
A component’s deployment information appears as the Latest deployment tag under the component’s name. Hover on the tag to view the latest deployment details.
Select Activity from the left navigation to view the activity feed.
By default, the activity feed displays the timeline view. Here, you can interact with the timeline to view the event details.
Select and drag the timeline to navigate to a different date and time. Select Now to go back to the current instance.
Hover on an event marker to view the event details. Select the event marker to go to the event’s source.
Select List to switch to the list view.
Select Show dependencies to view the deployment events from your component’s upstream dependencies.
Select the event to go to the event’s source.
Choose between production and staging environment types to see deployment events from the specific environments.
The environment filter only affects deployment events. All other event types are unaffected and continue appearing on the activity feed.
Compass maps the states of deployment events to specific statuses that appear in the deployment tag and activity list.
Compass reads the states of the deployment events and maps them to specific statuses to appear in a component’s deployment tag and activity list.
The following deployment statuses appear in Compass:
アイコン | デプロイのステータス | 説明 |
---|---|---|
進行中 | The deployment has started and is currently in progress. This is an intermittent status and it changes to show the most current status as the deployment progresses. | |
成功 | The deployment was completed because it was successful. | |
キャンセルされました | The deployment was completed because a user stopped it while it was in progress. | |
失敗 | The deployment was completed because it failed. | |
Unknown | The deployment event’s state isn’t available for Compass to read. |
The attention board is a place on your Compass home page where things like components that are failing scorecards or not owned by anyone are listed. Use the attention board to prioritize work and fix problem components, which will help you improve your overall software health.
The attention board consists of:
Priority: The priority of an item represents what is most important for your team to fix first, and what will have the most positive impact on your component health
Type: The type of problem, a description of what’s failing at a high level such as the name of the scorecard or missing owner teams.
Description: The amount of failing criteria out of total criteria.
Link: A link to where the user can take action: for scorecards, this is the component that is currently failing and for components without owner teams, it’s a list of all those components where you can easily assign ownership.
この内容はお役に立ちましたか?