GITHUB COPILOT USAGE METRICS API MAPPING FROM OLD TO NEW

[vaidshah]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

API

Body

We were previously using the deprecated GitHub Copilot Usage API to power our internal dashboards. With the deprecation and move to the new API, the response structure has changed, and as a result, our dashboards are no longer functioning.

To get our dashboards back up and running, we require a clear mapping between the old API response and the new API response.

Specifically, we are looking for:

Field-level mapping between old and new response schemas
Details on renamed, removed, or newly introduced fields
Guidance on how to handle fields that no longer have direct equivalents

This information will help us update our existing dashboards with minimal disruption.
old api -https://api.github.com/orgs/congaengr/copilot/metrics
new api-/enterprises/{enterprise}/copilot/metrics/reports/enterprise-1-day

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