eandrewes
Joined 3 years ago
User Profile
User Widgets
Contributions
Transparency of TimeTicks
Hi all, Is there a way of ingesting data through a DS that can accommodate the northbound data tick? Assuming we’re talking to an element manager and the EMS has it’s own 9:00/9:05/9:10/etc timestamps, is there a DS template that will allow LM to use that existing time tick in it’s DS rather than applying the LM ‘Poll time’? Reason for the question: We may need to recover from a connection interuption/delay between EMS and LM and cant simply discard intervening data ticks Regards, ed30Views1like2CommentsGraphical Dashboard
Hi all, does anyone have an example of a dashboard page that shows the structure of a resource? Is it possible within LM to create a page with a chassis of a Device, with the LM discovered resources (Cards/CPU/Memory/Fans etc) displayed as selectable entities (as they would be in the resource tree, or as a NOC widget)? Regards edRe: Question: Autobalanced Collectors and Trap/Syslog reception
On 7/16/2022 at 10:03 AM, Stuart Weenig said: Agreed. This is how syslog works with LM Logs. It can be done, but LM is pretty anti-traps, so they might not do it for traps any time soon (even though they likely could). Have you thought about samplicator? It could be a single point that your infrastructure can send to, and you can configure it to forward to one/all/specific collectors. That said, I'll echo LM: what are you getting from traps that you aren't getting from polling? Seriously. If the answer is non-zero, in most cases, you can identify the values bound into the traps and poll them, eliminating the need for a trap. Not to mention EventSources don't have a concept of one trap to open the alert and a corresponding alert to close the trap. Thanks Michael. Unfortunatly the issue is that we've hit a hard limit on how much we can poll off the end devices. We're polling Huawei optical kit that aggregate's residential connections and in addition to interface stats we are attempting to use the equipment supported dying gasp traps as these represent a customer impacting issue. However attempting the poll the 800000+ dying gasp state per device has proven completely unable to scale (both in collector tasks as well as load introduced on the managed element).13Views0likes0CommentsQuestion: Autobalanced Collectors and Trap/Syslog reception
Hi everyone, can someone please advise the correct architecture/approach that should be used in the event that LogicMonitor collectors are configured in an AutoBalancedCollectorGroup, and are expected to receive push (SNMP Traps/syslogs) information from managed NEs in addition to SNMP polling. If the NEs are configured to send traps to all collectors (for redundancy) how is de-duplication of traps managed if the same trap appears on multiple collectors? Does each collector handle an instance of the trap or does trap reception need to be excluded from auto balance by setting a preferred collector for traps, or is LM able to deduplicate the traps itself?56Views1like5Comments