Datadog API
GET /api/v1/usage/timeseries endpoint removal
Deprecated, no dateSubscribe to Datadog APIShare
Datadog has deprecated the GET /api/v1/usage/timeseries endpoint without specifying a shutdown date. Calls made to this route are slated for removal and will eventually fail. Datadog API notes that hourly usage data for all products has moved to an alternate endpoint.
Calls it hits
GET /api/v1/usage/timeseries
What to use instead of these calls
Read hourly usage with GET /api/v2/usage/hourly_usage (filter[product_families]) instead.
In Datadog API's words
This endpoint has been deprecated. Hourly usage data for all products is now available in the [Get hourly usage by product family API](https://docs.datadoghq.com/api/latest/usage-metering/#get-hourly-usage-by-product-family).
Facts
- API
- Datadog API
api.datadoghq.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Datadog API's own pages
Questions
When does this change take effect?
Datadog API deprecated GET /api/v1/usage/timeseries without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Datadog API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Datadog API 8
-
No date
/api/v1/downtime*Endpoint removal Deprecated, no date -
No date
/api/v1/integration/awsEndpoint removal Deprecated, no date -
No date
/api/v1/integration/gcpEndpoint removal Deprecated, no date -
No date
/api/v2/metrics/config/bulk-tagsEndpoint removal Deprecated, no date -
No date
GET /api/v1/searchEndpoint removal Deprecated, no date -
No date
GET /api/v1/usage/hostsEndpoint removal Deprecated, no date -
No date
GET /api/v1/usage/logsEndpoint removal Deprecated, no date -
No date
POST /api/v2/dora/incidentEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.