Infrastructure Monitoring and Observability Platform

My primary responsibility is LogicMonitor administration, including network-device onboarding, monitoring configuration, alert tuning, and ITSM integration.

For new deployments, I recently onboarded 20+ network devices in the Australia South region. For smaller deployments, I use the Resource Wizard to add devices, assign collectors, configure SNMP credentials, and run discovery to validate communication and monitoring. For bulk deployments, I use NetScan to discover and onboard multiple devices efficiently.

I also manage alerting, thresholds, datasources, and monitoring customization based on operational requirements.

Additionally, I work on LogicMonitor integration with BMC Helix Operations using REST APIs, primarily GET and POST methods, to support automated alert and incident processing.

LogicMonitor has significantly improved our infrastructure observability, availability, and incident response by providing real-time dashboards, automated alerting, and proactive monitoring.

Our NOC team continuously monitors the environment and receives immediate notifications for critical infrastructure or service failures, enabling faster detection, escalation, and remediation. This has helped improve service availability from approximately 94–95% historically to nearly 99.9% currently.

LogicMonitor provides centralized visibility across Windows, Linux, network, and Cloud services, allowing us to monitor service health, performance metrics, resource utilization, and availability from a single platform.

The platform has also contributed to a significant improvement in MTTR by providing accurate diagnostic data and actionable alerts, enabling engineers to identify the affected component faster and reduce troubleshooting and resolution time.

Overall, LogicMonitor has strengthened our 24×7 monitoring capability, proactive incident detection, service availability, and operational efficiency.

LogicMonitor provides a highly automated and scalable monitoring framework. Once the required SNMP/API credentials are configured, devices can be onboarded using the IP address or hostname, followed by automated discovery of supported datasources, interfaces, and metrics.

At the Datasource level, monitoring logic, metrics, thresholds, and alert rules are predefined. Once the appropriate datasource is associated with a device, LogicMonitor automatically executes the required collection logic, retrieves metrics, and presents them through dashboards and time-series graphs, with alerts generated when defined thresholds are breached.

The automated alerting framework significantly improves operational response. For example, if CPU utilization exceeds a defined threshold such as 90%, LogicMonitor evaluates the associated alert rules and automatically routes the alert through the configured escalation path, such as the NOC notification channel, BMC Helix, Microsoft Teams, or email, without requiring manual intervention.

Another valuable capability is LM Logs, which provides detailed logging and troubleshooting information. During post-incident analysis, we can use these logs to trace device communication, collection activity, alert processing, and potential monitoring gaps, helping identify the root cause and determine whether any monitoring events were missed.

Overall, LogicMonitor provides automated discovery, centralized metric collection, intelligent alerting, visualization, and detailed troubleshooting capabilities within a single observability platform.

From an improvement perspective, one key requirement is extended raw-data retention and accessibility. Currently, raw metric data is available only for a relatively short period, which can limit detailed historical analysis during long-term troubleshooting or capacity planning. Providing an option to export or retrieve extended raw data through CSV, Excel, or APIs would improve historical analysis and reporting capabilities.

For AI, governance, and security, enhanced capabilities for FedRAMP environments would be valuable, particularly around security analytics, compliance monitoring, anomaly detection, and automated governance controls for regulated infrastructure.

There is also an opportunity to further enhance LogicMonitor's AI-driven troubleshooting and RCA capabilities. While the existing outage-analysis functionality is useful for automatically collecting relevant monitoring data during incidents, deeper correlation across metrics, alerts, logs, and events could provide more automated root-cause insights.

Another operational challenge is maintaining complete observability across hybrid infrastructure. In some scenarios, collector-side issues can result in data-collection gaps or "No Data" conditions, which may reduce monitoring visibility and potentially delay detection. Enhanced collector health monitoring, data-collection validation, and proactive detection of collection failures would help minimize these monitoring gaps.

Overall, LogicMonitor provides a strong observability platform, with the main opportunities focused on extended data retention, FedRAMP security/governance, AI-driven RCA, and improved collector/data-collection reliability.

I have been using LogicMonitor for the last six years.

LogicMonitor is a 100 percent stable application.

I would rate LogicMonitor a nine out of ten for scalability.

I would rate customer support a seven out of ten.

For customer support, I rate it a seven out of ten since we often do not get immediate responses from support or live chat agents, and most communication happens through email, which is time-consuming.

Previously, we used the HP monitoring tools but switched to LogicMonitor due to its on-premises solution being costly in licensing and support.

Complex.

Yes, LogicMonitor has delivered ROI by reducing manual monitoring effort, enabling faster incident detection and resolution, and improving infrastructure availability. Automated alerting and integrations with BMC Helix and Microsoft Teams streamline incident escalation, reduce operational overhead, and help improve service availability from approximately 94–95% to nearly 99.9%.

We directly connect to LogicMonitor, purchasing it through our third-party vendor.

Regarding pricing, setup cost, and licensing, it is more about management decisions, but I find the pricing for collector and device count fair enough for the SaaS-based model.

Our team consulted with network architect team and found that LogicMonitor was more useful than other monitoring solutions, so we chose it.

I would rate LogicMonitor a nine out of ten since it is the most reliable tool nowadays. Being SaaS-based eliminates the need to worry about infrastructure, servers, and databases, making it very useful for monitoring.

I choose a nine out of ten for LogicMonitor because it is SaaS-based, and we do not need to worry about the database or the server going down, with automatic updates for the collector, which ensures it works well for monitoring.

We have not utilized the Dynamic Service Insights feature for real-time visibility.

We recently applied for the trial license of Edwin AI in our lab to explore its functionality, but we are not yet fully using it in production.

We are not yet using the autonomous learning feature of Edwin AI.

I advise organizations with vast enterprise-level infrastructure to consider LogicMonitor, while smaller setups might look for less costly options. My overall product rating for LogicMonitor is nine out of ten.