Kirby_Narine
LM ChampionJoined 6 years ago
User Profile
LM ChampionUser Widgets
Contributions
Re: Anyone doing PostFix monitoring?
Hi Derek! So we do have a method and some modules built out where the LogicMonitor collector acts as a desktop email client. It sends outgoing messages using your SMTP service and measures basic metrics including RTT and transit time. Take a look here: https://www.logicmonitor.com/support/monitoring/applications-databases/email-service-monitoring130Views3likes0CommentsRe: Entering enable mode using JSch
It does seem like shell mode would be your best bet. That being said you could introduce a false sort of delay if you really wanted to use exec. https://epaul.github.io/jsch-documentation/simple.javadoc/com/jcraft/jsch/ChannelExec.html Maybe something like: Session session = jsch.getSession(user, host, 22); session.setPassword(password); session.setConfig("StrictHostKeyChecking", "no"); session.connect(); // command1 ChannelExec channel1 = (ChannelExec) session.openChannel("exec"); channel1.setCommand("enable"); channel1.connect(); channel1.disconnect(); Thread.sleep(1000); // Delay for 1 second // command2 ChannelExec channel2 = (ChannelExec) session.openChannel("exec"); channel2.setCommand("your_next_command"); channel2.connect(); channel2.disconnect(); session.disconnect(); There could be issues depending on how certain devices response, or if connection session up/down takes an extended amount of time. Using shell would be easier for sure, and more consistent across devices, but hope this helps!49Views6likes0CommentsRe: Collectors Capacity review
Yes, you should leverage the resource metrics trends report. Report creation: https://www.logicmonitor.com/support/reports/creating-managing-reports/what-are-reports Resource metric trends report info: https://www.logicmonitor.com/support/reports/report-types/device-metric-trends-report Use the same datasources you want to pull from in the report. If you have your collectors dynamically grouped, (maybe already in “Devices by Type/Collectors”), you can target that group.35Views1like0CommentsRe: Collectors Capacity review
“Collector Thread: Time” or “Collector Thread: CPU” in your screenshot are good ones as well. If you see any specific instance spiking (let’s say, batchscript), it means the collector needs more threads put towards that collection method. The threads can be raised in the collector config (colector.batchscript.threadpool is a very common one to raise), but should only be done if the CPU and Memory of the host are not reaching their peak. I’d recommend reaching out to support before making any collector config changes for general guidance. Collector Data Collecting Tasks (also seen under that collector datasource list in your screenshot) is also very useful. If you see a queue depth (on graph), it might mean the collector is having trouble keeping up with the load.111Views1like0CommentsRe: Groovy script failing for alinux server
If it’s working via datasource test, but not in debug (!groovy), can you make sure the hostprops are being populated correctly via debug? Consider manually entering them in the script as you run it via !groovy: host = "HOSTNAME" user = "SSHUSERHERE" pass = "SSHPASSHERE" port = hostProps.get("ssh.port")?.toInteger() ?: 22 cert = hostProps.get("ssh.cert") ?: '~/.ssh/id_rsa' Note: For hostname, make sure to use the same value under INFO tab of device for system.hostname. If still failing, definitely create a support ticket, as it can be tested more in-depth from LM support side.129Views2likes0CommentsRe: Introduce Yourself!
Hey everyone! Good to meet you all. I’m a Sr. Premier Support Engineer at LM. I’ve been with LM for over 3 years and have established wide and deep product knowledge. Looking forward to contributing to the community. In my free time, I train Muay Thai. I also enjoy seeking out new restaurants around my city of Austin. I enjoy traveling and take a trip or 2 each year to a different country. Cheers!1View3likes0Comments