AWS Gateway Load Balancer monitoring functionality must be added.
Hi LM Ihadarequestfromoneofourclientstosetupmonitoringandalertingforthegatewayloadbalancers,butIcouldn'tfindanydocumentationonthat,andaccordingtoLMsupport,thefunctionalityisn'tcurrentlyavailable. I'dliketorequestyoutopleaseintegratethisfunctionalityassoonasyoucan. Please refer the awsGWLB's documentation below. https://aws.amazon.com/elasticloadbalancing/gateway-load-balancer/48Views10likes2CommentsAWS Health Event and AWS Service Health Eventsources require enhancements.
Hi Community/LM Folks, I am aware that I am not the only one who expecting significant improvements for these two event sources: AWS Health Event and AWS Service Health. 1 - AWS Health Events - Since this event source lacks the ability to filter events, we are unable to personalize or filter event logs for a specific issue or region. 2 - AWS Service Health - I've observed that this event source does not provide as much information as what is displayed on the RSS feed page. Nevertheless, we can filter the event, however there are not many options. I truly believe that these two event sources deserve huge upgrades, and the majority of LM users are wishing for the same. Thank You :)23Views1like0CommentsUse AWS Unified Cloudwatch Agent to replace Logic Monitor Collector in multiple AWS accounts
Is there any way to use the AWS Unified CloudWatch Agent and Cloudwatch Logs load EC2 metrics into LogicMonitor similar to what is pulled from theLogicMonitor collector? A little background. We currently use two LogicMonitor collectors to gather Windows metrics from AWS EC2 instances and physical and virtual servers in our on-prem datacenter. This has worked well for the 100 Windows servers and network devices we are monitoring. We are moving all of our on-prem Windows applications to AWS, which requires we change the way we use AWS. Take a look at AWS Control Tower for more details Instead of one AWS account and one VPC ( network ) , we are moving every application and environment ( PROD, UAT, DEV, STAGE ) into different AWS account. No shared networking, so VPC peering or using a TGW isn't an option. This will result in about 20 new AWS accounts and up to 100 by the end of the year. Each of these accounts will have 2 to 20 EC2 Windows instances for web/application along with one EC2 or RDS based Microsoft SQL Server instance. I have no desire to pay for EC2 Windows instances for every account ( possibly hundreds ) just to run the LogicMonitor collector. The most important Windows server monitoring features we rely on in LogicMonitor boil down to - server is down ( ping loss ) - low disk space - high CPU utilization - the ability to alert on Windows Event log entries - Windows service X is not running Then tack on monitoring of an EC2 and RDS Microsoft SQL Server performance data Does LogicMonitor have any recommendations or examples on this type of configuration? Thanks in advance, Kevin Foley11Views1like1Comment