|
|
The features on this page require a GENESIS64 Advanced license and are not available with GENESIS64 Basic SCADA . |
|
|
The features on this page require a GENESIS64 Advanced license and are not available with GENESIS64 Basic SCADA . |
Current Archive State
Events Logged Count
Print Count
Print Input Count
Received Events Count
Size of the Log Queue
Size of Print Queue
Store and Forward Files Creation Count
Store and Forward Files Removal Count
Successful Logs to Primary Count
Successful Logs to Secondary Count
Total # of Dropped Events
Watchdog Update Count
Alarms per Second - Includes changes that trigger an update without generating a new alarm.
DA Points on Scan
DA Points Update Rate
Invalid Points Requested by Clients - Counts bad tag names requested by client of alarm server.
Invalid Points Requested by Server - Counts bad tags requested by alarm server.
Total # of Alarm Areas for Active Configuration
Total # of Alarms Configured for Active Configuration
Total # of Alarms Enabled for Active Configuration
Total # of Online Changes
Total # of Subscriptions
Total Alarms Count
Watchdog Update Count
Failed
Input Rate
Passed
Processed Rate
Queue Size
Failed
Input Rate
Passed
Processed Rate
Queue Size
Client Update Watchdog - Rate that monitors the periodic processing of updates - may be obsoleted later.
Data Output Rate - The rate updates are sent.
Cache read load % - The percentage of time spent by the cache thread by reading from the cache. This counter is computed on the start of every "caching period".
Cache reads/sec - Number of properties successfully read from the database cache per second.
Cache total load % - The percentage of time spent by the cache thread by operating the database (that is, reading + writing). This counter is computed on the start of every "caching period".
Cache write load % - The percentage of time spent by the cache thread by writing into the cache. This counter is computed on the start of every "caching period".
Cache writes/sec - Number of properties successfully written into the cache per second.
DA points on scan - Number of real time points subscribed by AC.
DA points update rate - Updates per second on the real time points.
Equipment Configured Count - The number of equipment configured in the configuration database.
Equipment Properties Configured as Always On Scan Count - The number of equipment properties configured to be always on scan.
Equipment Properties Configured Count - The number of equipment properties configured in the configuration database.
Events cache size - The number of events and alarms that are currently in an abnormal state, and being cached in the AssetWorX memory.
Events input queue length - The number of events waiting in the input queue to the rules engine. This should remain at zero, or could raise for a short period of time in the case of an input peak.
Events input/sec - Events per second comming into AssetWorX
Events output/sec - Events per second going out of AssetWorX
Events processed/sec
Events processing load % - The CPU load of the event processing part of AssetWorX
Average items in queue
Pool Utilization %
COV Errors Count
COV Transactions Count
Device with Highest Subscription Count
Devices Counfigured in Database Count
Devices in Cache Count
Highest Subscription Count to a Device
Objects Configured in Database Count
Objects in Cache Count
Read Property Errors Count
Read Property Multiple Errors Count
Read Property Multiple Transactions Count
Received COV Updates Count
Received Read Property Multiple Updates Count
Received Read Property Updates Count
Subscribed Points Count
Write Property Errors Count
Write Property Multiple Errors Count
Write Property Multiple Transactions Count
Write Property Transactions Count
# of currently executing queries at a given time
Average query execution time (ms)
Average query result set
Configured Dataflows Count
Configured Models Count
Online Models Count
Total # of executed queries since service start
Total # of failed queries since service start
Total # of invalid queries
These counters relate to information regarding the Energy Calculations processing. The counters may go up and down over time. Typically, they tend to have higher values for processing time towards the end of the day and faster ones at the beginning of the day. The storage times indicate how long it takes to save the calculations in the database. Typically, base summaries will take longer than hourly or daily summaries. The counters produce both overall values (Cycle process time etc.) as well as specific values (Standard calculations (base summary) processing time). % of Completed calculations is the percentage of Energy Calculations that completed, ie did not fail for some reason. A low value indicates data collection and/or configuration issues.
Note that the counters will update over time. Typically, energy calculations are run at about 15 minutes intervals.
For processing interval counters we could set a time limit past which we can set an alert. For example, a typical calculation processing should take less than 15 minutes.
If % of completed calculations is less that say 90 or 95% this may be a cause of concern.
% of Completed Calculations
Base Summaries Storage Time (sec)
Calculation Cycle Process Time (sec)
Daily Summaries Storage Time (sec)
Derived (base summaries) Process Time (sec)
Derived (daily summaries) Process Time (sec)
Derived (hourly summaries) Process Time (sec)
Hourly Summaries Storage Time (sec)
Metadata re-Processing Time (sec)
Standard (base summaries) Process Time (sec)
Standard (daily summaries) Process Time (sec)
Standard (hourly summaries) Process Time (sec)
These counters produce information regarding the summarization of meter data. The counters indicate the overall time required (to process in memory as well as to save the meter summaries to the database) along with the incoming raw meter samples vs the produced meter summaries. The counters will update when new meter summaries are produced, typically every 15 minutes. A low value of meter summaries indicates potential communication issues or configuration issues.
For processing interval counters we could set a time limit past which we can set an alert. For example, a typical processing should take less than 5 minutes
Typical raw count values will be much larger than summary counts. For example, say 5000 raw meter values may produce only 120 summaries (one for each meter)
If the count of meter summaries drops low or zero, this is an indication of issues or communications
Count of Meter Summaries
Count of Raw Meter Values
Count of Raw Related Meter Values
Count of Related Meter Summaries
Meter Data Process Time (sec)
Related Meter Data Process Time (sec)
These counters relate to information regarding the External data import. Energy AnalytiX supports external data import for the following items:
Meter data
Related Meter data
Metadata
Weather data
Rates
Budgeted costs
The % imported counters indicate the ratio of successfully imported values. A low value of the above counters indicates system issues such as misconfiguration, database load issues, limited hard disk space etc. These counters may or may not update, based on application settings (i.e. if External data are utilized at all).
For processing interval counters we could set a time limit past which we can set an alert. For example, a typical processing should take less than 5 minutes
If % of imported data is less that say 90 or 95% this may be a cause of concern
% of Imported Financial Data
% of Imported Metadata Data
% of Imported Meter Data
% of Imported Rate Data
% of Imported Related Meter Data
% of Imported Weather Data
Financial Data Import Time (sec)
Metadata Data Import Time (sec)
Meter Data Import Time (sec)
Rate Data Import Time (sec)
Related Meter Data Import Time (sec)
Weather Data Import Time (sec)
The above counters relate to historical data support within Energy AnalytiX. A high number of failed requests or a low number for Good data indicates communication or load performance issues with respect to Platform Services and Historian (such as Hyper Historian). The Batch Process Time indicates the time requested to process all received data, including time to merge data if backfill operation is triggered, time to save historian samples etc. A continuously growing value indicates application overloading and system misconfiguration. The Average sample count per request is used to detect if Energy AnalytiX is configured to request a huge number of historian samples, in which case it is constantly breaking the requests into smaller ones.
If the % of failed requests is high, this points to loading issues or communication issues
If the processing time of each batch is way too long, say more than 15 minutes, this can point to loading or database timeout issues
If the % of Good data is below 95%, this points to communication issues
% of Failed Requests
% of Good Data
Average Samples per Request
Batch Process Time (sec)
Average Query Execution Time
Average Query Execution Time Base
Cache Hit Ratio
Failed Queries Rate
These counters indicate percentage of raw data through Platform Services. A low value indicates communication issues or extreme network delays. The above counters will be updated about every 1 min.
If the % counters drop below 90% or 95% indicate possible communication issues
% of Good Quality Data (metadata)
% of Good Quality Data (meters)
% of Good Quality Data (rates)
% of Good Quality Data (weather)
Average Query Execution Time - Represents the average database query execution time (in milliseconds).
Cache Hit Ratio - Represents the percentage of hits to the internal cache that holds database, Web Service, or MobileHMI PM call results.
Failed Queries Rate
Average Log Append Time
Failed Log Writes Rate
Input Data Update Rate
Logging Queue Size
Logging Rate
Number of Assets on Scan
Number of Fault Rules on Scan
Browse Request Count - Same as Request Count, but only for Browse requests.
Browse Requests per Second - Same as Requests per Second, but only for Browse requests.
Custom Request Count - Same as Request Count, but only for Custom requests.
Custom Requests per Second - Same as Requests per Second, but only for Custom requests.
Data Update Count - Number of all data updates sent to clients by the particular Point Manager. This counter always grows. Value of 0 means the Point Manager never sent any data update to any client.
Data Updates per Second - Number of data updates sent to clients by the particular Point Manager per second. The higher the value is, the busier the Point Manager is.
Dataset Request Count - Same as Request Count, but only for Dataset requests.
Dataset Requests per Second - Same as Requests per Second, but only for Dataset requests.
Dropped Data Update Count - Number of dropped data updates. A dropped data update is a data update that has been discarded before sending to a client, because a newer data update became available. This counter always grows. Too many dropped updates indicates the clients requested faster scan rate than they can handle. Dropped updates create unnecessary load to the server.
Dropped Data Updates per Second - Number of dropped data updates per second. High values indicate overloading.
Event Update Count - Same as Data Update Count, but represents for Event updates. Event updates include AE notifications, updates from procedures and dataset updates.
Event Updates per Second - Same as Data Updates per Second, but for Event updates.
Method Request Count - Same as Request Count, but only for Method requests.
Method Requests per Second - Same as Requests per Second, but only for Method requests.
Point Count - Number of points handled by the particular Point Manager.
Read/Write Request Count - Same as Request Count, but only for Read/Write requests.
Read/Write Requests per Second - Same as Requests per Second, but only for Read/Write requests.
Request Count - Number of all requests handled by the particular Point Manager. This counter always grows. Value of 0 means the Point Manager never handled any request, i.e. it has not been used (so far).
Requests per Second - Number of all requests handled by the particular Point Manager per second. The higher the value is, the busier the Point Manager is.
Subscription Request Count - Same as Request Count, but only for Subscription requests.
Subscription Requests per Second - Same as Requests per Second, but only for Browse requests.
Aggregator Cache Size - Count of points that are in the Aggregator’s cache. These points are on scan, but no client is currently subscribed to them. Points in cache add load to under laying servers, increase memory usage and CPU utilization, but improve the performance of switching client displays.
Event ID Cache Size - Count of EventIDs stored in EventID cache, which is used to check security when acknowledging alarms. The count should never exceed the number of all configured alarms.
Invalid Point Name Requests Count
Session Count - Number of sessions currently handled by the server.
Unknown Point Name Requests Count
Queue Size - Length of update queue used by an internal session. Internal session may be used by Point Managers that request points on other Point Managers (e.g. Aggregator). If the queue grows, it means the Point Manager using the internal session does not remove the updates from the queue as quick as it should. It indicates a serious error or overload of the Point Manager.
The difference between the counter instances in Session and Session (PID) is that:
An instance in Session category represents all occurrences of a certain client application on one computer, e.g. all GraphWorX’s running on PC1 will be counted in one instance.
An instance in Session (PID) category represents each occurrence of a client application separately, e.g. starting GraphWorX, stopping it, starting another GraphWorX on the same computer creates two instances.
Instances in Session (PID) are more “granular” than instances in Session category.
Dropped Data Updates per Second - Number of dropped data updates in the particular session per second. A high value indicates the client that created the session requested faster scan rate than it can handle.
Pending Browse Requests - Same as Pending Requests, but only for Browse requests.
Pending Custom Requests - Same as Pending Requests, but only for Custom requests.
Pending Dataset Requests - Same as Pending Requests, but only for Dataset requests.
Pending Method Requests - Same as Pending Requests, but only for Method requests.
Pending ReadWrite Requests - Same as Pending Requests, but only for Read/Write requests.
Pending Requests - Number of requests that have been sent to FWX server, but the server did not send any response back yet. Constant high value means the particular session is overloading the server. Growing value may indicate a problem in the server (the server does not respond to incoming requests).
Pending Subscribe Requests - Same as Pending Requests, but only for Subscribe requests.
Point Count - Number of points being used by the particular session.
Requests per Second - Number of requests the particular session sends to the server. This can be used to determine which session causes the biggest load.
Responses per Second - Number of responses the server sends to the particular session. Note that Responses are Results (one per each Request) + Updates, i.e. RequestRate does not have to be equal to ResponseRate.
Output Queue Size - Size of the output queue for the particular session. Should not grow over time.
Output Updates per Second - Number of responses sent though the session’s output queue per second.
Response Queue Size
Configured Aliases Count
Configured Themes Count
% of cache hits - Represents the percentage of hits to the internal cache that holds database query results.
% of cache utilization - Represents how much of the internal cache is being utilized, in percentage, at any given moment.
% of failed queries - Represents the percentage of failed queries (queries that ended in exception) over the total # of queries.
% of failed queries (base) -
Average query execution time (ms) - Represents the average query execution time in milliseconds.
Cache reads/sec - Represents how many cache reads are being performed per second.
Cache writes/sec - Represents how many cache writes are being performed per second.
Configured Objects Count
Failed queries/sec - Represents the number of failed queries (queries that ended in exception) per second.
Queries/sec - Represents how many queries per second are being executed.
Total # of active queries - Represents the number of active queries to databases at any given time.
DA Point Updates per Second
DA Points on Scan Count
Number of BAD quality points
Number of GOOD quality points
Queued Data Packages Count
Cached Archive File Count
Cached Datablock Count
Filtered Request Count
IO Reads per Second (KB)
IO Writes per Second (KB)
Queued IO Request Count
Queued IO Volume Operation Count
Queued Read/Write Request Count
Queued Sync Request Count
Requests per Second
Enabled Calculated Tags Count
Enabled Collected Tags Count
Enabled Merged Tags Count
Logged Values Count
Logged Values per Second
Performance Calculations Count
Performance Calculations per Second
Read Values Count
Read Values per Second
Total Calculated Tags Count
Total Collected Tags Count
Total Merged Tags Count
Active Connections Count
Published Dynamic Points Count
Published Static Points Count
4k Messages Sent Count
Bytes Received Count
Bytes Sent Count
Messages Sent Count
Messages Sent Errors Count
Data Packages Error Sent Count
Data Packages Sent Count
Disk Data Updates Count
Memory Data Updates Count
Points On Scan
Command Browse Attempts Count
Command Browse Errors Count
Command Dynamic Point Subscribe Attempts Count
Command Dynamic Point Subscribe Errors Count
Command Method Call Attempts Count
Command Method Call Errors Count
Command Refresh Attempts Count
Command Write Attempts Count
Command Write Errors Count
Commands Received Count
Command Received Errors Count
Heartbeat Attempts Count
Heartbeat Errors Count
Open Attempts Count
Open Errors Count
Publish Attempts Count
Publish Errors Count
Refresh Attempts Count
Refresh Errors Count
History Values Wrote Count
History Values Wrote Errors Count
Configured Aliases Count
Configured Unit Conversions Count
Failed Point Updates Rate
Point Update Rate
Succeeded Point Updates Rate
Triggered Events
Browser session count
Count of Service Engines in Disposed State
Count of Service Engines in Empty State
Count of Service Engines in Ready State
Count of Service Engines in Running State
Count of Service Engines in Suspended State
Count of Service Engines in Uninitialized State
Service Engine count
Bytes received
Bytes sent
Current Service Engine State
Messages received
Messages sent
Size of BuildingBlock DOM
Size of Client DOM
% of failed calls - Represents the percentage of failed calls (calls that ended in exception) for the PM over the total # of calls.
Average call execution time (ms) - Represents the average call execution time, in milliseconds, to the PM. NOTE: this number will usually be quite small as most of the processing happens in memory so it is quite fast.
Calls/sec - Represents the number of calls per second to the PM.
Failed calls/sec - Represents the number of failed calls (calls that ended in exception) per second for the PM.
Total # of active calls - Represents the total number of active calls to the PM at any given time. If calls are very fast this number is likely to be zero most of the time.
Current number of Modbus frames in Pending state
Current number of Modbus frames in Waiting state
Current number of OPC AE Clients
Current number of OPC AE Subscriptions
Current number of OPC DA Clients
Current number of OPC DA Groups
Current number of DA Items
Current number of sockets in Idle state
Current number of sockets in Use
Current number of Tag objects
Current number of Write Modbus frames in Pending state
Current number of Write Modbus frames in Waiting state
Total number of Modbus frames received
Total number of Modbus frames received (Bad in row)
Total number of Modbus frames received (Bad)
Total number of Modbus frames received (Good)
Total number of Modbus frames sent
Total number of OPC AE Callbacks sent
Total number of OPC AE Events sent
Total number of OPC DA Callbacks sent
Total number of OPC DA Events sent
Total number of Sockets
Total number of Write Modbus frames completed
Devices on scan
Modbus READ packets received as BAD
Modbus READ packets received as Exceptions
Modbus READ packets received as OK
Modbus READ packets received, TOTAL
Modbus READ packets sent
Modbus WRITE packets received as BAD
Modbus WRITE packets received as Exceptions
Modbus WRITE packets received as OK
Modbus WRITE packets received, TOTAL
Modbus WRITE packets sent
Number of sockets
Points subscribed
Tags on scan
# of active calls - Represents the total number of active calls to this plugin at any given time. If calls are very fast this number is likely to be zero most of the time.
% of failed calls - Represents the percentage of failed calls (calls that ended in exception) for this plugins over the total # of calls to this plugin.
% of timed out calls - Represents the percentage of timed out calls for this plugin.
Average call execution time (ms) - Represents the average call execution time, in milliseconds, for this plugin.
Calls/sec - Represents the number of calls per second to this plugin.
Failed calls/sec
Timed out calls/sec - Represents the number of timed out calls for this plugin per second.
# of active FwxAsyncClient instances - Represents the total number of FwxAsyncClient instances currently used by the OData Point Manager to retrieve data. The OData PM will create a FwxAsyncClient instance and cache it with a sliding expiration of 1 minute: all calls received during the window will reuse the same instance; if the sliding window expires the cached instance will be disposed. If authentication + impersonation are enabled, a dedicated FwxAsyncClient instance will be created per user connected (to keep the security contexts separated).
Total # of active calls - Represents the total number of active calls to all plugins at any given time. If calls are very fast this number is likely to be zero most of the time.
Total % of failed calls - Represents the percentage of failed calls (calls that ended in exception) for all plugins over the total # of calls to all plugins.
Total % of timed out calls - Represents the percentage of timed out calls for all plugins.
Total calls/sec - Represents the number of calls per second to all plugins.
Total failed calls/sec - Represents the number of failed calls (calls that ended in exception) per second for all plugins.
Total timed out calls/sec - Represents the number of timed out calls for all plugins per second.
Read Errors Count
Reads Pending
Reads Succeeded Count
Requests Pending
Write Errors Count
Writes Pending
Writes Succeeded Count
Redirector command average time (ms)
Redirector command max time (ms)
Redirector command min time (ms)
Redirector commands
Redirector commands failed
Redirector commands succeeded
Report average time (ms)
Report min time (ma)
Total failed reports
Total reports in queue
Total reports processed
Total reports succeeded
Total reports with errors
Read Errors Count
Reads Count
Write Errors Count
Writes Count
Active directory request cumulative duration seconds - The cumulative duration of Active Directory requests in seconds.
Active directory request rate - The rate of Active Directory requests per second.
Security sessions - Current number of security sessions.
User auto logout count - Cumulative counter of auto logouts on all security sessions.
User login failure count - Cumulative counter of failed login requests on all security sessions.
User login success count - Cumulative counter of successful login requests on all security sessions.
User logout failure count - Cumulative counter of failed logout requests on all security sessions.
User logout success count - Cumulative counter of successful logout requests on all security sessions.
Users currently logged in - Current number of uses on all security sessions. Inclusive automatically logged in users.
Device Configured Count – The number of the devices configured in the configuration database.
Device Subscribed Count – The number of the devices on scan (some point from the device is subscribed). It’s sum of Device Subscribed Offline Count and Device Subscribed Online Count counters.
Device Subscribed Offline Count – The number of the devices that are on scan but offline
Device Subscribed Online Count – The number of the devices that are on scan and online.
Network Configured Count – The number of the networks configured in the configuration database.
Request Average Process Time – The average time that is needed to process one request (read or write), calculated since the point manager was started.
Request Average Queue Time – The average time that the request waits in the processing queue, calculated since the point manager was started. (This is part of the average process time.)
Request Processed Count Total – The total number of the processed requests since the point manager was started.
Request Read Count Total – The total number of read requests processed since the point manager was started.
Request Read Error Count Total – The total number of read errors encountered since the point manager was started.
Request Write Count Total – The total number of write requests since the point manager was started.
Request Write Error Count Total – The total number of write errors encountered since the point manager was started.
Server Running – Elapsed time from the moment when the point manager was started.
Server Started – The timestamp of when the server was started, UTC time.
Socket Allocated Count – The number of allocated sockets that are used for the communication with devices over the network.
Socket Blocked Count – The number of the sockets that are currently in use.
Socket Blocked Count Total – The total number of the sockets that have been created since the point manager was started.
Socket Freed Count – The number of the sockets that are currently available.
Socket Freed Count Total – The total number of the sockets that have been freed since the point manager was started.
Tag Client DA Subscription Count – The number of active client DA subscriptions.
Tag Configured Count – The number of the configured tags in the configuration database.
Tag Subscribed Count – The number of currently subscribed tags, including DA and dataset tags.
Trap Aborted Count Total – The total number of aborted traps.
Trap Configured Count – The number of the traps configured in the configuration database.
Trap Error Count Total – The total number of the errors when receiving the traps.
Trap Received Count Total – The total number of the received traps.
Inserted Comments
Logging Table Queries
Read Requests from Clients
Samples Returned
Support Table Queries
Configured Tags Count
DA Updates per Second
Database Group Count
Logging Group Count
Store and Forward Files Creation Rate
Store and Forward Files Removal Rate
Standby Cache Size
Successful Logs to Primary per Second
Successful Logs to Secondary per Second
Points Failed Count
Points On Scan
Trigger Errors Count
Trigger Notifications Count
Triggers Configured Count
Triggers Running Count
Triggers Subscribed Count
Client Points on Scan
Client Subscribed Point Count
Client Subscribed Point Failure Count
Client Subscribed Point Failure Rate
Client Subscribed Point Rate
Client Subscribed Point Success Count
Client Subscribed Point Success Rate
Client Updated Count
Client Update Rate
Client Write Success Count
Client Write Success Rate
Client Writes Count
Client Writes Failure Count
Client Writes Failure Rate
Client Writes Rate
Clients Connected
Configured Items Count
DA Points on Scan
DA Update Count
DA Update Rate
DA Write Success Count
DA Write Success Rate
DA Writes Count
DA Writes Failure Count
DA Writes Failure Rate
DA Writes Rate
Pending Writes Queue Size
Client Points on Scan
Client Subscribed Point Count
Client Subscribed Point Failure Count
Client Subscribed Point Failure Rate
Client Subscribed Point Rate
Client Subscribed Point Success Count
Client Subscribed Point Success Rate
Client Update Count
Client Update Rate
Client Write Success Count
Client Write Success Rate
Client Writes Count
Client Writes Failure Count
Client Writes Failure Rate
Client Writes Rate
Clients Connected
Configured Items Count
DA Points on Scan
DA Update Count
DA Update Rate
DA Write Success Count
DA Write Success Rate
DA Writes Count
DA Writes Failure Count
DA Writes Failure Rate
DA Writes Rate
Pending Writes Queue Size
Client Points on Scan
Client Subscribed Point Count
Client Subscribed Point Failure Count
Client Subscribed Point Failure Rate
Client Subscribed Point Rate
Client Subscribed Point Success Count
Client Subscribed Point Success Rate
Client Update Count
Client Update Rate
Client Write Success Count
Client Write Success Rate
Client Writes Count
Client Writes Failure Count
Client Writes Failure Rate
Client Writes Rate
Clients Connected
Configured Items Count
DA Points on Scan
DA Update Count
DA Update Rate
DA Write Success Count
DA Write Success Rate
DA Writes Count
DA Writes Failure Count
DA Writes Failure Rate
DA Writes Rate
Pending Writes Queue Size
Client Points on Scan
Client Subscribed Point Count
Client Subscribed Point Failure Count
Client Subscribed Point Failure Rate
Client Subscribed Point Rate
Client Subscribed Point Success Count
Client Subscribed Point Success Rate
Client Update Count
Client Update Rate
Client Write Success Count
Client Write Success Rate
Client Writes Count
Client Writes Failure Count
Client Writes Failure Rate
Client Writes Rate
Clients Connected
Configured Items Count
DA Points on Scan
DA Update Count
DA Update Rate
DA Write Success Count
DA Write Success Rate
DA Writes Count
DA Writes Failure Count
DA Writes Failure Rate
DA Writes Rate
Pending Writes Queue Size
% of cache hits
% of cache utilization
% of failed calls
Average call execution time (ms)
Cache reads/sec
Cache writes/sec
Calls/sec
Configured Services Count
Failed calls/sec
Total # of active calls
See Also:
Platform Services Health Monitoring Features
System Health Monitor Services Enumeration