Change Details

**Name for main point of contact and contact preference** Seve Kim via phab task comment/slack **What teams or departments is this for?** Platform Engineering (API Platform Team), Tech Dept **What are the details of your request? Include relevant timelines or deadlines** I want to create an evolving dashboard to compare the requests made per API and API endpoint for the following APIs: - [[ https://en.wikipedia.org/w/api.php | MediaWiki Action API ]] - [[ https://www.mediawiki.org/wiki/API:REST_API | MediaWiki REST API ]] - [[ https://en.wikipedia.org/api/rest_v1 | Wikimedia REST API ]] It would be a great starting point to see the following dimensions: - User Agent - HTTP Method - HTTP Status - URI Path - URI Query - Content Type - Response Size We are hoping to start interviews and begin API migration planning by Q1 (Mid-July). **How will you use this data or analysis?** This data will help inform: 1. Who we consider interviewing for defining our API consumer personas 2. What legacy APIs we prioritize to migrate to the API Platform **Is this request urgent or time-sensitive?** No, it would support our work but does not block us

**Name for main point of contact and contact preference** Virginia Poundstone via phab task comment/slack **What teams or departments is this for?** Platform Engineering (API Value Stream) **What are the details of your request? Include relevant timelines or deadlines** We need to create a **dashboard ** to compare the requests made per endpoint for the following APIs: - [[ https://en.wikipedia.org/w/api.php | MediaWiki Action API ]] - [[ https://www.mediawiki.org/wiki/API:REST_API | MediaWiki REST API ]] - [[ https://en.wikipedia.org/api/rest_v1 | Wikimedia REST API ]] - {T329907} captured preliminary data from RESTbase about who the clients are It would be a great starting point to see the following available data per endpoint: - user_agent - user_agent_map - access_method - ip - HTTP Method - HTTP Status - URI Path - URI Query - Content Type - Response Size Data Analysis goal: Define the major "buckets" or types of client callers so we can design an API Architecture with their use cases in mind. A secondary goal is to determine what services are used the most to the least and by whom, for what purpose and how much. **How will you use this data or analysis?** This data will help inform: 1. Product decisions based on current API usage 2. What endpoints we prioritize to maintain and enhance **Is this request urgent or time-sensitive?** It supports our ongoing work, until we have this data, we are making decisions based on guesses. THat said, this feels urgent, but is not technically blocking us.

**Name for main point of contact and contact preference** Seve KimVirginia Poundstone via phab task comment/slack **What teams or departments is this for?** Platform Engineering (API Platform TValue Stream), Tech Dept **What are the details of your request? Include relevant timelines or deadlines** I wantWe need to create an evolving **dashboard ** to compare the requests made per API and API endpoint for the following APIs: - [[ https://en.wikipedia.org/w/api.php | MediaWiki Action API ]] - [[ https://www.mediawiki.org/wiki/API:REST_API | MediaWiki REST API ]] - [[ https://en.wikipedia.org/api/rest_v1 | Wikimedia REST API ]] - {T329907} captured preliminary data from RESTbase about who the clients are It would be a great starting point to see the following dimensions:available data per endpoint: - User Agent- user_agent - user_agent_map - access_method - ip - HTTP Method - HTTP Status - URI Path - URI Query - Content Type - Response Size We are hoping to start interviews and begin API migration planning by Q1 (Mid-July)Data Analysis goal: Define the major "buckets" or types of client callers so we can design an API Architecture with their use cases in mind. A secondary goal is to determine what services are used the most to the least and by whom, for what purpose and how much. **How will you use this data or analysis?** This data will help inform: 1. Who we consider interviewing for defining our API consumer personasProduct decisions based on current API usage 2. What legacy APIendpoints we prioritize to migrate to the API Platformaintain and enhance **Is this request urgent or time-sensitive?** NoIt supports our ongoing work, until we have this data, we are making decisions based on guesses. THat said, this feels urgent, it would support our work but does notbut is not technically block using us.