Provide tools for inspecting reliable collections
If I'm going to move some of my core application state from an external state store to reliable collections, I would like to have equivalent tools for inspecting that state apart from the VS debug window.
Last update on here was 15 months ago. Is this started? or still in the planned phase
There's a comment below from Azure saying in Dec 2017 "We'll be releasing this feature in the upcoming months.", that's been over a year. Is this still coming?
Hired Mind commented
Please, I beg of you, just add a StateProvider.LoadStateAsync() method without a type parameter. Even if it only returns the serialized form of the state as a string, that's fine. Right now, actors from 3rd-party libraries are a complete black box at runtime. If something goes wrong, I have no hope of debugging them, because in order to use StateProvider.LoadStateAsync<T>() I have to know the type of their state beforehand. Adding one method could be done quickly rather than create an entire tool set.
Any update on when this will be released?
We'll be releasing this feature in the upcoming months.
Mark showed this off at Ignite 2017, not sure if it has been released yet?
Check out this tool on github
Charles Lazarr commented
It looks like the Service Fabric development team at Microsoft has been working on this feature (yea!). Mark Fussell did a quick demo of some features 'on the road ahead' (near term futures) at Ignite 2017. The demo included a Data Explorer UI within the Service Fabric Explorer web UI for a deployed service using reliable collections. Demo of this starts near the end of the video around the 1:03:20 time mark - https://myignite.microsoft.com/videos/55068
This has been under review for 2 years now. Is this kind of tooling being worked on? Would certainly benefit the adoption of stateful services by the community.
Stas Sultanov commented
possibly it should be integrated into the cluster manager.
Søren Enemærke commented
Not only from the VS debug window, I'd like some ready-made tool to inspect/query/edit this data rather than having to build an "admin API" into the services for handling specific scenarios. Without this, I have no quick way of finding/changing/handling incorrect data stored in a reliable collection in a production environment