I am working on T202233. One of the main goals I have is to allow Wikimedia event organizers to track developer activity by providing a tool that allows them to query the users for checking their contributions over time. To achieve this, I initially tried fetching developers’ activity via the Phabricator and Gerrit APIs. With each, I can get detailed information on every activity. But the problem is that Phabricator has a limit of obtaining 100 objects per request (including every activity like tasks created, subscribed comments added, etc.). I then discovered how http://wikimedia.biterg.io allows much faster and detailed queries and uses ElasticSearch to perform queries internally. With Elasticsearch API, it is not only feasible to bypass the limit; it is also very fast in comparison with individual APIs. You can take a look at it here. To use Elasticsearch, I would need the following info:
- Is the ES instance accessible for querying publicly via REST APIs (https://www.elastic.co/guide/en/cloud/current/ec-getting-started-connect.html#ec-getting-started-api)
- If so, according to the link above, I would need CLUSTER_ID, REGION, CLOUD_PLATFORM, DOMAIN, PORT details (also need the password for elastic search (>=5.0) )
- Is there some mode of authentication required which would allow my tool to access those APIs the same way we can provide them in the browser via the Web Console (https://wikimedia.biterg.io/app/kibana#/dev_tools/console?_g=())?
Is there any other way in which these queries can be made via REST APIs?