Lacuna Systems

LacunaLogo

I had the pleasure of speaking with the people from Lacuna Systems at Interop a few weeks ago. I wasn’t familiar with them at all, and since they happened to have a booth on the expo floor, I was able to meet up with them and talk about their Indico platform. I’ve used a few APM(application performance management) solutions, so I am a little familiar with the space. However, Lacuna Systems is doing something a little different. Before I mention what that is, allow me to point out a few negative things regarding some of the APM implementations out there.

Cons of APM

1. Can be extremely difficult to implement. - Some APM implementations take months and many engineers to get up and running.
2. Can be extremely difficult to use. - Some APM products have so many nerd knobs that you can get lost in the sheer amount of options. If you don’t have a dedicated monitoring engineer, your APM solution might become a really expensive tool that is never used by anyone.
3. Software agents. - Installing software agents on a bunch of servers can become problematic. The agents have to be updated on occasion, and depending on how they are implemented, they can cause stability issues.
4. Interface monitoring. - It is fairly common to have to mirror all traffic coming in and out of chokepoint interfaces(physical or logical) and relay that to the APM system. Quite often, the APM system itself does not have the number of interfaces needed to aggregate all this data and you have to buy a really expensive network tap solution(eg Gigamon or Anue/Ixia). You can also potentially use up the limited number of monitoring sessions available on your hardware platforms and have to make hard decisions as to which of your monitoring platforms is more important.

Not every APM solution out there has all of the problems listed above. Some have only one or two and others don’t have any of those problems. How is Lacuna Systems different? It’s quite simple. They are only watching your load balancers, or ADC’s, for those of you who refuse to use the term load balancer.

Why Load Balancers?

How many data centers do you walk into these days that DON’T have some sort of load balancer in production? Not many, unless you are dealing with smaller environments. The traffic that flows through a load balancer is probably pretty important to an organization. Any revenue generating applications are probably sitting behind one or more load balancers. You’d want redundant servers at each tier to ensure constant availability. The easiest way to do that is with a load balancer.

Considering the traffic flowing through a load balancer is pretty important, why not focus your monitoring efforts on that traffic? That’s what Lacuna Systems does. You might think that they are missing out on a lot of other stuff in the network by only watching the load balancers. They would agree with you because they are also not trying to be all things to all people. What they are betting on is that the bulk of the information you care about from an APM perspective, is flowing through your load balancers.

How Does It Work?

Simple. They use the built in API’s from each load balancer to get the monitoring information. No network taps or port spans are needed. No remote agents on servers. None of that. They basically just need login information to your load balancer and then they can pull all the data out that they need for monitoring purposes. The Indico platform will take in all of this data and automatically build a baseline of your traffic. When there are deviations down the road, alerts get sent. I’d like to say that there is more to it than that, but that is basically how it works.

If you add new members to a load balancing pool or create new virtual IP’s on a load balancer, the Indico platform automatically detects them. You don’t have to manually update the system every time a change is made to a  particular load balancer that is being monitored by Indico.

How Can I Use It?

Today, Lacuna Systems is focusing on F5, Citrix, and A10. However, that doesn’t mean those are the ONLY vendors they will support. I asked them about future plans to support other vendors, and they told me that they’ll support whichever vendor they need to based on customer demand. Obviously, the vendors they support will also have to allow API access. Otherwise, you are looking at screen scrapes off a GUI session, which is messy trying to convert it to text, or using CLI to get data and then parsing it into a usable format.

Think beyond monitoring though. What if you could provision things for multiple load balancers from a central location? What if you were able to do this for load balancers from multiple vendors all at once? That’s where I see an additional use case with Indico. Granted, you can do that apart from Indico just by using the API’s, but since Indico is able to talk to multiple vendors, if you happen to use a variety of load balancers, it might make sense to push those changes through the Indico platform. Maybe that is something they could bake into the product down the road. Of course, customers would probably have to ask for that feature first.

More Info

Here’s a quick 15 minute video from Robert Scoble and Rackspace where Derek Andree from Lacuna Systems is interviewed about the Indico platform. It is a nice summary of the overall solution.

Just to give you a general idea of what their platforms can monitor, here are the numbers for the virtual and 2 physical appliances(Dell servers):

Indico Specs

More information is found here: https://lacunasystems.com/products.php

Closing Thoughts

There are a lot of players in the APM space. Most of them are very expensive. Depending on your needs, you may not need all of the bells and whistles that the larger APM players provide. Maybe you just need to know how your core applications are performing. If they happen to flow through a load balancer, Lacuna Systems just might be a vendor that can meet your needs. They also don’t require you to mirror your network traffic into another device for monitoring purposes since they are using API’s.

