test /mod-notify/patron-notice API endpoint performance
CSP Request Details
None
CSP Rejection Details
None
CSP Approved
None
Description
Environment
None
Potential Workaround
None
Attachments
10
relates to
Checklist
hideTestRail: Results
Activity
Show:
Duplicate
Details
Assignee
UnassignedUnassignedReporter
Hongwei JiHongwei JiLabels
Priority
P3Development Team
VegaTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Unassigned
UnassignedReporter

Labels
Priority
Development Team
Vega
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created September 18, 2019 at 2:11 PM
Updated February 12, 2021 at 12:50 PM
Resolved February 12, 2021 at 12:50 PM
Per
"Oleksii Maksymov, just a FYI that since this ticket was created, we have narrowed some performance issues related to mod-authtoken and mod-permissions (mostly mod-permissions because mod-authtoken calls mod-permissions). The log provided in this ticket does not show that because at that time the Okapi "requestId" was not passed/logged from module->auth->permissions yet. So if you can directly test /mod-notify/patron-notice API endpoint and proves that it indeed performs good, we can focus on mod-permissions performance. Thanks."