Inspect our API endpoint for optimal performance

[sharon-fdm]

Goal

User story
As a customer managing a large number of hosts,
I want Fleet server API endpoints to be evaluated for performance,
so that bottlenecks can be identified and optimized to reduce the risk of outages.

Changes

Engineering

We will conduct a time-boxed research effort to identify inefficient Fleet server API endpoints.
In alignment with our company values, we will prioritize the most problematic and highest-impact bottlenecks.
Based on the findings, we will create follow-up tasks to optimize and improve those endpoints.

• Test plan is finalized - no test plan
• Contributor API changes: NO
• Feature guide changes: NO
• Database schema migrations: NO
• Load testing: NO
• Pre-QA load test: NO
• Load testing/osquery-perf improvements: NO
• This is a premium only feature: Yes / No

ℹ️  Please read this issue carefully and understand it. Pay special attention to UI wireframes, especially "dev notes".

QA

Risk assessment

• Requires testing in a hosted environment: NO
• Requires load testing: NO
• Risk level: Low / None
• Risk description: This is a research to find inefficient API endpoints

Test plan

Make sure to go through the list and consider all events that might be related to this story, so we catch edge cases earlier.
No tests required

Testing notes

Confirmation

1. Engineer: Added comment to user story confirming successful completion of test plan.
2. QA: Added comment to user story confirming successful completion of test plan.

[sharon-fdm]

cc @lukeheath for prioritizing
I'm happy to apply a P2 to be taken next sprint (or if we are available this sprint)

[lukeheath]

@sharon-fdm Thanks for the detailed issue. I've prioritized to the drafting board and assigned to you to coordinate getting this drafting and into a sptint.