Mike Moniz

  • Content Count

  • Joined

  • Last visited

  • Days Won


Community Reputation

40 Excellent


About Mike Moniz

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Try using the /device/groups/{gid}/properties/{name}/ endpoint.
  2. To provide some more generic information when you see "No Data" on the resource page... The first thing I suggest you do is go to the Raw tab and use Poll Now. This actually can provide a lot of useful troubleshooting information. It will show what it attempted and the output or results. If you post a screenshot of it, we might be able to help out. You might want to block/blur out any sensitive information though.
  3. When you create a new Datasource you will have the option to check a "multi-instance" box. You can't easily change it after creating the DataSource as it's greyed out in the UI. You can either export and edit the XML directly or best to just create a new DataSource with that option enabled and copy over the settings/script. Once you enable that option you can optionally choose to use an Active Discovery script or not. If you disable this option, then you can use "add monitoring instance" on the device (resource tab) to manually add instances. If you enable Active Discovery, you can automate the addition of customer instances, assuming you have a source list you can query. Note that using BatchScript is generally more efficient than using plain Script when it can be used. Side note. It sounds like you might be an MSP? Keep in mind that DataSources will always run on the collector systems. So you don't want to collect data for one customer from another customer's collector. Best to do something like that from a collector you directly own. Unless by "customer" you mean your customer's customer.
  4. Use the Reports section? ;) It does seem LM is not that strong in the reporting department. Something like that you may want to either write a script to get the details from the LM API or put in a feature request for a more detailed report. In our case, all our alerts go to our ticketing system so we tend to do reporting from that instead.
  5. Mike Moniz


    I'm not familiar with Kibana but the Collector logs are stored by default at c:\Program Files (x86)\LogicMonitor\Agent\logs\ but these log files are meant for troubleshooting collector problems. They are not meant (and may not contain) any performance/alerting data from your monitored devices. LogicMonitor is a cloud PaaS monitoring solution so all the monitoring data is kept and stored within the LogicMonitor portal on the cloud, not in your on-prem devices. If you need to independently process or visualize performance data that LogicMonitor is collecting, you likely need to export it via one of LogicMonitor's built in reports or use the REST API.
  6. I wasn't aware (or wasn't at the time) of that suggested best practice back when we started using LM 4+ years ago, but also not sure how well that works over the long term if you change enough stuff, I worry that this end up forking any non-trivial changes DataSources from the repo so you can miss any bug fixes or improvements. Also you can end up with stuff like multiple copies of the same DataSource with slight changes or per-customer (for MSPs), although you can plan ahead a bit to mitigate that. The category assignment is easy and minimal change that is easy to verify and mark as audited, imho. But then again we spend a lot of time auditing changes too, the new LM Exchange should improve that. The new LM Exchange seems to be geared towards people modifying the original DataSource anyway since it seems to separate items like AppliesTo and thresholds. The whole GIT pull thing is very interesting although I expect that wouldn't scale well.
  7. Would you say that that suggestion apply to EventSources (this thread), DataSources and any other LogicModules?
  8. I don't think you can re-enable something at a lower level. What I do is modify the AppliesTo to the EventSource so it only applies to devices with a particular category. You will see some built in DataSources work this way too. So for Windows System Event Log for example you can change "isWindows()" to something like 'isWindows() && hasCategory("SysEventLogs")' then assign that Category manually to groups/resources you do want to applied to. If there are particular classes of resources that you always want this applies to, you can also custom write your own PropertySource to assign that category for you.
  9. I suggest you start a new thread/topic. You can also try taking one of the existing linux ssh DataSources and customizing the Groovy code to do the work you need.
  10. You would add the ssh.user and ssh.pass as properties to the device or group that contains the device. You can see the link for details but basically choose the device/group and then the Manage button, on the bottom will be a section for Properties. https://www.logicmonitor.com/support/getting-started/advanced-logicmonitor-setup/defining-authentication-credentials
  11. Well the great thing about LogicMonitor is you can see exactly how it works by looking at the DataSource. Here it's using some Groovy code you can review but the technical notes say: So sounds like it's worth making sure the permissions are setup correctly.I don't really know Citrix myself nor it's API but if you either use the Poll Now button on the raw data tab, or use the TEST buttons on the DataSource, it might provide additional details.
  12. Another suggestion for the services check, although this does deviate from the existing WinServices- check is instead of doing 0=Not OK and 1=OK, is to set 0=OK and 1=Not OK. Several other LM Datasources generally work this way in that the larger the number the more urgent the problem so you can do thresholds like > 0 1 2. In this case it that doesn't matter since it's binary option, but it also helps with widgets like table color bars where < does not work very well or gauge widgets and others that also seem to assume this.
  13. I've had problems attempting to do that in the past outside of LM but haven't really resolved it (kinda gave up at the time). I think you need to query the value twice over a set period and also take into account the number of logical cores in the system has. But even doing that I intermittently was getting weird results like 72025954.98% cpu. You'll see some various discussions on replicating task manager per-process cpu % via wmi on google. It would be great if there was a good solution to this though.
  14. As a thought, if you add a new datapoint "ProcessId" which outputs the process id of the Windows Service (which is a number), you can then use the delta threshold to cause an alert if the service restarts between checks. Just as an option if it's ever needed at the instance level.
  15. Ha, I just realized I have used it before to create PropertySources based on https://communities.logicmonitor.com/topic/1137-use-ilps-for-applies-to/. How quickly I forget :P