Search the Community

Showing results for tags 'process'.

  • 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 3 results

  1. I have been using a Powershell script for a while now that used Batch Script (to not use as much collector resources as my company has TONS of App Pools per box) This links Win32_PerfRawData_PerfProc_Process with Win32_Process using the process ID for discovery. Instead of having an ugly instance name (W3WP#1,W3WP#2 etc) it now will display the AppPool name from the command line. We recycle AppPools nightly. This will run discovery every hour as it stands although, the collection uses instance ID ,matching the Command line so no holes in the data LM Exchange ID: 2WHYY4
  2. Please add an option to disable the "reply commands" footer section in notification emails. We want our users to follow our organisational process and procedure. You may reply to this alert with these commands:- ACK (comment) - acknowledge alert- NEXT - escalate to next contact- SDT X - schedule downtime for this alert on this host for X hours.- SDT datasource X - SDT for all instances of the datasource on this host for X hours- SDT host X - SDT for entire host for X hours
  3. I wrote this DataSource for a customer with a specific requirement, namely, they have a particular application that should spawn and maintain a specific number of processes on Windows machines. Operation: The DataSource finds all processes on the Windows machine and groups and counts based on name - e.g. if there are processes powershell, powershell#1, powershell#2, then the powershell instance will be added and will show a count of 3. Out of the box this DataSource will create instances for *all* processes as reported from the Win32_PerfRawData_PerfProc_Process WMI class, except the