Mike Moniz

  • Posts

  • Joined

  • Last visited

  • Days Won



71 Excellent


About Mike Moniz

  • Rank

Recent Profile Visitors

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

  1. Actually we use that DataSource too and I see the same issue. So I looked at the code and it's just calling the getSharePointSiteUsageDetail (7 day) GraphAPI and retrieving some raw CSV data. The report data looks screwed up to me though. Like all the Site IDs are "00000000-0000-0000-0000-000000000000" and the URLs, Owner Display Name and Owner Principal Name are long HEX codes. I don't have admin to O365 to check directly but I'm wondering if something is broken in the report and how long it's been like that.
  2. As a general troubleshooting test I suggest you look at the DataSource (Office365_Reports_SharepointOnlineSiteUsage) in Settings > LogicModules > DataSources, then use the Test Active Discovery button. Check what it shows for instances there and if the names look correct. If it shows correctly there then I would just delete all the instances then get Active Discovery to rebuild it. Note that this will cause you to lose any historical data for sharepoint site usage, but since it sounds like it never worked until just now, so I assume that is ok to do. If the test still shows GUIDs then you might need to dig into the powershell code or work with LM support if it's not by design.
  3. I'm not sure about this exact issue but looking at the Microsoft_SQLServer_Troubleshooter DataSource code, LM checks for sysadmin access by using the below SQL statement and checking if userstatus = 1 (basically). Perhaps logicmonitor.svc is part of a group that is sysadmin? SELECT IS_SRVROLEMEMBER('sysadmin', SYSTEM_USER) as userstatus
  4. Since you have collectors per site, you can just run a Resource Inventory Report and include the "system.collectordesc" and/or "system.collectorid" properties. Then sort/group by the collector.
  5. One the server itself it's at c:\Program Files\LogicMonitor\Agent\logs\ (by default) but you can also grab the logs from the portal.
  6. Interesting. And it's checks for the collector itself? I would check the EventLog for crashes or other messages, along with the Collector log files. I would also check for any antivirus or security software that might be causing problems. Make sure that nothing it stopping PowerShell from running or killing it since the collector might use PowerShell for some wmi queries. Can you query Uptime and CPU on the server directly using WBEMTEST or get-wmiobject?
  7. Can you provide some example code? They fact that your getting html response instead of JSON likely means something more fundamental is an issue then the specific EventSource API details. You might want to use some of the REST v1 examples on the support pages, to make sure any API calls work, then you can convert them to v2 convention. Based on the v2 docs, it does look like import via XML is the documented method to create EventSources. You might need to generate the XML file (perhaps by having an XML template that the script modifies) to provide into the API call.
  8. As far as I know parent tokens are still not available. One workaround is to use dynamic groups. Under each Customer you can create a dynamic group for each site (something like system.staticgroups =~ "^Customer A/SiteB/") then point the widget there.
  9. Also feel free to also reach out to me about this. I've brought up this issue several times over the past 4 years including several tickets: tickets 76322, 88632, 108961, FEED-2277.
  10. Unfortunately Datapoints must be valid numbers and strings can't be use. The two periods makes it an invalid number. Generally you can store version data as property data (strings allowed) or you can perhaps change the DataSource to crop the version or drop the 2nd period, for example 4.4 or 4.45 .
  11. IPs also need to be unique per collector/ABCG also and I don't think one CSV file itself can specify which collector to use (I don't use CSV much). Might need to do one CSV import per customer so you can chose the correct collectors. For an MSPs I suggest investing in writing onboarding scripts. But I definitionally agree on the error messages and more error checking. CSV importing can allow items to be imported that have problems that GUI would normally prevent like newlines and ending spaces in names.
  12. MSPs have collectors installed on various customer's sites. Collectors also act as a dependency so if a site goes down and takes the collectors down too, you don't get all the devices at that site to send tons of alert notifications. Remote Access via collector proxy might help gain access if site-to-site connection is down.
  13. Not directly (can't upload a MIB to LogicMonitor) but you can create custom SNMP DataSources and using the MIB file as reference. MIB files can be hard to read but there are a few programs and online MIB Viewers that would make it much easier to read. Also LM has a blog post on creating SNMP DataSources at https://www.logicmonitor.com/blog/5-tips-for-creating-snmp-datasources-in-logicmonitor which also includes a link to a recorded training session on creating SNMP DataSources.
  14. As a kinda messy workaround, you can clone the DataSource you want to use so you have two version: 1. Informational version covering all instances with no alert thresholds which you can use for graphs and performance data. 2. Alerting version that uses Auto Discovery filtering to ONLY contains instances based on the naming you want to alert on and has global threshold values. This does mean that you are performing some checks multiple times but would be more automatic than manually setting thresholds per interface. Still like the idea of having an instance option in Alert Rules though.
  15. Does this work between collectors in ABCG? Like if a device balances to another collector or if there is a failover/failback?