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.77 release brings a few more much anticipated features, and we’re just warming up. Check out the new Internal Service Checks (collector based services) and Alert Forecasting report, both valuable ways to keep you one step ahead of potential issues. There are a lot of other good nuggets in this one, so be sure to give the details a scan.
Sunsetting the Old UIWe mention this almost every release, because we know our entire purpose is to help you avoid surprises. The old Dashboard page is going to linger for one more release, but will be formally removed with v.78. The Devices page will follow, be sure to check out some tips on why the new view is more helpful. Finally, use the feedback button – we want this transition to be positive for all, so let us know how we can help.
Internal service checks, or collector based checks, bring you all of the functionality of our standard Service checks direct from your collector. It’s great to know if the rest of the world can reach your website, but you likely only really care if your end users can reach your cloud services or internal applications. Internal service checks allow you to run these checks directly from your data centers, or wherever you have a collector installed.
How does this differ from the HTTP Web Page checks you’re currently running, you ask? Great question. The underlying functionality is the same, but usability and configuration is significantly easier. You can add a Ping or Website check from the Services page just by clicking Add, and selecting Internal Website Check or Internal Ping Check.
Configuration is exactly the same as standard Services checks, with the exception of needing to add a collector (version 22.050 or higher):
You can run a check from as many, or as few, collectors as you desire, and can configure alerting based on individual or overall performance.
Service Defaults can also be used for your checkpoint locations and alert triggering, just add your primary service collectors in the Services Defaults window:We recommend setting up service checks for all of your internal applications and creating a published dashboard so you can proactively let your end users know if the service is having an issue. We have some other features in the works, but use the feedback button to let us know what would be most useful to you.
We introduced Alert Forecasting as a function of the table widget. This is great for troublesome equipment, devices where the table widget view is also necessary, or situations where less than 100 datapoints suffices. The Alert Forecasting Report allows you to extend that functionality, with a higher limit on datapoints and the ability to set up a few monthly reports as a routine checkin opposed to the daily widget view.
To give the report a try, select Alert Forecast Report from the Reports | Add | Add Reports menu. As with the widget, you can configure the training data (which past performance to base the forecast on), Minimum Confidence, and datapoints to include. You can also configure which columns, order, and can sort in the HTML view. See more details here.
A historical view of Scheduled Downtime (SDT) is now available at the level the SDT was set. For example, a SDT set at group “Servers” will apply to all members of the servers group at the time it was run, and will be visible in the SDT tab History section for Servers.
We’ve streamlined collector management a bit. You can now select all collectors, or select all viewable collectors, from the toolbar:
Once selected, you can use the actions dropdown to set scheduled down time, schedule updates, or move collectors:
In This Article
