Search the Community

Showing results for tags 'WIndows'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • From LogicMonitor
    • Product Announcements
    • LM Staff Contributions
    • Community Events
  • LogicMonitor Product Discussion
    • Feature Requests
    • LM Exchange
    • Ask the Community

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 32 results

  1. So this is less of an ask the community and more of a show the community. Ive written some Ruby code that makes it much much easier to use the LogicMonitor API. It does all the signing for you so you can just focus on your API calls and worry less about the secure signing. https://gist.github.com/ITJamie/4937de9139c682c02c34ff2d17051d58 It uses the following rest-client library https://github.com/rest-client/rest-client and injects the authentication method into the rest-client library. Ive included some examples of usage in my gist. Let me know if your having difficulty and i will test and patch as needed For an example of how easy this makes using the Rest API temp_url = @URL + '/service/services' response = RestClient.get(temp_url) # Printing API server response puts "\nServer response: #{response}"
  2. Useful for inventory purposes. Displays the total number of CPU's, cores, and logical processors on Windows machines. Also provides a description of each CPU. Example below. auto.cpu.cores 4 auto.cpu.logicalcount 4 auto.cpu.total 4 auto.cpu0.description Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz auto.cpu1.description Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz auto.cpu2.description Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz auto.cpu3.description Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz MRF3XG
  3. Created this little data source for collecting the usage of file system quotas on Windows. JFR7TJ The data source is based on File System Resource Manager in Windows 2012R2, it havent been tested on any other version of Windows yet.
  4. During the initial and periodic device auto-discovery tasks, there should be far more information stored about each device. This information should be easily accessible from the device information page and populated with data such as "Installed Programs", "Installed Features", "Running Services", "Domain Role", etc. This information could then be used to auto-group devices. For example, I should be able to create an auto-discover rule that automatically grabs all Domain Controllers based on the system.installedservices and system.installedfeatures categories. There is no reason I should have to manually move this server that is clearly a Domain Controller into my group labeled "Domain Controllers". This approach would allow administrators to "set it and forget it" instead of having to be hands-on every time a new device is added or discovered. This data can be easily populated from standard WMI classes: system.installedservices = win32_services.displayname system.serverfeatures = win32_serverfeature.Name Please help me organize my devices automatically. We have too many machines in too many environments to manually sort them all into groups.
  5. I want to know how I can monitor multiple windows processes for a device group.
  6. The data sources below will gather the service packs from Windows Servers and alert if the system is not on the latest service pack. As new service packs are released, you will need to update the alerting level. Since you do this manually, it gives you the opportunity on when to start alerting, or you can set it to the latest to create a list of servers in your organization that need upgrading. 2003 - CLDJYT 2008 - TYAYTD 2008 R2 - 97DY2F 2012 - HMKPFL 2012 R2 - W2HKGR 2016 - YZWNTM
  7. Hi, As much as i love the graphs and visuals that LM produces for all sorts of metrics, unfortunately a big part of our monitoring is keeping an eye on Windows Event Logs, which i have to say LM is not that good at. Adding exceptions is a pain (i now have so many i often delete them by accident when adding new ones). I have been told this is in the pipeline for the new UI several times but it has not been mentioned as yet. My first line guys check our gfi & LM dashboard every morning and i hear time again that they prefer the gfi one for looking at Event log messages. I have even caught them loading gfi on to servers that already have LM on them (costing us twice the cost). Is there anything in the pipeline for this? I know it's not a priority for you guys, but i think for a lot of customers it would be.