A lot of us who work with TrueSight are still think that the product goes in the right direction. However, the big "but" hangs in the air. We know all the complaints we have and we know all the complaints the users have we have TrueSight implemented for. We know all the phrases
- Please make this usable!
- Why is this and this missing?
- Why untill here and not a step further?
- Was this tested in a first place?
- Why can't I see this? Where is the transparency? e.g. agent based thresholds
- and so on
We all know: complaining is so easy.
Somtimes it helps, but most times it doesn't really help.
Let us try another approach. Let us describe how TrueSight should be. Maybe this helps more than just complaining.
Ok, where should I start? Let us start at the bottom: the PATROL Agent. How should it be? First, it should be easy to install. Idealy it should leverage the installation mechanisms the operating systems provide. The agent is the starting point. Everything else (KMs, etc.) should be deployable from the TrueSight infrastructure. Obstacles like accounts and passwords should be left out (e.g. like already possible on Windows). There should be simple ways to debug the agent. For example, the PATROL Agent logs should be automaticaly centralized through the existing connectivity or at least it should be possible to fetch them on demand throught the TrueSight UI. Also the creation of a diagnostic report must be possible. I also imagine that there is a at the glance view for the agent which provides all necessary information like versions of agent and KMs, all installed components, the configuration and other runtime information.
Next step: configuration. There should be a structure which allows intheritance. I think, we all have kind of a default configuration. Every further configuration should be only the delta to the default. This should work in every direction. Adding something to the default, removing something from the default and customization of the default. Have I left something out? For specific configuration tasks also a kind of "expert mode" would be helpful. It should be possible to switch in export mode in any configuration and directly modifying the resulting configuration variables. Of course configurations should be exportable and copyable. There has also to be an import function in the UI. Also an advanced tagging functionality should be provided.
Big topic: the TrueSight UI. Right, everything should be possible from a single entry point. Of course it has to be performant. It must be intuitive and as simple as possible. Data like operating system, operating system version, tags, hostnames etc. should be available for creating groups. All graphs should be exportable and it should also be possible to export the data as csv or similar format. The user should have the possible to compare measurements also from multiple devices. The user should be able to leverage highly customizable dashboards and if possible be able to create his own custom dashlets.
What do you think? How should your TrueSight be?