Timeseries API v1 - DELETE a custom metric
Deletes the specified custom metric. If you delete a metric definition, you lose all of that metric's data, so be careful with deletes.
Built-in metrics can't be deleted.
| DELETE | SaaS | https://{your-environment-id}.live.dynatrace.com/api/v1/timeseries/{timeseriesIdentifier} |
| Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/v1/timeseries/{timeseriesIdentifier} |
Authentication
To execute this request, you need an access token with DataExport scope.
To learn how to obtain and use it, see Tokens and authentication.
Parameters
| Parameter | Type | Description | In | Required |
|---|---|---|---|---|
| timeseriesIdentifier | string | The ID of the metric to delete. | path | required |
Response
Response codes
| Code | Type | Description |
|---|---|---|
| 204 | - | Success. The custom metric has been deleted. |
| 4XX | Error | Client side error. |
| 5XX | Error | Server side error. |
Example
In this example, the request deletes the custom:firewall.connections.dropped custom metric.
The API token is passed in the Authorization header.
Curl
curl -X DELETE \https://mySampleEnv.live.dynatrace.com/api/v1/timeseries/custom:firewall.connections.dropped \-H 'Authorization: Api-Token dt0c01.abc123.abcdefjhij1234567890'
Request URL
https://mySampleEnv.live.dynatrace.com/api/v1/timeseries/custom:firewall.connections.dropped
Response code
204