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!
LogicMonitor v.164 is scheduled to roll out to customer portals from January 19 through January 31.
You can now integrate LogicMonitor with StackStorm and Terraform.
Integrating LogicMonitor with StackStorm allows you to automate complex IT workflows by using alerts to drive event-driven runbooks. Alerts from LogicMonitor can trigger simple or complex, multi-step workflows. For example, if you receive an alert that a resource’s memory is low, you could configure StackStorm to automatically run a script and delete the cache of the impacted resource and then create a note in your ticketing system. This integration can be used across both your on-premises and cloud infrastructure.
With LogicMonitor and Terraform, you can leverage infrastructure as code to ensure that any scaling, onboarding, and offboarding is done in a controlled and repeatable manner for your collectors, collector groups, devices, and device groups. Now, you can also sync your AWS cloud account through Terraform to better ensure full monitoring coverage whenever you make changes.
This new integration is verified by HashiCorp and supported by default by LogicMonitor, and you’ll notice increased performance as well as continued maintenance and updates. When you make changes to your environment using Terraform, LogicMonitor is kept in sync with the changes in the infrastructure it monitors. This ensures that services are deployed with the required monitoring, and the monitoring automatically adapts as systems or application environments are promoted from QA to staging to production.
This new functionality delivers service health status across your organization’s Microsoft 365 subscription for services such as Exchange, Teams, OneDrive, Sharepoint, etc. If you are experiencing problems with a cloud service, you can check the service health to determine whether this is a known issue with a resolution in progress before you call support or spend time troubleshooting. See Monitoring Microsoft 365 Services Health Status DataSources.
We are introducing Object Quota Limits for Resource Groups to encourage best practices for using the LogicMonitor platform. This feature provides users with a warning message if they cross thresholds set according to LogicMonitor best practices. This feature helps users identify problematic configurations, like high number of Resource Groups, and warns them before it starts impacting portal performance. At this point, this feature will not stop users from performing any action. See LogicMonitor Limits, Quotas, and Constraints.
New and updated LogicModules are available for you to import from the LogicMonitor Public Repository. This section lists the LogicModules that are new in this release, updated in this release, or will be removed in a future release. Changes related to the LogicModule feature will be listed under General Updates.
This table lists LogicModules that we are deprecating in this release. This means that these LogicModules will be removed in a future release. If available, a replacement LogicModule is listed.
For the list of LogicModules deprecated over the past five releases, see the support article Deprecated LogicModules.
In this section you will find announcements about upcoming beta features, updates about ongoing beta features, and information about the end-of-life of existing features.
LogicMonitor APM has been available in a limited release capacity for the past few months. We are now getting ready to expand access with the launch of our Lighthouse Program for users that want access to our APM capabilities. Along with early access, qualified customers and prospects will have the opportunity to influence the early direction of our product and provide feedback to enhance our APM offering.
If you are interested in participating in our Lighthouse Program, please fill out the Google form here.
The automatic update to MGD Collector 30.001 was scheduled to deploy on January 10, 2022.
However, due to the Log4Shell vulnerabilities, the new MGD Collector version will now be 30.002. This version addresses the Log4shell vulnerabilities. This version is scheduled to be automatically installed on January 20, 2022.
No action is required ahead of this date. You may upgrade to MGD Collector 30.002 before January 20 or you may wait for the automatic upgrade to occur. For more information, see MGD Release Update.
In This Article