All in all, I thought it was an interesting way to monitor applications. You can check them out at www.lacunasystems.com.

Posted in data center, lacunasystems, load balancing, monitoring, network management, vendors | Leave a comment

In Search Of Swag

Just when you think you have all the vendor swag you could want, and more, someone else comes along that makes your collection look pathetic. Courtesy of Josh Atwell, I give you “The Brad”:

Posted in humor | Leave a comment

The Curse Of Matthew’s Books

Now I know what you are thinking. That’s an odd title. You might think this is about me, but it isn’t. It’s about another fella named Matthew. Perhaps the word “curse” is a bit extreme, but please allow me to explain.

There’s this guy I know. He works for Aerohive and works with the 802.11 working group. His name is Matthew Gast, and he writes books that make me lose sleep in search of further understanding. You may know him from the 802.11 Wireless Networks book and maybe even the more recent 802.11n: A Survival Guide book. That isn’t where I know him from. The first book of his that I read was this one:

T1 Book Cover

 

 

 

 

 

 

 

In case you aren’t familiar with this book, your eyes are not deceiving you. That is a book on T1 circuits and it drove me insane for a brief period. Several years ago I was reading every technical book I could get my hands on in terms of networking. I had a subscription to Safari Books Online and I was plowing through title after title at rapid pace. Lunch hours, late nights, and weekends were spent absorbing as much as I could because I couldn’t stand the thought of not knowing about everything there was to know about networking. I was working a job where there were literally hundreds of T-1 circuits spread out across a nationwide network. Any additional information I could use in regards to those circuits would be beneficial and I would be able to converse with the service providers more on their level, which would help reduce the time spent troubleshooting.

And so it was that I summoned the powers of my Safari membership and began to read an entire book on the T1. My mind was exposed to things I was somewhat familiar with. Line coding and framing modes were terms I was used to muttering when asked about how the circuit was configured. B8ZS and ESF were the stock answer, but what did they really mean? That book on the T1 exposed me to the meat and potatoes of B8ZS and ESF. I could see the 1′s and 0′s clearly. I suddenly knew how circuit alarms were generated. I was able to comprehend why the serial interface on a router showed a bandwidth of 1536kbps instead of 1544kbps for a T1. It all made sense. So much sense that I went off the deep end.

I became obsessed with Extended Superframe. I wanted to read binary and find the framing bits vs the standard channel data. In turn, I became obsessed with the Ethernet frame as well. Reading raw hex in Wireshark, I would try to see where the Ethernet header was, the IP header, TCP header, etc. It was a wild and informative ride, but I finally had to come to the conclusion that nobody really cared about that stuff. You couldn’t talk to people about it because they just didn’t feel the need to know that level of detail. It’s one thing to talk about something like BGP in great detail. There are plenty of people that will gladly engage you in those kinds of discussions. It is a completely different kind of party where people want to discuss the finer points of B8ZS vs AMI or why ESF yields 1.544Mbps when you add all the 1′s and 0′s up. The ONLY people that are probably even remotely interested in that stuff are voice engineers. Even then, apart from understanding sampling rates, and why a DS0 is 64kbps, they probably don’t care about the rest.

I put that period of insanity behind me. I swore off the urge to obsess over the finer points of technology and wanted to just be a decent all-around network guy. The following years were full of routing, switching, wireless, load balancing, WAN optimization, monitoring, firewalls, and any other type of networking to be had. Nothing too crazy and nothing too deep.

Fast forward a few years and I had read a few more of Matthew’s books:802-11WirelessNetworks

 

 

 

 

 

 

 

802-11n

 

 

 

 

 

 

 

And then, about a month ago, I got my hands on an early release copy of his new book:

802-11ac

 

 

 

 

 

 

 

I read the entire thing, and for some reason, I had another “T1 episode”.

I’m currently on week 2 of layer 1 obsession as it relates to WiFi. Suddenly, I don’t feel competent in the realm of wireless until I can whiteboard every little thing that happens when the energy leaves the antenna on the AP and makes its way to the client or vice versa, and I am not even concerned with the higher layers yet. I find myself watching anything on YouTube that even remotely resembles RF fundamentals. I’ve got several books from different publishers on wireless communications that I have been skimming through, but I still want to know more. What I want is what I cannot have and that is to be able to see those little wireless waves travel through the air. I want to see that phase shift. I want to see the amplitude adjustment happen in a split second and be able to map a point on a  constellation diagram and know that the little dot that I just mapped is the binary equivalent of 01100101. Of course, that might be asking too much and how many customers would even be interested in that level of detail? It would probably weird them out if you started spouting off binary strings like you had a bad case of Tourette’s syndrome.

I hope Matthew’s next book will be a picture book. That would make it easier on me. :)

Posted in learning | 1 Comment