Refresh bandit
Changed onStart a refresh of a running bandit now, instead of waiting for its schedule. The refresh reads the bandit's latest data and saves new results. Outside warmup it also serves the traffic split it proposes, so it can change traffic. HTTP 202 confirms the refresh started, not that it finished. The response returns the refresh ID, which the bandit then reports as latest_refresh. Bandits must be enabled for the organization.
Request
- Base URLhttps://api.datadoghq.com
- Auth
- API key in header DD-API-KEY and API key in header DD-APPLICATION-KEY
- or OAuth 2Authorization code/oauth2/v1/authorizeToken URL/oauth2/v1/tokenScopesproduct_analytics_experiments_write
Path parameters
The UUID of the bandit.
Query parameters
Recompute the bandit's whole history instead of updating its latest refresh; for example, after its exposure or metric data was backfilled. Defaults to false.
Recompute the bandit's whole history instead of updating its latest refresh; for example, after its exposure or metric data was backfilled. Defaults to false.
Response
Accepted
Example response
{
"data": {
"attributes": {
"bandit_id": "4b1f3c2e-8d5a-4f6b-9c7e-1a2b3c4d5e6f"
},
"id": "cc1e8400-e29b-41d4-a716-446655440000",
"type": "bandit-refresh"
}
}Changes
- warning
the optional response header
X-RateLimit-Limitremoved for the status429 - warning
the optional response header
X-RateLimit-Periodremoved for the status429 - warning
the optional response header
X-RateLimit-Remainingremoved for the status429
1 more change in this revision
- warning