Question

Monitoring API: v2/monitoring/sink and v2/monitoring/sink/destinations return 404

Posted on December 29, 2024
DigitalOcean API and CLI (doctl)Monitoring API OpenSearch
Asked by g w

Hi,

trying to use the official production Monitoring APIs at

https://api.digitalocean.com/v2/monitoring/sinks https://api.digitalocean.com/v2/monitoring/sinks/destinations

with GET or POST and in all cases receive a 404.

Was expecting to be able to retrieve lists for GETs and POST new entries as described here:

https://docs.digitalocean.com/reference/api/api-reference/#operation/monitoring_list_sinks

To be sure, I created a new full access API token to test with which did not make a difference.

Are these APIs simply not working or do I need to do something else to be able to use them?

Thank you!

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby Iliev

Site Moderator

• January 1, 2025

Hey there! 👋

As the endpoints are already available in the documentation they should all be working.

When you try to retrieve all of the sinks for a specific resource, can you confirm that you are passing the resource ID in the required format?

curl -X GET \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
  "https://api.digitalocean.com/v2/monitoring/sinks?resource_id=do:kubernetes:f2fcd5d9-f410-4f3a-8015-130ada94b1fe"

If you are passing the correct resource ID in the correct format and you are still seeing a 404 not found, what I would suggest is reaching out to the DigitalOcean support team: