Purge Oracle Metric Cache

Drops the copy of a metric provider's source document held by the server process that answered the request, so a corrected sheet shows up now instead of after the provider's cache_ttl_seconds. Only the SHEET provider keeps a document; other server processes keep theirs until their own cache window ends.

Unlike Purge Oracle Cache there are no shared summaries to drop: metric summaries are read from the source on every request, so summary_entries is always 0.

Required permission: oracle:update

Request

DELETE /v2/admin/oracle-metrics/{oracle_metric_id}/cache

Parameters

Name	Type	In	Description
oracle_metric_id	string	path	Required. Metric provider id (24-character hex)

Headers

Name	Description
Authorization	Required. Bearer <access_token>

Example

curl --request DELETE \
  --url '{{baseUrl}}/v2/admin/oracle-metrics/6a5d0206379ebd02e53bf1a1/cache' \
  --header 'Authorization: Bearer <access_token>'

Response

{
  "summary_entries": 0,
  "document_cleared": true
}

Response Fields

Field	Type	Description
summary_entries	integer	Always 0 for metric providers
document_cleared	boolean	Whether the answering process held a copy of the source document and dropped it. false means nothing was cached there

Errors

Status	Code	Description
400	10000	oracle_metric_id is not a valid 24-character hex id
400	10001	Metric provider not found or deleted (domain 53)

See Errors for the error format and common codes.