Management client shows used space for each camera, how do I find this same information via the SDK?

Config API Client sample might be helpful –

https://doc.developer.milestonesys.com/html/index.html?base=samples/componentsamples/configapiclient/readme.html&tree=tree_2.html

Thanks, Rie. I’ve played with this client quite a bit and have found it very helpful, but the only storage information I’ve found in it so far relates to entire live and archive databases. I haven’t seen anything in there that would give me the disk space used per each camera. Did I miss it?

Hi Travis, I posted a guide on accessing storage usage information on the MilestonePSTools docs site but whether you’re using PowerShell or not, it should help point you in the right direction: https://www.milestonepstools.com/Guides/Working-With-Storage/

Thanks, Josh, this is definitely in the right direction of what I’m looking for. However I’m building a C# Winforms tool so that our other admins who are not developers can access this information more easily, and therefore I won’t be able to make use of MilestonePSTools in this case. My tool currently has access to recorder and device guid’s, but I’m unsure how to call the RecorderStatusService2 interface or the GetVideoDeviceStatistics() method mentioned in your documentation. I also have not seen any references to these methods in the ConfigAPIClient tool, which is what I’ve been using so far to help me navigate the configuration.

You can instantiate a VideoOS.Platform.SDK.Proxy.Status2.RecorderStatusService2 from our MIP SDK directly, and then call the GetVideoDeviceStatistics method with a token string and list of device GUIDs. Under the hood, it’s calling the /RecorderStatusService/RecorderStatusService2.asmx SOAP interface if you’d prefer to implement the WCF proxy yourself.

Here’s an example of where that class is used in our samples on GitHub as well: https://github.com/milestonesys/mipsdk-samples-component/blob/0967968ca1e4da8de74bf8fbe56185231110eb22/StatusDemoConsole/Program.cs

That did the trick, thanks again, Josh!