Process

3 Topics

Display IIS App Pool Process Memory and CPU use with App Pool name as Instance ID
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 linksWin32_PerfRawData_PerfProc_Process withWin32_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
Zsmith
5 years ago Place LM Exchange
209Views
1like
3Comments
Add option to disable email reply commands
Please add an option to disable the "reply commands" footer section in notification emails. We want our users to follow our organisationalprocess 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
Mosh
7 years ago Place Archive
2Views
1like
2Comments
Count of Windows Processes
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 "Idle" process and the "_Total" metrics. This behaviour is unlikely to be of great benefit; the main use case will involve editing the filters (and cloning the DS as appropriate) such that it only brings back processes you care about (and not, for example, the dozens of svchost processes that will be present on every Windows machine). Also returned are thread count, file handle count, and working set metrics, each being the sum of the per-process metrics. This is possible as these are instantaneous values. Note that unlike the per-process DataSource, CPU metrics cannot be returned. This is because these metrics are returned by WMI as incremental counters and the appearance and disappearance of individual processes between polls would render any sum meaningless. It is however possible to see combined CPU metrics for multiple processes via manipulation of theWinProcessStats- DataSource (clone and filter for the processes you need) and smart graphs with a sum aggregation. v1.0.0 Exchange Locator ID:XHT4MD Example of instances found: Overview graphs: Per-instance graphs:
Antony_Hawkins
7 years ago Place Archive
14Views
0likes
0Comments