Activity Services

The Services Dashboard provides an engineering activity breakdown at the repository/service level, allowing teams to track activity across different microservices and repositories.

Data Sources

All activity data is sourced from Git/VCS tools integrated with Hatica.

Filters

1. Date Range Picker: Select a specific time period to view relevant metrics.
2. Service: Filter activity by a specific service or repository.
3. Activities: Select specific activity types such as:
   1. PRs Opened
   2. PRs Merged
   3. PR Reviews
   4. PR Comments
   5. Commits
4. Custom Teams: Filter based on pre-defined custom teams.
5. Filter Empty Rows: Hide services with no recorded activity during the selected period.

How to infer this data?

Each activity type is color-coded to help users quickly identify activity distribution.

1. Color and Band Size:
   1. Color coding differentiates activity types, making it easy to spot trends.
   2. Band density represents the volume of activity—packed cells indicate high engagement, while empty cells indicate no recorded activity.
   3. Pill size varies based on task significance—larger pills represent bigger tasks or higher effort, while smaller pills indicate smaller contributions.
2. Summary Column: The second column summarizes total activity per service, helping teams compare workloads across repositories. Active repositories should show steady commit and review activity, while dormant ones may indicate abandoned projects.
3. Day-Level Summaries: Clicking on a day’s cell within a service’s row opens the context window displaying all activity on that day, helping teams track repository changes in real time.

The Commit data only accounts for Remote commits; any commits done on Local Git branches are not included here. So if your team has a habit of doing all development on a local branch and pushing it to a remote branch after a period of time, you may not see any Commit activity.

How to Use This Dashboard

• Compare activity levels across services—which repositories are most active?
• Understand team engagement across different services.
• Identify inactive services—if a repository has had no recent PRs or reviews, it may indicate abandoned work.
• Track deployment lag—are merged PRs being deployed quickly or getting stuck?
• Spot repositories with long open PRs or stalled reviews.
• Ensure healthy code contribution and review cycles across microservices.