Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
The v.86 release will be rolled out through the second week of March. The changes you will see were designed to improve our platform’s ease-of-use and put more helpful data right at your fingertips.
Network Flow Improvements
We have added another round of improvements to our network traffic flow monitoring. This release debuts network flow groups, which display the aggregate of network flow data from each device assigned to a group. This is a fundamental improvement to the way we display your network flow data because it permits a traffic view (total bandwidth/flows) of all interfaces, which is generally more pertinent than the flows from a single device.
Why you care: consider each of your office locations. Every location may contain multiple routers and switches. The individual traffic for each of those devices is likely not nearly as important as the overall traffic flow for the office. Grouping the traffic of each device into a single aggregate flow will provide insight into the latter.
Alert Threshold History When adding, editing, or removing an alert threshold, you will have the option to add a note describing the purpose/reason for the change. These notes are stored at the datapoint-level and displayed in a history log within the Manage Alert Thresholds dialog. This is a powerful new feature that will contextualize your alert thresholds, which can explain why a threshold was set at a certain value; who last edited the threshold; and what historical changes have been made to a threshold, which can facilitate issues identification and remediation.
Why you care: knowing the full history of when and why your alert thresholds were established is critical for determining future action. For instance, consider the following scenario: “We have excessive CPU usage on a device and we are not alerting on it because of an exceptionally high alert threshold. With a threshold history, I can go back and see that the threshold was intentionally changed due to a recent JIRA ticket. Now that I have this context, I do not need to worry about the lack of triggered alerts.”
Raw Data Tab We made two major improvements to the Raw Data Tab:
Why you care: Using these improvements in conjunction with one another enables a quicker time to resolution when troubleshooting unexpected DataSources information.
We’ve added the following functionalities to v1 of our REST API: