When several events, policy discovery requests (observations), or inventory updates are received on the ePO - On-prem server, the ePO - On-prem interface might become unresponsive or sluggish. The throttling feature helps avoid such scenarios.
You can control the flow of events, policy discovery requests, and inventory updates. When the data sent to the ePO - On-prem server reaches the defined threshold for an endpoint, throttling is initiated and these actions are taken.
Data is no longer sent to the ePO - On-prem server.
Data is stored in a cache at the endpoints. When the cache is full, data starts dropping with the oldest.
Note
Data is stored in the cache only for events and policy discovery requests. The inventory data isn't stored in the cache; instead, it is updated at the endpoints locally.
Throttling is reset no less than 24 hours after the first event, policy discovery request, or inventory update for the day.
Note
When throttling of inventory updates is initiated, the Pull Inventory client task is disabled. This indicates that you can't fetch inventory until throttling resets.
Data stored in the cache is sent to the ePO - On-prem server in batches (starting with the oldest data).
After throttling resets for events and policy discovery requests, further generated data is stored in the cache and not sent to the ePO - On-prem server until the cache is empty.
The throttling feature is available on all supported Windows platforms. You can manage throttling by identifying the endpoints where throttling is initiated and taking remedial actions. If needed, you can configure throttling for your enterprise.