failover

4 Topics

Auto Balanced Collector Group vs Failover?
Hi, I'm wondering if there are pros and cons vs setting up multiple collectors as an ABCG vs stand-alone collectors with failover. If we have two collectors in the same location, monitoring the same servers, I'd use an ABCG. However... Let's say I have servers in Los Angeles and New York, and I have one collector in each location. If I set them up as an ABCG, would LM be smart enough to have the LA machines be monitored by the LA Collector and NY by NY, or does it just assign them randomly? I'm not sure if it has each collector ping each device to see which one has a better connection or anything like that. I currently have the LA collector manually assigned to the LA machines. I then have the LA Collector fail over to the NY Collector in the event of a problem. Each location CAN see the other, but I don't want LM monitoring things across the connection when each location has it's own collector on-site. Thoughts?
Solved
Kelemvor
17 days ago Place Product Discussions
41Views
0likes
4Comments
If a collector fails to a down collector, will it then fail to that collectors backup?
Hi, We have three collectors that can all see the same items. Normally we've had them setup where 1 and 2 fail to each other, and 3 fails to 1. However, if we ever lose two at a time, we'd be stuck. If I set them up so 1 -> 2, 2 -> 3, 3 -> 1, and we lose 1 and 2, what happens? The devices on 2 will fail to 3 just fine. What happens with the devices on 1? Do they try to fail to 2 and then realize that 2's down and then fail to 3? Or do they just go to 2 and then stop? Thanks
Kelemvor
3 months ago Place Product Discussions
29Views
0likes
3Comments
Windows_Cluster_Failover
R79DJL I'm not sure if this datasource was removed intentionally, but there was a datasource named "Windows_Cluster_Failover" that monitored for cluster failover events. We've been using this datasource, but we noticed that it triggered a false alarm last night which prompted me to go back and rebuild it. This datasource will monitor a Windows cluster for a failover event. If a failover is detected, it will be logged in the LogicMonitor's installation directory (Default is "c:/Program Files (x86)/LogicMonitor/bin/"). The datasource exits if certain calls fail altogether (to prevent false alerts) and there is a separate alert that will trigger if the datasource continuously fails to get data. So far this appears to be working more reliably, so I thought I'd share.
Brandon
7 years ago Place Archive
3Views
0likes
1Comment
Failover Collector confusion
LM Team, When you are on your primary collector and choose a failover collector and are deciding to check that box "Automatically failback when THIS collector becomes available again". The way that it is worded, THIS collector could mean the current collector you are configuring. Then again, the checkbox is underneath the failover collector you just selected and it is indented, so it's easy to convince yourself that it could be referring to the failover collector. I think it would be worth re-wording or at least offering a hover-hint (?) box to clarify that the failback will be occurring on the collector you are currently configuring. Looking back, I had checked this box differently depending on how I felt that day and which made most sense to me at the time. Some clairification would be good. Thanks!
DBA_Troy
8 years ago Place Archive
6Views
1like
2Comments