Add the capability to track how many V2 request we're getting so we can plan deprecation

[ParkerM]

I'd be happy to tackle this if you could provide some leads on available resources for persisting the data.

[karianna]

@johnoliver or @gdams are you able to connect with @ParkerM and give him v2 Bootcamp?

[ParkerM]

Here's a basic impl that uses MongoDB to persist a hit counter for each /v2/ endpoint: https://github.com/AdoptOpenJDK/openjdk-api/compare/master...ParkerM:usage-stats

I tested it on an Atlas free tier instance and it seems stable enough. The v3 API already has a Mongo instance so hooking it up to that should be as simple as adding a collection and plugging the URL/credentials into db.service.js. If that sounds like a plan then I can add an endpoint or two that exposes the gathered metrics and submit a PR.

[karianna]

@gdams - Will App Insights give us this functionality? Else we could look to add ParkerM's feature

[joschi]

Would it be possible to retrieve this information from HTTP access logs to https://api.adoptopenjdk.net/v2/*, assuming that these are recorded?

[gdams]

@johnoliver Can we now verify that we can identify V2 requests coming from the graphql server?