There's a beta release of FrameFlow v2020.1 available. Version 2020.1 will introduce a new Info status level that sits between the existing Success and Warning levels. Info status appears in blue and is best used for conditions that you want to know about but don't really qualify as a full-blown alert.
In this release the Info status level is available in the Windows Update event monitor and in the File event monitor. In the official v2020.1 release, which is due in mid-February, it will be available in the majority of the other event monitor types as well.
Existing customers can get the beta release by logging into their account on our web site. If you are currently evaluating FrameFlow, and would like to try the beta, get in touch with our support staff who can provide you with instructions on how to access it and upgrade.
We released FrameFlow v2019.5 today and it is now available in our portal for all licensed customers. This release is largely a maintenance release that delivers fixes for a number of issues that were recently reported.
You can download the licensed setup from your account. If you are in the evaluation phase, you can download our evaluation version again to upgrade. Either way, all of your settings and configuration will be preserved.
FrameFlow v2019.4 was released today and is available in our portal for all licensed customers. Some of the highlights include improved monitoring for Office 365 status, updated email templates with better compatibility for some versions of Outlook and a new option to control how many failures in a row it takes before an alert will change its status.
Log into your account now to download and upgrade. If you are using our 30-day evaluation version, then download and install the eval version again. Either way, our setup program will do the upgrade while preserving all of your settings.
FrameFlow includes an event monitor that helps you to keep track of the status of the Office 365 services that your organization uses. We're currently seeing sporadic issues where some incidents published by Microsoft are not being made available to our event monitor through the APIs that Microsoft provided us with. We're investigating and looking into various workarounds.
We released a beta version of FrameFlow v2019.4 today. This new version adds improved UI performance, better compatibility for email templates, new date formatting options and a new option to control how many alerts it takes before an alert switches from success status to another status. Licensed customers can get the beta release by logging into their account on our site.
Most, if not all, applications and business processes are based on multiple components or units, each of which plays an important role in the overall operation of the process. So how do you judge the overall health of the system as a whole? FrameFlow's new Business Process event monitor lets you do exactly that.
Have you tried FrameFlow's integrated support for maintenance windows? Maintenance windows let you define regular periods of time when systems will be down for planned maintenance so you don't get unnecessary alerts about them. FrameFlow has full support for both recurring and one-time maintenance windows. Take a look at our two-minute video that explains how they work.
Python is becoming more and more popular as a scripting language for sysadmins. FrameFlow v2019.3 will add a new Python-based event monitor. Just like our PowerShell event monitor, this new event monitor will let you integrate your Python scripts directly with FrameFlow's monitoring and alerting engines.
FrameFlow v2019.3 is currently in the testing phase. If you are excited to try our new Python event monitor for yourself, contact us and we'll get you access to pre-release build that you can try for free.
VMware 6.7 disables TLS 1.0 and 1.1 by default. As a result if your are using one of FrameFlow's "legacy" event monitors for VMware you may see connection errors when trying to monitor VMware 6.7 hosts. To work around this we suggest that you switch to using our set of newer VMware monitors. They support v6.7 and offer improved features and functionality. If you prefer to stay with the legacy versions and need to monitor VMware 6.7, contact us for a patch that you can apply to your FrameFlow 2019.2 installation.
Update: The patch is now included in latest v2019.2 release. Log into our portal to download and upgrade.
We updated the v2019.2 release today to include a few fixes and updates. In particular, we fixed an issue that could affect multi-site communications. We also fixed a problem with system health monitoring using SNMPv2c. Lastly we added new options to control what is displayed on "List of Alerts" dashboard panels. Log into your account now to get build 4553.
Windows servers form the backbone IT infrastructure for many business operations, but are often taken for granted when everything is humming along...
The term “smart building” is currently buzzing in commercial real estate circles around the world. Thanks to the exponential growth of the Industrial Internet of Things (IIoT), many new buildings are incorporating network-enabled building management systems...
We fully understand the importance monitoring all the various IT systems that are critical to your business operations including: servers, routers, switches, HVAC systems, temperature sensors, back-up power supplies and virtually any type of device with an IP address.
We continually strive to offer a robust and versatile server and IT systems monitoring solution for a variety of enterprise customers, we’ve noticed that there are several common issues, some of which are interrelated, detected by our software across the board. Here’s a rundown on the top five:
FrameFlow is highly customizable and offers a wide variety of monitoring options. We’ve designed it that way on purpose to give you the flexibility to build out your monitoring configuration in a way that best suits your work environment, practices and policies.
Your servers, switches and routers are the core of your operations so of course it’s important to ensure that everything is running smoothly and to get early warning about potential problems. With this set of five best practices you can optimize your server monitoring configuration.