mirror of
https://github.com/empayre/fleet.git
synced 2024-11-06 08:55:24 +00:00
2520fc2179
📺 Loom: https://www.loom.com/share/9e17848963574af3aa10d426b450bcd0?sid=f8078293-c7e1-4864-a8a3-4cec996971f5 #15476 #15540 #15542 After upgrading fleetd, customer-blanco saw a spike in traffic and a spike in DB connections. These fixes attempt to reduce the traffic and DB load when fleetd is upgraded. On the server, added fleet/device/{token}/ping endpoint to be used by agents to check their token. On the agent: - Removed call to fleet/orbit/device_token unless token needs to be updated. - Changed call to fleet/device/{token}/desktop with a less resource intensive call to fleet/device/{token}/ping - Removed call to fleet/orbit/ping # Checklist for submitter If some of the following don't apply, delete the relevant line. <!-- Note that API documentation changes are now addressed by the product design team. --> - [x] Changes file added for user-visible changes in `changes/` or `orbit/changes/`. See [Changes files](https://fleetdm.com/docs/contributing/committing-changes#changes-files) for more information. - [x] Manual QA for all new/changed functionality - For Orbit and Fleet Desktop changes: - [x] Manual QA must be performed in the three main OSs, macOS, Windows and Linux. - [x] Auto-update manual QA, from released version of component to new version (see [tools/tuf/test](../tools/tuf/test/README.md)). |
||
---|---|---|
.. | ||
.keep | ||
11958-remove-glibc-requirements | ||
12842-orbit-bitlocker-management | ||
14176-orbit-retries | ||
14380-rpm-graceful-upgrade | ||
14546-orbit-not-reporting-bitlocker-errors | ||
14633-bump-go | ||
14657-log-flag | ||
15539-removing-duplicate-device_token-calls | ||
15540-reduce-server-load-from-fleetd-upgrade | ||
15541-reduce-agent-calls-to-orbit-config-endpoint | ||
go-update |