FrameFlow Newsletter – June 2015

FrameFlow v2015.2

As most of you have seen, we released the long awaited v2015.2 on June 9th. Since then we’ve seen that many of you have already upgraded and have taken advantage of the new features and functionality that we delivered in this release.

The major change is the addition of new alerting levels. Now instead of just success and failure, your event monitors can generate success, warning, error and critical alert levels. This gives you a great way to prioritize your efforts, especially when there are multiple system issues going on at the same time.

More than that, it has also helped us to simplify and organize many things throughout the FrameFlow interface. One example is in system health dashboards. In previous releases you would define one set of thresholds in your system health event monitor, which would define the difference between success and failure. Then, in your dashboard you would select another set of thresholds that defined the lines between success, warning and error. With v2015.2, and later, your dashboards automatically pick up the thresholds used by your system health event monitors so everything is consistent and you have one single place where you select your thresholds.

That’s just one example, but we’ve made similar changes throughout the user interface.

And Now… FrameFlow v2015.3!

The roll out of v2015.2 went very smoothly for most of you, but we did run into severe problems at a few customer sites. In particular, we discovered two issues that could cause the monitoring service to stop.

The first one was related to certain notification actions which could cause an exception in the service. We worked with several customers to track this one down and, a few days after the release, we had a hotfix for it. This hotfix has been incorporated in v2015.3 which was released on June 26th.

The second issue had to with SNMP monitoring. We’ve incorporated a new high-performance SNMP engine and it works great in controlled environments. Our tests have shown it to be at least 10 times faster that our previous engine, allowing you to monitor more systems on a faster schedule. Unfortunately, in real world testing it has also proven to be a bit unstable. To work around this, the new engine is off by default in the 2015.3 release. We are currently working with a number of customers to stabilize the new engine and once we are confident that it is solid, it will become the default in a future release.

The 2015.3 release also includes fixes for smaller issues that have been reported. It’s the current recommended release and as usual you can get it by logging into your account on our site.

Server Monitoring Industry News

Here is a piece of news that is probably the sort of thing that can only be appreciated by server monitoring nerds like us. Wait for it, yes it’s true: Microsoft is Adding SSH Support to Windows

If you’re like us, you probably just fell out of your chair or maybe punched the air a few times.

As far back as the days of Windows 2000, we remember booting up the latest from Microsoft and thinking: “Wow, lots of cool new stuff but still no support for SSH. I’m sure they’ll get to that in the next release.

Firmly in the category of “better late than never,” it seems we’ll finally get secure command line access to Windows boxes via SSH some fifteen to sixteen years later. We have to be a bit vague on the timing, you see, because Microsoft so far can only say that they “will provide details in the near future on availability dates.”

FrameFlow Newswire

That’s all for this newsletter, but before you get back to business, be sure to check out the latest from FrameFlow Newswire.

Press Release: FrameFlow Announces Second Headquarters Move

The FrameFlow Support Team
FrameFlow: Keep the Servers Going, Keep Your Network Flowing