ClickHouse Cloud API
GET /v1/organizations/{id}/prometheus endpoint removal
Stops workingSubscribe to ClickHouse Cloud APIShare
On January 1, 2027, the endpoint GET /v1/organizations/{id}/prometheus will be disabled. It is already disabled for new organizations. Requests made to this endpoint after that day will fail.
Calls it hits
GET /v1/organizations/{id}/prometheus
What to use instead of these calls
Scrape through the service discovery endpoint GET /v1/organizations/{organizationId}/prometheus/discovery using the http_sd format with one target per service.
In ClickHouse Cloud API's words
This endpoint is disabled on 1 January 2027. It is already disabled for new organizations.
Facts
- API
- ClickHouse Cloud API
api.clickhouse.cloud - Kind
- Endpoint removal
- Takes effect
- January 1, 2027
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against ClickHouse Cloud API's own pages
Questions
When does this change take effect?
Calls to GET /v1/organizations/{id}/prometheus on ClickHouse Cloud API stop working on January 1, 2027.
What happens to calls after January 1, 2027?
They fail from that day.
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 ClickHouse Cloud API 1
-
No date
GET /v1/organizations/{id}/activeBalancesEndpoint 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 before January 1, 2027.