We wanted to get a sense of how many of you use Dr Nimbus and how often. Do your customers use it? and is it satisfactory to simply keep it as a windows utlity?
I show Dr. Nimbus on almost every POC as techies generally think its "cool". It's interesting to them that we have this tool that can read messages off our bus and view messages in queues.
I've used it occasionally in some support cases. It's been helpful.
I use Dr Nimbus quite a lot - it's a great diagnostic tool for investigating issues with "missing" alarms and/or QoS. It is however quite dangerous if used in the wrong hands - you can easily remove messages from a queue if you're not careful. Also not to be shown if there are security people in the room - gives you access to file transfer with root/administrator priviliges.
I'd be happy for it to stay as a windows utility but what we really need is an easy way to ask these questions directly to the wider user community - may add a section to the Support forum e.g. "Product Management Survey" or something like that where customers can vote; similar to the enhancement request voting but for feature removals or non-development.
I too use Dr. Nimbus, mainly when diagnosing problems, but also when trying to do integration with other systems.
I cannot say that I have used DrNimbus frequently, but I have used it on many occasions and found it to be indispensable those times.
I am a little curious about which features of DrNimbus people use the most. I think I have used the file transfer feature once or twice, but I do not really need it. For me the real killer feature is the ability to subscribe to the message bus on any hub. It can be very helpful for troubleshooting. There have been times I would have liked a way to do that from Linux as well. I tried to create a Lua script that woudl do it, but the Lua function for subscribing to messages does not allow you to specify a hub. If it did, that would probably be a good replacement for DrNimbus for my purposes. (It might be possible to do this in one of the other SDKs; I have not looked.)
I use Dr. Nimbus frequently.
The main uses are:
a) sniff messages on the message bus (that is so important when trying to debug custom probes and/or behaviour between components)
b) look into queues (again to debug. e.g. when miss-formatted messages are blocking a queue)
The file copy functionality is great but can scare customers because it actually is a huge security risk. I wouldn't miss that.
I too use DrNimbus frequently for custom development and troublshooting. I am OK with it staying a Windows Utility as I (and most customers) still use Infrastructure Manager. A DrNimbus portlet would be pretty cool though.
Retrieving data ...