Have you heard of Uila? Maybe you should have!

So a little while back, I had a demo of some unusual, and very interesting software.  As you might know, I used to be a professional services guy, and I learned how to be successful by solving technical issues that customers had.  It was not just about installing email or virtualization software but doing it in a way that actually solved issues and doing it in a way that allowed the customer to truly exploit it. I am also a true BCDR guy.  I have had customers lose stuff, and helped them rebuild enough times so that whether I wanted to or not, I am a BCDR guy at heart.  So when I heard about this software, and they were talking about root cause, and full stack monitoring, I realized it sounded pretty good.  Often companies I know do not always do root cause as it can be hard, and expensive.  So if software could help, that is a big deal.  When I heard about the ability to recognize 2700 applications that really got the BCDR part of me interested as packaging applications to protect them is hard when you don’t know all the components – and in fact you end up doomed with lots of problems and lots of testing to make things work.

Who is this you ask? It is Uila and you can find them here.

So I was interested to say yes to the chat and demo. They have patents, lots of customers – including some that I know so that is all good.

In the few slides that they shared first I found some interesting stuff.

I bet you have experienced this sort of thing yourself – right?

Thanks to Uila for the image.

I have personally – often – been in that picture or some version of it. I have tried to bring that picture – improved of course – to life in a few environments – meaning that when a user has an issue, that the IT people can see the full stack and not deal with silo’s.  But that is hard indeed. And some of the monitoring tools out there make it even harder as they look at the layers, or the VMs and not the services. And silos too make it tough.

But it got really interesting when the demo started.  They do full stack monitoring (with correlated analytics too), and as part of that do the full application viability and dependency mapping which is important to me.  They showed how they can do really nice end-user monitoring.  Really nice in fact.

Some of the cool examples that this software can do that impresses me:

  • You can profile normal operations of an application, and then when a user thinks it is slow,you can see the difference and zero in on the issue.
  • SSL configuration issues can be seen and in fact highlighted in the UI.
  • Software that you are trying to block, like Dropbox, can be detected, and easily seen the source usage.
  • I don’t quite understand how yet, but it can be a tool to help with change control.  And that is handy.

Something else that I like is that they have a management platform that can be installed and used in-house, or there is an SaaS version too – particularly useful if you want to manage / monitor both on-prem and Cloud.

How do they do this sort of thing?  It is with deep packet inspection and I suspect with a lot of knowledge on their side. There is a lot of analysis that makes things look pretty easy! I also appreciate that they do not use agents, and I do not have to make changes in my networking or environment to support them.

But I am not going to talk too much about them.  I am going to get them going in the lab, and see how it does.  Then I will talk – and show – more about them.


=== END ===

Leave a Reply