droplet history and api calls

  • Posted on March 6, 2015
  • API
  • GROK7Asked by GROK7


We are a new customer to Digital Ocean. We have noticed yesterday after several API calls to power/off/on and rebuild instances that the droplet history has not reflected those actions. Should we aspect the history to account for API calls? Let me know if I should file a support ticket.


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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

The event history shown on the droplet page will only include control panel events. By clicking on Settings->Security you can view the full security log which includes all events via the API or Control Panel.

My droplet was “restored”, but I’m looking for more information about what happened. Who restored it? How? Where? From the terminal? From the console? Which backup did it restore it to?

Where can I get a detailed history of what happened to my droplet?

Awesome! Danke!