DVT GitHub Copilot Metrics - Dashboard

1. Introduction
2. Deploy to Azure

Introduction

The GitHub Copilot Metrics Dashboard is a solution accelerator designed to visualize metrics from GitHub Copilot using the GitHub Copilot Metrics API and GitHub Copilot User Management API.

The dashboard showcases a range of features:

Filters: Ability to filter metrics by date range, languages, code editors and visualise data by time frame (daily, weekly, monthly).

Acceptance Average: Percentage of suggestions accepted by users for given date range and group by time range (daily, weekly, monthly).

Active Users: Number of active users for the last cycle.

Adoption Rate: Number of active users who are using GitHub Copilot in relation to the total number of licensed users.

Seat Information: Number of active, inactive, and total users.

Language: Breakdown of languages which can be used to filter the data.

Code Editors: Breakdown of code editors which can be used to filter the data.

Deploy to Azure

DVT-specific setup

You need access to the Developer tooling prod-001 subscription in Azure. To do this, log into Azure with your adm account, navigate to Privileged Identity Management > My roles > Groups and activate the az-sub-Developer Tooling-prod-001-owner group for the time you need.

Run:

azd auth login
# choose your adm account in the browser window that pops up
azd init
# set environment name = dvt-copilot-dashboard
azd up
# choose
#   subscription = Developer Tooling- prod- 001 subscription
#   location = (Europe) West Europe (westeurope)
#   githubAPIScope = organization
#   githubEnterpriseName = tv2
#   githubOrganisationName = tv2

We haven't figured out how to attach to the existing secrets 🤷

General setup

The solution accelerator is a web application that uses Azure App Service, Azure Functions, Azure Cosmos DB, Azure Storage and Azure Key Vault. The deployment template will automatically populate the required environment variables in Azure Key Vault and configure the application settings in Azure App Service and Azure Functions.

The following steps will automatically provision Azure resources and deploy the solution accelerator to Azure App Service and Azure Functions using the Azure Developer CLI.

Important

🚨🚨🚨 You must setup authentication using the built-in authentication and authorization capabilities of Azure App Service.

Prerequisites

You will be prompted to provide the following information:

- GitHub Enterprise name
- GitHub Organization name
- GitHub Token
- GitHub API Scope

GitHub API Scope define the GITHUB_API_SCOPE environment variable that can be "enterprise" or "organization". It is used to define at which level the GitHub APIs will gather data. If not specified, the default value is "organization".

1. Download the Azure Developer CLI
2. If you have not cloned this repo, run azd init -t microsoft/copilot-metrics-dashboard. If you have cloned this repo, just run 'azd init' from the repo root directory.
3. Run azd up to provision and deploy the application

azd init -t microsoft/copilot-metrics-dashboard
azd up

# if you are wanting to see logs run with debug flag
azd up --debug

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.