Patrick_Rouse
Product ManagerJoined 4 years ago
User Profile
Product Manager
User Widgets
Contributions
Linux Collectors: Expanded OS Support
We recently expanded our list of supported Linux distributions by adding Oracle, Chainguard, and Rocky Linux. Also, at the end of June we'll no longer support CentOS, as this distribution is end of life and no longer maintained. https://www.logicmonitor.com/support/adding-collector#h-collector-server-requirements Excerpt support list for Collector OS: Amazon Linux CentOS Linux (LogicMonitor End of Support: July 1, 2026) Chainguard Debian GNU/Linux Oracle Linux Server Red Hat Enterprise Linux (RHEL) Rocky Linux Ubuntu With this, over 93% of all Linux collectors used by our customers are using a LogicMonitor-supported Linux distribution. However, a little south of 5% of Linux collectors are still running CentOS that reached end-of-life four years ago, so if this applies to please make plans to migrate to a supported Linux distro to mitigate risk of monitoring disruption and to maintain a strong security posture.Re: Centralizing Vendor Status Pages in LogicMonitor - How are you doing it?
Hi, eortiz. Since it sounds like SaaS app monitoring is important to you, I wonder to what extent you are aware of LogicMonitor’s SaaS app monitoring capabilities with last week’s announcement that we acquired Catchpoint, the industry leader for Internet Performance Monitoring. So, if you need, it’s possible to monitor the experience of these applications from where it matters via more 3000 vantage points strategically placed across the globe. Furthermore, you can get alerted if the performance is not acceptable for users in the regions you care about and visually see where in the Internet Stack the problem exists. This is an interactive, searchable map of where you can test from: https://www.catchpoint.com/global-observability-network How we visualize where problems exist in the Internet Stack: https://www.catchpoint.com/internet-stack-map https://www.catchpoint.com/workforce-experience/saas-application-monitoring For fun, and with assistance from some of mt new teammates, I used Catchpoint Webhooks to send some of the test results to my LM Envision portal to start thinking about how we might leverage this information in-product.Real-Time Insight: Webhook Events as Logs Now Available in LogicMonitor
As highlighted in our recent v228 platform release notes, we’re excited to announce that Webhook Events as Logs is now generally available. This enhancement makes it easier than ever to bring external alerts and events directly into LogicMonitor—no Collector required. If you’re using a platform like Cisco Meraki, Rubrik Security Cloud, or CommScope Ruckus One, you can now configure those systems to send webhook alerts straight to your LogicMonitor portal. Why It Matters Traditional log collection methods (like syslog or scripted collection) rely on a Collector to process messages. With Webhook Events as Logs, external platforms securely deliver event data via HTTPS directly to LM Logs. This means: Faster insight: Events are ingested in real time, not on a polling interval. Simpler setup: No Collector configuration or maintenance needed. Flexible processing: Use LogSources to filter, enrich, and map webhook messages to LogicMonitor resources, and extract key fields for use in alert rules, messages, or queries. Getting Started To use Webhook Events as Logs, you’ll need: LM Logs enabled in your LogicMonitor account A platform that supports Bearer Token Authorization (either natively in its UI or via custom header configuration) Once configured, external systems can send events directly into LM Logs—triggered by real-world actions rather than scheduled polling. Real-World Examples Here are just a few examples of events that can now flow directly into LogicMonitor via webhooks: A camera detects motion A panic or lockdown button is pressed (e.g., Alyssa’s Law compliance) A wireless client joins or disconnects from a network A device becomes unreachable A backup job fails A virtual machine shuts down A configuration change occurs (e.g., in a Cisco Meraki network) Any webhook-capable system that can send a Bearer-authenticated POST request can now send event data to LogicMonitor. Verified Integrations We’ve validated this capability with: Cisco Meraki Rubrik Security Cloud CommScope Ruckus One …but the feature is built to work with any platform that supports webhook notifications. Learn More For setup details and examples, check out: Product Documentation for Webhook Events as Logs: https://www.logicmonitor.com/support/webhook-events-as-logs LogicMonitor Webhook Integration for Cisco Meraki: https://developer.cisco.com/meraki/webhooks/logicmonitor-custom/
