@Scott_French I am waiting for final go ahead from QA . I will let you know once tag is created ,

@Scott_French The CI pipeline is ready , can you have a look at https://gitlab.wikimedia.org/repos/generated-data-platform/aqs/commons-impact-analytics/-/pipelines

@hnowlan The service does have any api spec , which the service is exposing at /commons-impact-analytics/api-spec.json.

@mforns and @EChukwukere-WMF The problem is that we do not have any aggregation in test environment , previous AQS 2.0 services had some of the rows like this
"analytics.wikimedia.org","all-wikipedia-projects","all-sites","daily","20180101","13814000-1dd2-11b2-8080-808080808080","","128209697","33568105","94641592"
We got this from production cassandras , I am unsure how we should handle this . There can be multiple approaches -

• Copy aggregation logic from prod to test environment .
• Add multiple rows having all-edit-types as edit-type.
• Copy aggregated data from cassandra db.

@mforns We must change it in this document

However, the source data is already cut to the top 100. So, the final result will be the top 100.

@mforns Is it not 1000 ?

In T358722#9880653, @apaskulin wrote:

I have a few questions to help clarify the docs:

• For the endpoints that return a time series without monthly in the path, what is the granularity of the data?
• For the ranking endpoints, is there a limit on how many results are returned? For example, the top 100

@mforns I fixed your comments , the new page is here https://wikitech.wikimedia.org/wiki/AQS_2.0/CommonsImpactAnalytics

@apaskulin @Sfaci This is the MR for API spec handler endpoint
https://gitlab.wikimedia.org/repos/generated-data-platform/aqs/commons-impact-analytics/-/merge_requests/8

Hi @apaskulin The docs are already on main branch but you may review them on this patch as well
https://gitlab.wikimedia.org/repos/generated-data-platform/aqs/commons-impact-analytics/-/merge_requests/6

@Emeka-okechukwu I have fixed these issues for not found route error message and correct error messages. Please verify.

Hi @Scott_French We are almost done coding the services , what would be the next steps ? What are the tasks we could take up ourselves or others for which we will depend on SREs?

@WDoranWMF Please approve.

@Scott_French Thank you ! We are in process of creating the cassandra tables accounted in this task. Will update the task once we have cassandra tables defined and a minimal build is ready

@WDoranWMF Yep , it makes sense . I confirmed with @mforns that API paths and we agreed on metrics/commons-analytics . Regarding the prefix , all the AQS services use /api/rest_v1/metrics , we could use that from consistency perspective . But still will like @VirginiaPoundstone to confirm .
Also , we are developing CIM AQS services in gitlab . Would that make any significant difference? Should we raise a ticket for CI of the same?

Added phab Two-Factor authentication . Thanks!

@Sfaci @WDoranWMF @VirginiaPoundstone Just shared this doc for review .

Hi @WDoranWMF Should we mark this one as done as we already have a draft version of SLOs for DA?
Thanks

hi @WDoranWMF I think we could conclude this task as the dimensions and SLIs have already been identified.

In my opinion the service responds with desired application/json+problem when correct basepath is provided . The other responses returned by rest gateway or restbase differ and since the basepath in itself is incorrect , is not obligated to return the same response as of service