# Identify users with performance issues Analyzes and identifies users experiencing the slowest feed operation times. Can analyze a specific operation or aggregate across all operations. RBAC: - requires ANY of Jobs.Read, Jobs.Manage Endpoint: GET /api/v1/admin/feed/metrics/slowest-users Version: 1.0 Security: ## Query parameters: - `limit` (integer) Maximum number of users to return (default: 10) Example: 10 - `operation` (string,null) Optional specific operation to analyze Enum: "populate", "merge", "unmerge", "redis", "redisLex", "cache", "idsDb", "db", "add", "remove" - `ownerType` (string, required) Owner type to analyze Enum: "USER", "EVENT", "CATEGORY" - `window` (string, required) Time window for analysis Enum: "TEN_MINUTES", "ONE_HOUR", "TWENTY_FOUR_HOURS" ## Response 200 fields (application/json): - `slowestUsers` (array, required) - `ownerType` (string, required) Owner types for posts: * USER - user’s channel (personal or group channel) * EVENT - event (personal or group) * CATEGORY - forum category POST OWNER: - Personal channel - userId = author - ownerId = userId (Type.USER) - ownerType = USER - groupId = null - Forum post - userId = author - ownerId = categoryId (Type.CATEGORY) - ownerType = CATEGORY - groupId = forum’s groupId - Personal event - userId = author - ownerId = eventId (Type.EVENT) - ownerType = EVENT - groupId = null - Group channel - userId = author - ownerId = channel userId (Type.USER) - ownerType = USER - groupId = groupId - Group event - userId = author - ownerId = eventId (Type.EVENT) - ownerType = EVENT - groupId = groupId Enum: "USER", "EVENT", "CATEGORY" - `operation` (string,null) Enum: "populate", "merge", "unmerge", "redis", "redisLex", "cache", "idsDb", "db", "add", "remove" - `limit` (integer) ## Response 403 fields (application/json): - `errorCode` (string, required) Error code - `message` (string, required) Error message - `docUrl` (string) Link to documentation