-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the ability to be able to query the number of downloads for each (componentID, version) #44
Comments
Plan of action:
The cloud-watch graph will be accessible via aws console. |
@hspencer77 will be adding tags manually for the latest version of all components to get the data. In parallel, we are working on adding tags to the new extensions: brave/brave-core-crx-packager#123 Component list:
|
Completed the following:
Metrics were just enabled, so we won't see any metrics associated with anything before today. Please let me know if there are any additional questions. |
Added metric filters per https://github.com/brave/devops/issues/3167. Filters are in place:
|
It would be good to know the amount of users for each component that we have.
I think this would look like just a mapping of (componentID, version) => countI think to do this the URLs returned from the go-update server would be to itself, which would then redirect to the real URL. A map could be updated with a count, and there could be a task that updates the DB with the counts periodically (e.g. once per minute for example). I'd recommend against 1 update to the DB per component download request.
On startup, the count would be taken from dynamodb so that if the component is updated, the counts don't start back at 0.
brave-core-crx-updater could perhaps get an additional small script with command line params that allows you to query a component ID and a version (or omit version to get the latest version) to get a count directly from dynamodb.
The architecture described here is just an idea, I'm open to other ideas. E.g. maybe log based and then an aggregator would be another approach.See plan below by @jumde 👍
The text was updated successfully, but these errors were encountered: