Converted the Exchange 2010 Performance Monitoring Templates. Removed unsupported items and replaced them with equivalents that could be found. Added some new items and graphs.
matt snead
There are no macros links in this template.
There are no template links in this template.
There are no discovery rules in this template.
| Name | Description | Type | Key and additional info |
|---|---|---|---|
| Exchange ADAccess Processes(*)\LDAP Read Time |
-
 | Zabbix agent |
perf_counter[“\MSExchange ADAccess Processes(*)\LDAP Read Time”]
Update: 30s
 |
| Exchange Transport Q - Msgs Queued for Delivery/sec |
Shows the number of messages queued for delivery per second. Determines current load. Compare values to historical baselines.
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\Messages Queued for Delivery Per Second”]
Update: 30s
 |
| Exchange Transport Database ==> Instances(edgetransport/Transport Mail Database) I/O Database Writes/sec |
-
 | Zabbix agent |
perf_counter[“\MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\I/O Database Writes/sec”]
Update: 30s
 |
| Exchange Transport Database ==> Instances(edgetransport/Transport Mail Database) I/O Database Reads/sec |
-
 | Zabbix agent |
perf_counter[“\MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\I/O Database Reads/sec”]
Update: 30s
 |
| Exchange Mailbox Store Interface(*) RPC Requests Outstanding |
Shows the total number of outstanding RPC requests. Used for determining current load.
 | Zabbix agent |
perf_counter[“\MSExchange Store Interface(*)\RPC Requests Outstanding”]
Update: 30
 |
| Exchange Mailbox Database (Information Store) Database Cache % Hit |
Shows the percentage of database file page requests fulfilled by the database cache without causing a file operation. If this percentage is too low, the database cache size may be too small. Should be over 90% for companies with majority online mode clients. Should be over 99% for companies with majority cached mode clients. If the hit ratio is less than these numbers, the database cache may be insufficient.
 | Zabbix agent |
perf_counter[“\MSExchange Database(Information Store)\Database Cache % Hit”]
Update: 30
 |
| Exchange Mailbox IS Client(*) JET Log Records/sec |
Shows the rate that database log records are generated while processing requests for the client. Used to determine current load.
 | Zabbix agent |
perf_counter[“\MSExchangeIS Client Type(*)\Jet Log Records/sec”]
Update: 30
 |
| Exchange Mailbox Calendar Attendant Average Calendar Attendant Processing Time |
Shows the average time to process an event in the Calendar Attendant. Should be a low value at all times. High values may indicate a performance bottleneck.
 | Zabbix agent |
perf_counter[“\MSExchange Calendar Attendant\Average Calendar Attendant Processing Time”,30]
Update: 30
 |
| Exchange Mailbox Database I/O Database Writes (Attached) Average Latency |
Indicates the average time, in ms, to write to the database file. This counter isn’t a good indicator for client latency because database writes are asynchronous. In general, this latency should be less than the MSExchange Database I/O Database Reads (Attached) Average Latency when battery-backed write caching is utilized.
 | Zabbix agent |
perf_counter[“\MSExchange Database(*)\I/O Database Writes (Attached) Average Latency”]
Update: 30
 |
| Exchange RpcClientAccess Connection Count |
Shows the total number of client connections maintained
 | Zabbix agent |
perf_counter[“\MSExchange RpcClientAccess\Connection Count”]
Update: 30
 |
| Exchange Mailbox IS Client(*) RPC Operations/sec |
Shows what client protocol is performing an excessive amount of RPC Operations/sec. High IMAP4, POP3, or Outlook Anywhere latency can indicate problems with Client Access servers rather than Mailbox servers. This is especially true when other clients (which includes MAPI) latency is lower in comparison. In some instances, high IMAP latencies could indicate a bottleneck on the Mailbox server in addition to the latencies that the Client Access server is experiencing.
 | Zabbix agent |
perf_counter[“\MSExchangeIS Client Type(*)\RPC Operations/sec”]
Update: 30
 |
| Exchange Transport SmtpSend(_total) Messages Sent/sec |
Shows the number of messages sent by the SMTP send connector each second. Determines current load. Compare values to historical baselines.
 | Zabbix agent |
perf_counter[“\MSExchangeTransport SmtpSend(_total)\Messages Sent/sec”]
Update: 30s
 |
| Exchange ADAccess Domain Controllers(*)\LDAP Search Time |
-
 | Zabbix agent |
perf_counter[“\MSExchange ADAccess Domain Controllers(*)\LDAP Search Time”]
Update: 30s
 |
| Exchange Mailbox Store Interface(*) ROP Requests outstanding |
Shows the total number of outstanding remote operations requests. Used for determining current load.
 | Zabbix agent |
perf_counter[“\MSExchange Store Interface(*)\ROP Requests outstanding”]
Update: 30
 |
| Exchange Mailbox Process(MSExchangeMailboxAssistants) % Processor Time |
Shows the amount of processor time being consumed by mailbox assistants. Should be less than 5% of overall CPU capacity.
 | Zabbix agent |
perf_counter[“\Process(MSExchangeMailboxAssistants)\% Processor Time”]
Update: 30
 |
| Exchange Middle-Tier Storage(*)\Items Dumpster Deletions/sec |
Shows the rate at which items are deleted from the transport dumpster on this server. Determines the current rate of transport dumpster deletions. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeTransport Dumpster Dumpster Deletes/sec”]
 | Zabbix agent |
perf_counter[“\MSExchange Middle-Tier Storage(*)\Items Dumpster Deletions/sec”]
Update: 30s
 |
| Exchange Mailbox Database (Information Store) Database Page Fault Stalls/sec |
Shows the rate that database file page requests require of the database cache manager to allocate a new page from the database cache. If this value is nonzero, this indicates that the database isn’t able to flush dirty pages to the database file fast enough to make pages free for new page allocations.
 | Zabbix agent |
perf_counter[“\MSExchange Database(Information Store)\Database Page Fault Stalls/sec”]
Update: 30
 |
| Exchange Mailbox Database I/O Database Writes (Recovery) Average Latency |
Indicates the average time, in ms, to write to the database file. In general, this latency should be less than the MSExchange Database I/O Database Reads (Recovery) Average Latency when battery-backed write caching is utilized.
 | Zabbix agent |
perf_counter[“\MSExchange Database(*)\I/O Database Writes (Recovery) Average Latency”]
Update: 30
 |
| Exchange Transport Q - Msgs Completed Delivery/sec |
Shows the number of messages delivered per second. Determines current load. Compare values to historical baselines.
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\Messages Completed Delivery Per Second”]
Update: 30s
 |
| Exchange Transport Q - Mailbox Delivery Q |
This monitor shows the number of messages in the active mailbox queues. The returned value should be less than 250 at all times
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\Active Mailbox Delivery Queue Length”]
Update: 30s
 |
| Exchange Mailbox IS Client(*) JET Pages Read/sec |
Shows the rate that database pages are read from disk while processing requests for the client. Used to determine current load.
 | Zabbix agent |
perf_counter[“\MSExchangeIS Client Type(*)\Jet Pages Read/sec”]
Update: 30
 |
| Exchange Mailbox Database I/O Database Reads (Recovery) Average Latency |
Indicates the average time, in ms, to read from the database file. The average value should be below 200 ms. Spikes (maximum values) shouldn’t be higher than 1,000 ms.
 | Zabbix agent |
perf_counter[“\MSExchange Database(*)\I/O Database Reads (Recovery) Average Latency”]
Update: 30
 |
| ExchangeIS Client Type\RPC Requests |
-
 | Zabbix agent |
perf_counter[“\MSExchangeIS Client Type(*)\RPC Requests”]
Update: 30s
 |
| Exchange Mailbox Store Interface(*) RPC Slow Requests latency average (msec) |
Shows the average latency, in ms, of slow requests. Used for determining the average latencies of RPC slow requests.
 | Zabbix agent |
perf_counter[“\MSExchange Store Interface(*)\RPC Slow Requests latency average (msec)”]
Update: 30
 |
| Exchange RPC/HTTP Proxy\Current Number of Unique Users |
Shows the number of unique users currently connected to a back-end server via RPC/HTTP
 | Zabbix agent |
perf_counter[“\RPC/HTTP Proxy\Current Number of Unique Users”]
Update: 30
 |
| Exchange RpcClientAccess Active User Count |
Shows the number of users connected to the information store. Used to determine current user load. MODIFIED_FOR_EX2016-NEW
 | Zabbix agent |
perf_counter[“\MSExchange RpcClientAccess\Active User Count”]
Update: 30
 |
| Exchange Mailbox Database I/O Log Writes Average Latency |
Indicates the average time, in ms, to write a log buffer to the active log file. This counter should be 10 on production servers. If this counter is greater than 10, it’s an indication that the MSExchange Database I/O Database Writes (Attached) Average Latency is too high.
 | Zabbix agent |
perf_counter[“\MSExchange Database(*)\I/O Log Writes Average Latency”]
Update: 30
 |
| ExchangeSearch Indexes(*)\Items Processed/sec |
Shows the average, in ms, of how long it takes to index documents. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchange Search Indices(*) Average Document Indexing Time”]
 | Zabbix agent |
perf_counter[“\MSExchange Search Indexes(*)\Items Processed/sec”]
Update: 30
 |
| Exchange Mailbox Replication(*) CopyQueueLength |
Shows the number of transaction log files waiting to be copied to the passive copy log file folder. A copy isn’t considered complete until it has been checked for corruption. Should be less than 1 at all times for continuous replication.
 | Zabbix agent |
perf_counter[“\MSExchange Replication(*)\CopyQueueLength”]
Update: 30
 |
| Exchange RpcClientAccess\RPC Requests |
-
 | Zabbix agent |
perf_counter[“\MSExchange RpcClientAccess\RPC Requests”]
Update: 30s
 |
| Exchange Mailbox Database (Information Store) Version buckets allocated |
Shows the total number of version buckets allocated. Should be less than 12,000 at all times. The maximum default version is 16,384. If version buckets reach 70% of maximum, the server is at risk of running out of the version store.
 | Zabbix agent |
perf_counter[“\MSExchange Database(Information Store)\Version buckets allocated”]
Update: 30
 |
| Exchange Transport Q - Remote Delivery Q |
MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeTransport Queues(_total) Active Remote Delivery Queue Length”]
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\External Active Remote Delivery Queue Length”]
Update: 30s
 |
| Exchange Mailbox Replication(*) ReplayQueueLength |
Shows the number of transaction log files waiting to be replayed into the passive copy. Indicates the current replay queue length. Higher values cause longer store mount times when a handoff, failover, or activation is performed.
 | Zabbix agent |
perf_counter[“\MSExchange Replication(*)\ReplayQueueLength”]
Update: 30
 |
| Exchange Mailbox Database I/O Database Reads (Attached) Average Latency |
Indicates the average time, in milliseconds (ms), to read from the database file. The average value should be below 20 ms. Spikes (maximum values) shouldn’t be higher than 100 ms.
 | Zabbix agent |
perf_counter[“\MSExchange Database(*)\I/O Database Reads (Attached) Average Latency”]
Update: 30
 |
| Exchange Transport Q - Submission Q |
This monitor shows the number of messages in the submission queue. The returned value should not exceed 100. If sustained high values are occurring, investigate Active Directory and Mailbox servers for bottlenecks or performance-related issues. MODIFIED_FOR_EX2016-NEW
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\Submission Queue Length”]
Update: 30s
 |
| Exchange Mailbox Store Interface(_Total) RPC Requests outstanding |
Shows the current number of outstanding RPC requests. Should be 0 at all times.
 | Zabbix agent |
perf_counter[“\MSExchange Store Interface(_Total)\RPC Requests outstanding”]
Update: 30
 |
| Exchange Search Indexes(*)\Crawler: Mailboxes Remaining |
This counter is used to determine if a full crawl is occurring for any specified database. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchange Search Indices(*) Full Crawl Mode Status”] If CPU resources are high, it’s possible content indexing is occurring for a database or set of databases.
 | Zabbix agent |
perf_counter[“\MSExchange Search Indexes(*)\Crawler: Mailboxes Remaining”]
Update: 30
 |
| Exchange Submission Successful Submissions Per Second |
Determines current mail submission rate. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchange Mail Submission(*) Successful Submissions Per Second”]
 | Zabbix agent |
perf_counter[“\MSExchange Submission\Successful Submissions Per Second”]
Update: 30
 |
| Exchange OWA User Count |
Shows the number of users connected to the information store. Used to determine current user load. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeIS User Count”]
 | Zabbix agent |
perf_counter[“\MSExchange OWA\Current Users”]
Update: 30
 |
| Exchange Outlook (MapiHttp) User Count |
Shows the number of users connected to the information store. Used to determine current user load. MODIFIED_FOR_EX2016-NEW
 | Zabbix agent |
perf_counter[“\MSExchange MapiHttp Emsmdb\Active User Count”]
Update: 30
 |
| Exchange Transport Q - Msgs Submitted/sec |
-
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\Messages Submitted Per Second”]
Update: 30s
 |
| ExchangeIS Store(*)\RPC Average Latency |
-
 | Zabbix agent |
perf_counter[“\MSExchangeIS Store(*)\RPC Average Latency”]
Update: 30s
 |
| Exchange RpcClientAccess\RPC Averaged Latency |
Shows the average latency, in ms, of the most recent RPCs to the Information Store service. These RPCs are used to get content for the filter daemon for the specified database. Should coincide with the latencies that Outlook clients are experiencing. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchange Search Indices(*) Average Latency of RPCs Used to Obtain Content”]
 | Zabbix agent |
perf_counter[“\MSExchange RpcClientAccess\RPC Averaged Latency”]
Update: 30
 |
| Exchange ADAccess Processes(*)\LDAP Search Time |
-
 | Zabbix agent |
perf_counter[“\MSExchange ADAccess Processes(*)\LDAP Search Time”]
Update: 30s
 |
| ExchangeIS Client Type(*)\RPC Average Latency |
-
 | Zabbix agent |
perf_counter[“\MSExchangeIS Client Type(*)\RPC Average Latency”]
Update: 30s
 |
| Exchange Mailbox Resource Booking Average Resource Booking Processing Time |
Shows the average time to process an event in the Resource Booking Attendant. Should be a low value at all times. High values may indicate a performance bottleneck.
 | Zabbix agent |
perf_counter[“\MSExchange Resource Booking\Average Resource Booking Processing Time”]
Update: 30
 |
| Exchange Mailbox Database I/O Log Reads Average Latency |
Indicates the average time, in ms, to read data from a log file. Specific to log replay and database recovery operations. The average value should be below 200 ms. Spikes (maximum values) shouldn’t be higher than 1,000 ms.
 | Zabbix agent |
perf_counter[“\MSExchange Database(*)\I/O Log Reads Average Latency”]
Update: 30
 |
| Exchange Transport Q - Msgs Queued For Delivery |
MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeTransport Queues(_total) Aggregate Delivery Queue Length (All Queues)”]
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\Messages Queued For Delivery”]
Update: 30s
 |
| Exchange Transport Database ==> Instances(edgetransport/Transport Mail Database) I/O Log Writes/sec |
-
 | Zabbix agent |
perf_counter[“\MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\I/O Log Writes/sec”]
Update: 30s
 |
| Exchange Mailbox Database (Information Store) Database Cache Size (GB) |
Shows the amount of system memory, in megabytes (MB), used by the database cache manager to hold commonly used information from the database files to prevent file operations. Maximum value is RAM-2GB (RAM-3GB for servers with sync replication enabled). This and Database Cache Hit % are useful counters for gauging whether a server’s performance problems might be resolved by adding more physical memory. Use this counter along with store private bytes to determine if there are store memory leaks. If the database cache size seems too small for optimal performance and there is little available memory on the system (check the value of Memory/Available Bytes), adding more memory to the system may increase performance. If there is ample memory on the system and the database cache size isn’t growing beyond a certain point, the database cache size may be capped at an artificially low limit. Increasing this limit may increase performance.
 | Zabbix agent |
perf_counter[“\MSExchange Database(Information Store)\Database Cache Size (MB)”]
Update: 30
 |
| Exchange Transport SmtpReceive(_total) Messages Received/sec |
Shows the number of messages received by the SMTP server each second. Determines current load. Compare values to historical baselines.
 | Zabbix agent |
perf_counter[“\MSExchangeTransport SmtpReceive(_total)\Messages Received/sec”]
Update: 30s
 |
| Exchange Mailbox Database ==> Instances(*) Log Generation Checkpoint Depth |
Represents the amount of work in the log file count that needs to be redone or undone to the database files if the process fails. Should be below 500 at all times for the Mailbox server role. A healthy server should indicate between 20 and 30 for each database instance. If checkpoint depth increases continually for a sustained period, this indicates either a long-running transaction, (which will impact the version store), or a bottleneck involving the database disks.
 | Zabbix agent |
perf_counter[“\MSExchange Database ==> Instances(*)\Log Generation Checkpoint Depth”]
Update: 30
 |
| Exchange Transport Database ==> Instances(edgetransport/Transport Mail Database) I/O Log Reads/sec |
-
 | Zabbix agent |
perf_counter[“\MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\I/O Log Reads/sec”]
Update: 30s
 |
| Exchange Mailbox IS Mailbox(*) Search Rate |
Shows the number of search tasks created per second. Should be less than 10 at all times. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeIS Mailbox(*) Search Task Rate”]
 | Zabbix agent |
perf_counter[“\MSExchangeIS Store(*)\Search/sec”]
Update: 30
 |
| Exchange Mailbox IS Client(*) Directory Access: LDAP Searches/sec |
Shows the current rate that LDAP searches occur while processing requests for the client. Used to determine the current LDAP search rate per protocol. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeIS Client(*) Directory Access: LDAP Searches/sec”]
 | Zabbix agent |
perf_counter[“\MSExchangeIS Client Type(*)\Directory Access: LDAP Searches/sec”]
Update: 30
 |
| Exchange Mailbox IS RPC Operations/sec |
Indicates the current number of RPC operations occurring per second. Should closely correspond to historical baselines. Values much higher than expected indicate that the workload has changed, while values much lower than expected indicate a bottleneck preventing client requests from reaching the server. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeIS RPC Operations/sec”]
 | Zabbix agent |
perf_counter[“\MSExchangeIS Store(*)\RPC Operations/sec”]
Update: 30
 |
| Exchange ADAccess Domain Controllers(*)\LDAP Read Time |
-
 | Zabbix agent |
perf_counter[“\MSExchange ADAccess Domain Controllers(*)\LDAP Read Time”]
Update: 30s
 |
| Exchange Transport Database ==> Instances(edgetransport/Transport Mail Database) Log Generation Checkpoint Depth |
Represents the amount of work (in count of log files) that needs to be redone or undone to the database files if the process fails.
 | Zabbix agent |
perf_counter[“\MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\Log Generation Checkpoint Depth”]
Update: 30s
 |
| Exchange Middle-Tier Storage(*)\Items Moved to Dumpster/sec |
Shows the rate at which items are inserted into the transport dumpster on this server. Determines the current rate of transport dumpster inserts. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeTransport Dumpster Dumpster Inserts/sec”]
 | Zabbix agent |
perf_counter[“\MSExchange Middle-Tier Storage(*)\Items Moved to Dumpster/sec.”]
Update: 30s
 |
| Exchange ActiveSync\Current Requests |
Shows the number of HTTP requests waiting to be assigned to a thread
 | Zabbix agent |
perf_counter[“\MSExchange ActiveSync\Current Requests”]
Update: 30
 |
| Exchange ADAccess Domain Controllers(*)\LDAP Read Calls/sec |
Shows the current rate that LDAP reads occur while processing requests for the client. Used to determine the current LDAP read rate per protocol. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeIS Client(*) Directory Access: LDAP Reads/sec”]
 | Zabbix agent |
perf_counter[“\MSExchange ADAccess Domain Controllers(*)\LDAP Read Calls/sec”]
Update: 30
 |
There are no triggers in this template.
Converted the Exchange 2010 Performance Monitoring Templates. Removed unsupported items and replaced them with equivalents that could be found. Added some new items and graphs.
matt snead
There are no macros links in this template.
There are no template links in this template.
There are no discovery rules in this template.
| Name | Description | Type | Key and additional info |
|---|---|---|---|
| Exchange Transport Q - Mailbox Delivery Q |
This monitor shows the number of messages in the active mailbox queues. The returned value should be less than 250 at all times
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\Active Mailbox Delivery Queue Length”]
Update: 30s
 |
| ExchangeIS Client Type\RPC Requests |
-
 | Zabbix agent |
perf_counter[“\MSExchangeIS Client Type(*)\RPC Requests”]
Update: 30s
 |
| Exchange OWA User Count |
Shows the number of users connected to the information store. Used to determine current user load. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeIS User Count”]
 | Zabbix agent |
perf_counter[“\MSExchange OWA\Current Users”]
Update: 30
 |
| Exchange Transport Database ==> Instances(edgetransport/Transport Mail Database) I/O Database Writes/sec |
-
 | Zabbix agent |
perf_counter[“\MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\I/O Database Writes/sec”]
Update: 30s
 |
| Exchange Outlook (MapiHttp) User Count |
Shows the number of users connected to the information store. Used to determine current user load. MODIFIED_FOR_EX2016-NEW
 | Zabbix agent |
perf_counter[“\MSExchange MapiHttp Emsmdb\Active User Count”]
Update: 30
 |
| Exchange Mailbox Store Interface(*) RPC Requests Outstanding |
Shows the total number of outstanding RPC requests. Used for determining current load.
 | Zabbix agent |
perf_counter[“\MSExchange Store Interface(*)\RPC Requests Outstanding”]
Update: 30
 |
| ExchangeSearch Indexes(*)\Items Processed/sec |
Shows the average, in ms, of how long it takes to index documents. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchange Search Indices(*) Average Document Indexing Time”]
 | Zabbix agent |
perf_counter[“\MSExchange Search Indexes(*)\Items Processed/sec”]
Update: 30
 |
| Exchange Mailbox Database I/O Log Reads Average Latency |
Indicates the average time, in ms, to read data from a log file. Specific to log replay and database recovery operations. The average value should be below 200 ms. Spikes (maximum values) shouldn’t be higher than 1,000 ms.
 | Zabbix agent |
perf_counter[“\MSExchange Database(*)\I/O Log Reads Average Latency”]
Update: 30
 |
| Exchange RpcClientAccess\RPC Averaged Latency |
Shows the average latency, in ms, of the most recent RPCs to the Information Store service. These RPCs are used to get content for the filter daemon for the specified database. Should coincide with the latencies that Outlook clients are experiencing. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchange Search Indices(*) Average Latency of RPCs Used to Obtain Content”]
 | Zabbix agent |
perf_counter[“\MSExchange RpcClientAccess\RPC Averaged Latency”]
Update: 30
 |
| Exchange Mailbox Database I/O Database Reads (Recovery) Average Latency |
Indicates the average time, in ms, to read from the database file. The average value should be below 200 ms. Spikes (maximum values) shouldn’t be higher than 1,000 ms.
 | Zabbix agent |
perf_counter[“\MSExchange Database(*)\I/O Database Reads (Recovery) Average Latency”]
Update: 30
 |
| ExchangeIS Client Type(*)\RPC Average Latency |
-
 | Zabbix agent |
perf_counter[“\MSExchangeIS Client Type(*)\RPC Average Latency”]
Update: 30s
 |
| Exchange Transport SmtpReceive(_total) Messages Received/sec |
Shows the number of messages received by the SMTP server each second. Determines current load. Compare values to historical baselines.
 | Zabbix agent |
perf_counter[“\MSExchangeTransport SmtpReceive(_total)\Messages Received/sec”]
Update: 30s
 |
| Exchange Transport Q - Msgs Queued for Delivery/sec |
Shows the number of messages queued for delivery per second. Determines current load. Compare values to historical baselines.
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\Messages Queued for Delivery Per Second”]
Update: 30s
 |
| Exchange Mailbox Calendar Attendant Average Calendar Attendant Processing Time |
Shows the average time to process an event in the Calendar Attendant. Should be a low value at all times. High values may indicate a performance bottleneck.
 | Zabbix agent |
perf_counter[“\MSExchange Calendar Attendant\Average Calendar Attendant Processing Time”,30]
Update: 30
 |
| Exchange Mailbox Resource Booking Average Resource Booking Processing Time |
Shows the average time to process an event in the Resource Booking Attendant. Should be a low value at all times. High values may indicate a performance bottleneck.
 | Zabbix agent |
perf_counter[“\MSExchange Resource Booking\Average Resource Booking Processing Time”]
Update: 30
 |
| Exchange Mailbox Database I/O Log Writes Average Latency |
Indicates the average time, in ms, to write a log buffer to the active log file. This counter should be 10 on production servers. If this counter is greater than 10, it’s an indication that the MSExchange Database I/O Database Writes (Attached) Average Latency is too high.
 | Zabbix agent |
perf_counter[“\MSExchange Database(*)\I/O Log Writes Average Latency”]
Update: 30
 |
| Exchange Mailbox IS Client(*) Directory Access: LDAP Searches/sec |
Shows the current rate that LDAP searches occur while processing requests for the client. Used to determine the current LDAP search rate per protocol. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeIS Client(*) Directory Access: LDAP Searches/sec”]
 | Zabbix agent |
perf_counter[“\MSExchangeIS Client Type(*)\Directory Access: LDAP Searches/sec”]
Update: 30
 |
| Exchange ADAccess Domain Controllers(*)\LDAP Read Calls/sec |
Shows the current rate that LDAP reads occur while processing requests for the client. Used to determine the current LDAP read rate per protocol. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeIS Client(*) Directory Access: LDAP Reads/sec”]
 | Zabbix agent |
perf_counter[“\MSExchange ADAccess Domain Controllers(*)\LDAP Read Calls/sec”]
Update: 30
 |
| Exchange RpcClientAccess\RPC Requests |
-
 | Zabbix agent |
perf_counter[“\MSExchange RpcClientAccess\RPC Requests”]
Update: 30s
 |
| Exchange Mailbox Database I/O Database Writes (Attached) Average Latency |
Indicates the average time, in ms, to write to the database file. This counter isn’t a good indicator for client latency because database writes are asynchronous. In general, this latency should be less than the MSExchange Database I/O Database Reads (Attached) Average Latency when battery-backed write caching is utilized.
 | Zabbix agent |
perf_counter[“\MSExchange Database(*)\I/O Database Writes (Attached) Average Latency”]
Update: 30
 |
| Exchange Transport Database ==> Instances(edgetransport/Transport Mail Database) I/O Database Reads/sec |
-
 | Zabbix agent |
perf_counter[“\MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\I/O Database Reads/sec”]
Update: 30s
 |
| Exchange Mailbox Process(MSExchangeMailboxAssistants) % Processor Time |
Shows the amount of processor time being consumed by mailbox assistants. Should be less than 5% of overall CPU capacity.
 | Zabbix agent |
perf_counter[“\Process(MSExchangeMailboxAssistants)\% Processor Time”]
Update: 30
 |
| Exchange RpcClientAccess Active User Count |
Shows the number of users connected to the information store. Used to determine current user load. MODIFIED_FOR_EX2016-NEW
 | Zabbix agent |
perf_counter[“\MSExchange RpcClientAccess\Active User Count”]
Update: 30
 |
| Exchange Transport Database ==> Instances(edgetransport/Transport Mail Database) I/O Log Writes/sec |
-
 | Zabbix agent |
perf_counter[“\MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\I/O Log Writes/sec”]
Update: 30s
 |
| Exchange Transport Database ==> Instances(edgetransport/Transport Mail Database) I/O Log Reads/sec |
-
 | Zabbix agent |
perf_counter[“\MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\I/O Log Reads/sec”]
Update: 30s
 |
| Exchange RPC/HTTP Proxy\Current Number of Unique Users |
Shows the number of unique users currently connected to a back-end server via RPC/HTTP
 | Zabbix agent |
perf_counter[“\RPC/HTTP Proxy\Current Number of Unique Users”]
Update: 30
 |
| Exchange RpcClientAccess Connection Count |
Shows the total number of client connections maintained
 | Zabbix agent |
perf_counter[“\MSExchange RpcClientAccess\Connection Count”]
Update: 30
 |
| Exchange Mailbox Database I/O Database Reads (Attached) Average Latency |
Indicates the average time, in milliseconds (ms), to read from the database file. The average value should be below 20 ms. Spikes (maximum values) shouldn’t be higher than 100 ms.
 | Zabbix agent |
perf_counter[“\MSExchange Database(*)\I/O Database Reads (Attached) Average Latency”]
Update: 30
 |
| Exchange Mailbox Store Interface(*) ROP Requests outstanding |
Shows the total number of outstanding remote operations requests. Used for determining current load.
 | Zabbix agent |
perf_counter[“\MSExchange Store Interface(*)\ROP Requests outstanding”]
Update: 30
 |
| Exchange Submission Successful Submissions Per Second |
Determines current mail submission rate. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchange Mail Submission(*) Successful Submissions Per Second”]
 | Zabbix agent |
perf_counter[“\MSExchange Submission\Successful Submissions Per Second”]
Update: 30
 |
| Exchange Mailbox Database (Information Store) Version buckets allocated |
Shows the total number of version buckets allocated. Should be less than 12,000 at all times. The maximum default version is 16,384. If version buckets reach 70% of maximum, the server is at risk of running out of the version store.
 | Zabbix agent |
perf_counter[“\MSExchange Database(Information Store)\Version buckets allocated”]
Update: 30
 |
| ExchangeIS Store(*)\RPC Average Latency |
-
 | Zabbix agent |
perf_counter[“\MSExchangeIS Store(*)\RPC Average Latency”]
Update: 30s
 |
| Exchange ActiveSync\Current Requests |
Shows the number of HTTP requests waiting to be assigned to a thread
 | Zabbix agent |
perf_counter[“\MSExchange ActiveSync\Current Requests”]
Update: 30
 |
| Exchange Mailbox Store Interface(_Total) RPC Requests outstanding |
Shows the current number of outstanding RPC requests. Should be 0 at all times.
 | Zabbix agent |
perf_counter[“\MSExchange Store Interface(_Total)\RPC Requests outstanding”]
Update: 30
 |
| Exchange Mailbox Database (Information Store) Database Page Fault Stalls/sec |
Shows the rate that database file page requests require of the database cache manager to allocate a new page from the database cache. If this value is nonzero, this indicates that the database isn’t able to flush dirty pages to the database file fast enough to make pages free for new page allocations.
 | Zabbix agent |
perf_counter[“\MSExchange Database(Information Store)\Database Page Fault Stalls/sec”]
Update: 30
 |
| Exchange Mailbox Replication(*) ReplayQueueLength |
Shows the number of transaction log files waiting to be replayed into the passive copy. Indicates the current replay queue length. Higher values cause longer store mount times when a handoff, failover, or activation is performed.
 | Zabbix agent |
perf_counter[“\MSExchange Replication(*)\ReplayQueueLength”]
Update: 30
 |
| Exchange Mailbox IS Client(*) JET Log Records/sec |
Shows the rate that database log records are generated while processing requests for the client. Used to determine current load.
 | Zabbix agent |
perf_counter[“\MSExchangeIS Client Type(*)\Jet Log Records/sec”]
Update: 30
 |
| Exchange ADAccess Domain Controllers(*)\LDAP Search Time |
-
 | Zabbix agent |
perf_counter[“\MSExchange ADAccess Domain Controllers(*)\LDAP Search Time”]
Update: 30s
 |
| Exchange Transport Q - Msgs Submitted/sec |
-
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\Messages Submitted Per Second”]
Update: 30s
 |
| Exchange Middle-Tier Storage(*)\Items Dumpster Deletions/sec |
Shows the rate at which items are deleted from the transport dumpster on this server. Determines the current rate of transport dumpster deletions. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeTransport Dumpster Dumpster Deletes/sec”]
 | Zabbix agent |
perf_counter[“\MSExchange Middle-Tier Storage(*)\Items Dumpster Deletions/sec”]
Update: 30s
 |
| Exchange Mailbox IS Client(*) RPC Operations/sec |
Shows what client protocol is performing an excessive amount of RPC Operations/sec. High IMAP4, POP3, or Outlook Anywhere latency can indicate problems with Client Access servers rather than Mailbox servers. This is especially true when other clients (which includes MAPI) latency is lower in comparison. In some instances, high IMAP latencies could indicate a bottleneck on the Mailbox server in addition to the latencies that the Client Access server is experiencing.
 | Zabbix agent |
perf_counter[“\MSExchangeIS Client Type(*)\RPC Operations/sec”]
Update: 30
 |
| Exchange ADAccess Processes(*)\LDAP Search Time |
-
 | Zabbix agent |
perf_counter[“\MSExchange ADAccess Processes(*)\LDAP Search Time”]
Update: 30s
 |
| Exchange Mailbox IS RPC Operations/sec |
Indicates the current number of RPC operations occurring per second. Should closely correspond to historical baselines. Values much higher than expected indicate that the workload has changed, while values much lower than expected indicate a bottleneck preventing client requests from reaching the server. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeIS RPC Operations/sec”]
 | Zabbix agent |
perf_counter[“\MSExchangeIS Store(*)\RPC Operations/sec”]
Update: 30
 |
| Exchange Search Indexes(*)\Crawler: Mailboxes Remaining |
This counter is used to determine if a full crawl is occurring for any specified database. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchange Search Indices(*) Full Crawl Mode Status”] If CPU resources are high, it’s possible content indexing is occurring for a database or set of databases.
 | Zabbix agent |
perf_counter[“\MSExchange Search Indexes(*)\Crawler: Mailboxes Remaining”]
Update: 30
 |
| Exchange Mailbox Database (Information Store) Database Cache % Hit |
Shows the percentage of database file page requests fulfilled by the database cache without causing a file operation. If this percentage is too low, the database cache size may be too small. Should be over 90% for companies with majority online mode clients. Should be over 99% for companies with majority cached mode clients. If the hit ratio is less than these numbers, the database cache may be insufficient.
 | Zabbix agent |
perf_counter[“\MSExchange Database(Information Store)\Database Cache % Hit”]
Update: 30
 |
| Exchange Mailbox Database I/O Database Writes (Recovery) Average Latency |
Indicates the average time, in ms, to write to the database file. In general, this latency should be less than the MSExchange Database I/O Database Reads (Recovery) Average Latency when battery-backed write caching is utilized.
 | Zabbix agent |
perf_counter[“\MSExchange Database(*)\I/O Database Writes (Recovery) Average Latency”]
Update: 30
 |
| Exchange Mailbox IS Mailbox(*) Search Rate |
Shows the number of search tasks created per second. Should be less than 10 at all times. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeIS Mailbox(*) Search Task Rate”]
 | Zabbix agent |
perf_counter[“\MSExchangeIS Store(*)\Search/sec”]
Update: 30
 |
| Exchange Transport SmtpSend(_total) Messages Sent/sec |
Shows the number of messages sent by the SMTP send connector each second. Determines current load. Compare values to historical baselines.
 | Zabbix agent |
perf_counter[“\MSExchangeTransport SmtpSend(_total)\Messages Sent/sec”]
Update: 30s
 |
| Exchange Transport Q - Submission Q |
This monitor shows the number of messages in the submission queue. The returned value should not exceed 100. If sustained high values are occurring, investigate Active Directory and Mailbox servers for bottlenecks or performance-related issues. MODIFIED_FOR_EX2016-NEW
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\Submission Queue Length”]
Update: 30s
 |
| Exchange Middle-Tier Storage(*)\Items Moved to Dumpster/sec |
Shows the rate at which items are inserted into the transport dumpster on this server. Determines the current rate of transport dumpster inserts. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeTransport Dumpster Dumpster Inserts/sec”]
 | Zabbix agent |
perf_counter[“\MSExchange Middle-Tier Storage(*)\Items Moved to Dumpster/sec.”]
Update: 30s
 |
| Exchange Transport Database ==> Instances(edgetransport/Transport Mail Database) Log Generation Checkpoint Depth |
Represents the amount of work (in count of log files) that needs to be redone or undone to the database files if the process fails.
 | Zabbix agent |
perf_counter[“\MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\Log Generation Checkpoint Depth”]
Update: 30s
 |
| Exchange Transport Q - Msgs Queued For Delivery |
MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeTransport Queues(_total) Aggregate Delivery Queue Length (All Queues)”]
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\Messages Queued For Delivery”]
Update: 30s
 |
| Exchange Mailbox Database ==> Instances(*) Log Generation Checkpoint Depth |
Represents the amount of work in the log file count that needs to be redone or undone to the database files if the process fails. Should be below 500 at all times for the Mailbox server role. A healthy server should indicate between 20 and 30 for each database instance. If checkpoint depth increases continually for a sustained period, this indicates either a long-running transaction, (which will impact the version store), or a bottleneck involving the database disks.
 | Zabbix agent |
perf_counter[“\MSExchange Database ==> Instances(*)\Log Generation Checkpoint Depth”]
Update: 30
 |
| Exchange Mailbox IS Client(*) JET Pages Read/sec |
Shows the rate that database pages are read from disk while processing requests for the client. Used to determine current load.
 | Zabbix agent |
perf_counter[“\MSExchangeIS Client Type(*)\Jet Pages Read/sec”]
Update: 30
 |
| Exchange ADAccess Processes(*)\LDAP Read Time |
-
 | Zabbix agent |
perf_counter[“\MSExchange ADAccess Processes(*)\LDAP Read Time”]
Update: 30s
 |
| Exchange Mailbox Database (Information Store) Database Cache Size (GB) |
Shows the amount of system memory, in megabytes (MB), used by the database cache manager to hold commonly used information from the database files to prevent file operations. Maximum value is RAM-2GB (RAM-3GB for servers with sync replication enabled). This and Database Cache Hit % are useful counters for gauging whether a server’s performance problems might be resolved by adding more physical memory. Use this counter along with store private bytes to determine if there are store memory leaks. If the database cache size seems too small for optimal performance and there is little available memory on the system (check the value of Memory/Available Bytes), adding more memory to the system may increase performance. If there is ample memory on the system and the database cache size isn’t growing beyond a certain point, the database cache size may be capped at an artificially low limit. Increasing this limit may increase performance.
 | Zabbix agent |
perf_counter[“\MSExchange Database(Information Store)\Database Cache Size (MB)”]
Update: 30
 |
| Exchange Transport Q - Msgs Completed Delivery/sec |
Shows the number of messages delivered per second. Determines current load. Compare values to historical baselines.
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\Messages Completed Delivery Per Second”]
Update: 30s
 |
| Exchange Mailbox Store Interface(*) RPC Slow Requests latency average (msec) |
Shows the average latency, in ms, of slow requests. Used for determining the average latencies of RPC slow requests.
 | Zabbix agent |
perf_counter[“\MSExchange Store Interface(*)\RPC Slow Requests latency average (msec)”]
Update: 30
 |
| Exchange ADAccess Domain Controllers(*)\LDAP Read Time |
-
 | Zabbix agent |
perf_counter[“\MSExchange ADAccess Domain Controllers(*)\LDAP Read Time”]
Update: 30s
 |
| Exchange Mailbox Replication(*) CopyQueueLength |
Shows the number of transaction log files waiting to be copied to the passive copy log file folder. A copy isn’t considered complete until it has been checked for corruption. Should be less than 1 at all times for continuous replication.
 | Zabbix agent |
perf_counter[“\MSExchange Replication(*)\CopyQueueLength”]
Update: 30
 |
| Exchange Transport Q - Remote Delivery Q |
MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeTransport Queues(_total) Active Remote Delivery Queue Length”]
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\External Active Remote Delivery Queue Length”]
Update: 30s
 |
There are no triggers in this template.
Converted the Exchange 2010 Performance Monitoring Templates. Removed unsupported items and replaced them with equivalents that could be found. Added some new items and graphs.
matt snead
There are no macros links in this template.
There are no template links in this template.
There are no discovery rules in this template.
| Name | Description | Type | Key and additional info |
|---|---|---|---|
| Exchange Transport Q - Mailbox Delivery Q |
This monitor shows the number of messages in the active mailbox queues. The returned value should be less than 250 at all times
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\Active Mailbox Delivery Queue Length”]
Update: 30s
 |
| ExchangeIS Client Type\RPC Requests |
-
 | Zabbix agent |
perf_counter[“\MSExchangeIS Client Type(*)\RPC Requests”]
Update: 30s
 |
| Exchange OWA User Count |
Shows the number of users connected to the information store. Used to determine current user load. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeIS User Count”]
 | Zabbix agent |
perf_counter[“\MSExchange OWA\Current Users”]
Update: 30
 |
| Exchange Transport Database ==> Instances(edgetransport/Transport Mail Database) I/O Database Writes/sec |
-
 | Zabbix agent |
perf_counter[“\MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\I/O Database Writes/sec”]
Update: 30s
 |
| Exchange Outlook (MapiHttp) User Count |
Shows the number of users connected to the information store. Used to determine current user load. MODIFIED_FOR_EX2016-NEW
 | Zabbix agent |
perf_counter[“\MSExchange MapiHttp Emsmdb\Active User Count”]
Update: 30
 |
| Exchange Mailbox Store Interface(*) RPC Requests Outstanding |
Shows the total number of outstanding RPC requests. Used for determining current load.
 | Zabbix agent |
perf_counter[“\MSExchange Store Interface(*)\RPC Requests Outstanding”]
Update: 30
 |
| ExchangeSearch Indexes(*)\Items Processed/sec |
Shows the average, in ms, of how long it takes to index documents. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchange Search Indices(*) Average Document Indexing Time”]
 | Zabbix agent |
perf_counter[“\MSExchange Search Indexes(*)\Items Processed/sec”]
Update: 30
 |
| Exchange Mailbox Database I/O Log Reads Average Latency |
Indicates the average time, in ms, to read data from a log file. Specific to log replay and database recovery operations. The average value should be below 200 ms. Spikes (maximum values) shouldn’t be higher than 1,000 ms.
 | Zabbix agent |
perf_counter[“\MSExchange Database(*)\I/O Log Reads Average Latency”]
Update: 30
 |
| Exchange RpcClientAccess\RPC Averaged Latency |
Shows the average latency, in ms, of the most recent RPCs to the Information Store service. These RPCs are used to get content for the filter daemon for the specified database. Should coincide with the latencies that Outlook clients are experiencing. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchange Search Indices(*) Average Latency of RPCs Used to Obtain Content”]
 | Zabbix agent |
perf_counter[“\MSExchange RpcClientAccess\RPC Averaged Latency”]
Update: 30
 |
| Exchange Mailbox Database I/O Database Reads (Recovery) Average Latency |
Indicates the average time, in ms, to read from the database file. The average value should be below 200 ms. Spikes (maximum values) shouldn’t be higher than 1,000 ms.
 | Zabbix agent |
perf_counter[“\MSExchange Database(*)\I/O Database Reads (Recovery) Average Latency”]
Update: 30
 |
| ExchangeIS Client Type(*)\RPC Average Latency |
-
 | Zabbix agent |
perf_counter[“\MSExchangeIS Client Type(*)\RPC Average Latency”]
Update: 30s
 |
| Exchange Transport SmtpReceive(_total) Messages Received/sec |
Shows the number of messages received by the SMTP server each second. Determines current load. Compare values to historical baselines.
 | Zabbix agent |
perf_counter[“\MSExchangeTransport SmtpReceive(_total)\Messages Received/sec”]
Update: 30s
 |
| Exchange Transport Q - Msgs Queued for Delivery/sec |
Shows the number of messages queued for delivery per second. Determines current load. Compare values to historical baselines.
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\Messages Queued for Delivery Per Second”]
Update: 30s
 |
| Exchange Mailbox Calendar Attendant Average Calendar Attendant Processing Time |
Shows the average time to process an event in the Calendar Attendant. Should be a low value at all times. High values may indicate a performance bottleneck.
 | Zabbix agent |
perf_counter[“\MSExchange Calendar Attendant\Average Calendar Attendant Processing Time”,30]
Update: 30
 |
| Exchange Mailbox Resource Booking Average Resource Booking Processing Time |
Shows the average time to process an event in the Resource Booking Attendant. Should be a low value at all times. High values may indicate a performance bottleneck.
 | Zabbix agent |
perf_counter[“\MSExchange Resource Booking\Average Resource Booking Processing Time”]
Update: 30
 |
| Exchange Mailbox Database I/O Log Writes Average Latency |
Indicates the average time, in ms, to write a log buffer to the active log file. This counter should be 10 on production servers. If this counter is greater than 10, it’s an indication that the MSExchange Database I/O Database Writes (Attached) Average Latency is too high.
 | Zabbix agent |
perf_counter[“\MSExchange Database(*)\I/O Log Writes Average Latency”]
Update: 30
 |
| Exchange Mailbox IS Client(*) Directory Access: LDAP Searches/sec |
Shows the current rate that LDAP searches occur while processing requests for the client. Used to determine the current LDAP search rate per protocol. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeIS Client(*) Directory Access: LDAP Searches/sec”]
 | Zabbix agent |
perf_counter[“\MSExchangeIS Client Type(*)\Directory Access: LDAP Searches/sec”]
Update: 30
 |
| Exchange ADAccess Domain Controllers(*)\LDAP Read Calls/sec |
Shows the current rate that LDAP reads occur while processing requests for the client. Used to determine the current LDAP read rate per protocol. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeIS Client(*) Directory Access: LDAP Reads/sec”]
 | Zabbix agent |
perf_counter[“\MSExchange ADAccess Domain Controllers(*)\LDAP Read Calls/sec”]
Update: 30
 |
| Exchange RpcClientAccess\RPC Requests |
-
 | Zabbix agent |
perf_counter[“\MSExchange RpcClientAccess\RPC Requests”]
Update: 30s
 |
| Exchange Mailbox Database I/O Database Writes (Attached) Average Latency |
Indicates the average time, in ms, to write to the database file. This counter isn’t a good indicator for client latency because database writes are asynchronous. In general, this latency should be less than the MSExchange Database I/O Database Reads (Attached) Average Latency when battery-backed write caching is utilized.
 | Zabbix agent |
perf_counter[“\MSExchange Database(*)\I/O Database Writes (Attached) Average Latency”]
Update: 30
 |
| Exchange Transport Database ==> Instances(edgetransport/Transport Mail Database) I/O Database Reads/sec |
-
 | Zabbix agent |
perf_counter[“\MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\I/O Database Reads/sec”]
Update: 30s
 |
| Exchange Mailbox Process(MSExchangeMailboxAssistants) % Processor Time |
Shows the amount of processor time being consumed by mailbox assistants. Should be less than 5% of overall CPU capacity.
 | Zabbix agent |
perf_counter[“\Process(MSExchangeMailboxAssistants)\% Processor Time”]
Update: 30
 |
| Exchange RpcClientAccess Active User Count |
Shows the number of users connected to the information store. Used to determine current user load. MODIFIED_FOR_EX2016-NEW
 | Zabbix agent |
perf_counter[“\MSExchange RpcClientAccess\Active User Count”]
Update: 30
 |
| Exchange Transport Database ==> Instances(edgetransport/Transport Mail Database) I/O Log Writes/sec |
-
 | Zabbix agent |
perf_counter[“\MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\I/O Log Writes/sec”]
Update: 30s
 |
| Exchange Transport Database ==> Instances(edgetransport/Transport Mail Database) I/O Log Reads/sec |
-
 | Zabbix agent |
perf_counter[“\MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\I/O Log Reads/sec”]
Update: 30s
 |
| Exchange RPC/HTTP Proxy\Current Number of Unique Users |
Shows the number of unique users currently connected to a back-end server via RPC/HTTP
 | Zabbix agent |
perf_counter[“\RPC/HTTP Proxy\Current Number of Unique Users”]
Update: 30
 |
| Exchange RpcClientAccess Connection Count |
Shows the total number of client connections maintained
 | Zabbix agent |
perf_counter[“\MSExchange RpcClientAccess\Connection Count”]
Update: 30
 |
| Exchange Mailbox Database I/O Database Reads (Attached) Average Latency |
Indicates the average time, in milliseconds (ms), to read from the database file. The average value should be below 20 ms. Spikes (maximum values) shouldn’t be higher than 100 ms.
 | Zabbix agent |
perf_counter[“\MSExchange Database(*)\I/O Database Reads (Attached) Average Latency”]
Update: 30
 |
| Exchange Mailbox Store Interface(*) ROP Requests outstanding |
Shows the total number of outstanding remote operations requests. Used for determining current load.
 | Zabbix agent |
perf_counter[“\MSExchange Store Interface(*)\ROP Requests outstanding”]
Update: 30
 |
| Exchange Submission Successful Submissions Per Second |
Determines current mail submission rate. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchange Mail Submission(*) Successful Submissions Per Second”]
 | Zabbix agent |
perf_counter[“\MSExchange Submission\Successful Submissions Per Second”]
Update: 30
 |
| Exchange Mailbox Database (Information Store) Version buckets allocated |
Shows the total number of version buckets allocated. Should be less than 12,000 at all times. The maximum default version is 16,384. If version buckets reach 70% of maximum, the server is at risk of running out of the version store.
 | Zabbix agent |
perf_counter[“\MSExchange Database(Information Store)\Version buckets allocated”]
Update: 30
 |
| ExchangeIS Store(*)\RPC Average Latency |
-
 | Zabbix agent |
perf_counter[“\MSExchangeIS Store(*)\RPC Average Latency”]
Update: 30s
 |
| Exchange ActiveSync\Current Requests |
Shows the number of HTTP requests waiting to be assigned to a thread
 | Zabbix agent |
perf_counter[“\MSExchange ActiveSync\Current Requests”]
Update: 30
 |
| Exchange Mailbox Store Interface(_Total) RPC Requests outstanding |
Shows the current number of outstanding RPC requests. Should be 0 at all times.
 | Zabbix agent |
perf_counter[“\MSExchange Store Interface(_Total)\RPC Requests outstanding”]
Update: 30
 |
| Exchange Mailbox Database (Information Store) Database Page Fault Stalls/sec |
Shows the rate that database file page requests require of the database cache manager to allocate a new page from the database cache. If this value is nonzero, this indicates that the database isn’t able to flush dirty pages to the database file fast enough to make pages free for new page allocations.
 | Zabbix agent |
perf_counter[“\MSExchange Database(Information Store)\Database Page Fault Stalls/sec”]
Update: 30
 |
| Exchange Mailbox Replication(*) ReplayQueueLength |
Shows the number of transaction log files waiting to be replayed into the passive copy. Indicates the current replay queue length. Higher values cause longer store mount times when a handoff, failover, or activation is performed.
 | Zabbix agent |
perf_counter[“\MSExchange Replication(*)\ReplayQueueLength”]
Update: 30
 |
| Exchange Mailbox IS Client(*) JET Log Records/sec |
Shows the rate that database log records are generated while processing requests for the client. Used to determine current load.
 | Zabbix agent |
perf_counter[“\MSExchangeIS Client Type(*)\Jet Log Records/sec”]
Update: 30
 |
| Exchange ADAccess Domain Controllers(*)\LDAP Search Time |
-
 | Zabbix agent |
perf_counter[“\MSExchange ADAccess Domain Controllers(*)\LDAP Search Time”]
Update: 30s
 |
| Exchange Transport Q - Msgs Submitted/sec |
-
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\Messages Submitted Per Second”]
Update: 30s
 |
| Exchange Middle-Tier Storage(*)\Items Dumpster Deletions/sec |
Shows the rate at which items are deleted from the transport dumpster on this server. Determines the current rate of transport dumpster deletions. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeTransport Dumpster Dumpster Deletes/sec”]
 | Zabbix agent |
perf_counter[“\MSExchange Middle-Tier Storage(*)\Items Dumpster Deletions/sec”]
Update: 30s
 |
| Exchange Mailbox IS Client(*) RPC Operations/sec |
Shows what client protocol is performing an excessive amount of RPC Operations/sec. High IMAP4, POP3, or Outlook Anywhere latency can indicate problems with Client Access servers rather than Mailbox servers. This is especially true when other clients (which includes MAPI) latency is lower in comparison. In some instances, high IMAP latencies could indicate a bottleneck on the Mailbox server in addition to the latencies that the Client Access server is experiencing.
 | Zabbix agent |
perf_counter[“\MSExchangeIS Client Type(*)\RPC Operations/sec”]
Update: 30
 |
| Exchange ADAccess Processes(*)\LDAP Search Time |
-
 | Zabbix agent |
perf_counter[“\MSExchange ADAccess Processes(*)\LDAP Search Time”]
Update: 30s
 |
| Exchange Mailbox IS RPC Operations/sec |
Indicates the current number of RPC operations occurring per second. Should closely correspond to historical baselines. Values much higher than expected indicate that the workload has changed, while values much lower than expected indicate a bottleneck preventing client requests from reaching the server. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeIS RPC Operations/sec”]
 | Zabbix agent |
perf_counter[“\MSExchangeIS Store(*)\RPC Operations/sec”]
Update: 30
 |
| Exchange Search Indexes(*)\Crawler: Mailboxes Remaining |
This counter is used to determine if a full crawl is occurring for any specified database. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchange Search Indices(*) Full Crawl Mode Status”] If CPU resources are high, it’s possible content indexing is occurring for a database or set of databases.
 | Zabbix agent |
perf_counter[“\MSExchange Search Indexes(*)\Crawler: Mailboxes Remaining”]
Update: 30
 |
| Exchange Mailbox Database (Information Store) Database Cache % Hit |
Shows the percentage of database file page requests fulfilled by the database cache without causing a file operation. If this percentage is too low, the database cache size may be too small. Should be over 90% for companies with majority online mode clients. Should be over 99% for companies with majority cached mode clients. If the hit ratio is less than these numbers, the database cache may be insufficient.
 | Zabbix agent |
perf_counter[“\MSExchange Database(Information Store)\Database Cache % Hit”]
Update: 30
 |
| Exchange Mailbox Database I/O Database Writes (Recovery) Average Latency |
Indicates the average time, in ms, to write to the database file. In general, this latency should be less than the MSExchange Database I/O Database Reads (Recovery) Average Latency when battery-backed write caching is utilized.
 | Zabbix agent |
perf_counter[“\MSExchange Database(*)\I/O Database Writes (Recovery) Average Latency”]
Update: 30
 |
| Exchange Mailbox IS Mailbox(*) Search Rate |
Shows the number of search tasks created per second. Should be less than 10 at all times. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeIS Mailbox(*) Search Task Rate”]
 | Zabbix agent |
perf_counter[“\MSExchangeIS Store(*)\Search/sec”]
Update: 30
 |
| Exchange Transport SmtpSend(_total) Messages Sent/sec |
Shows the number of messages sent by the SMTP send connector each second. Determines current load. Compare values to historical baselines.
 | Zabbix agent |
perf_counter[“\MSExchangeTransport SmtpSend(_total)\Messages Sent/sec”]
Update: 30s
 |
| Exchange Transport Q - Submission Q |
This monitor shows the number of messages in the submission queue. The returned value should not exceed 100. If sustained high values are occurring, investigate Active Directory and Mailbox servers for bottlenecks or performance-related issues. MODIFIED_FOR_EX2016-NEW
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\Submission Queue Length”]
Update: 30s
 |
| Exchange Middle-Tier Storage(*)\Items Moved to Dumpster/sec |
Shows the rate at which items are inserted into the transport dumpster on this server. Determines the current rate of transport dumpster inserts. MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeTransport Dumpster Dumpster Inserts/sec”]
 | Zabbix agent |
perf_counter[“\MSExchange Middle-Tier Storage(*)\Items Moved to Dumpster/sec.”]
Update: 30s
 |
| Exchange Transport Database ==> Instances(edgetransport/Transport Mail Database) Log Generation Checkpoint Depth |
Represents the amount of work (in count of log files) that needs to be redone or undone to the database files if the process fails.
 | Zabbix agent |
perf_counter[“\MSExchange Database ==> Instances(edgetransport/Transport Mail Database)\Log Generation Checkpoint Depth”]
Update: 30s
 |
| Exchange Transport Q - Msgs Queued For Delivery |
MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeTransport Queues(_total) Aggregate Delivery Queue Length (All Queues)”]
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\Messages Queued For Delivery”]
Update: 30s
 |
| Exchange Mailbox Database ==> Instances(*) Log Generation Checkpoint Depth |
Represents the amount of work in the log file count that needs to be redone or undone to the database files if the process fails. Should be below 500 at all times for the Mailbox server role. A healthy server should indicate between 20 and 30 for each database instance. If checkpoint depth increases continually for a sustained period, this indicates either a long-running transaction, (which will impact the version store), or a bottleneck involving the database disks.
 | Zabbix agent |
perf_counter[“\MSExchange Database ==> Instances(*)\Log Generation Checkpoint Depth”]
Update: 30
 |
| Exchange Mailbox IS Client(*) JET Pages Read/sec |
Shows the rate that database pages are read from disk while processing requests for the client. Used to determine current load.
 | Zabbix agent |
perf_counter[“\MSExchangeIS Client Type(*)\Jet Pages Read/sec”]
Update: 30
 |
| Exchange ADAccess Processes(*)\LDAP Read Time |
-
 | Zabbix agent |
perf_counter[“\MSExchange ADAccess Processes(*)\LDAP Read Time”]
Update: 30s
 |
| Exchange Mailbox Database (Information Store) Database Cache Size (GB) |
Shows the amount of system memory, in megabytes (MB), used by the database cache manager to hold commonly used information from the database files to prevent file operations. Maximum value is RAM-2GB (RAM-3GB for servers with sync replication enabled). This and Database Cache Hit % are useful counters for gauging whether a server’s performance problems might be resolved by adding more physical memory. Use this counter along with store private bytes to determine if there are store memory leaks. If the database cache size seems too small for optimal performance and there is little available memory on the system (check the value of Memory/Available Bytes), adding more memory to the system may increase performance. If there is ample memory on the system and the database cache size isn’t growing beyond a certain point, the database cache size may be capped at an artificially low limit. Increasing this limit may increase performance.
 | Zabbix agent |
perf_counter[“\MSExchange Database(Information Store)\Database Cache Size (MB)”]
Update: 30
 |
| Exchange Transport Q - Msgs Completed Delivery/sec |
Shows the number of messages delivered per second. Determines current load. Compare values to historical baselines.
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\Messages Completed Delivery Per Second”]
Update: 30s
 |
| Exchange Mailbox Store Interface(*) RPC Slow Requests latency average (msec) |
Shows the average latency, in ms, of slow requests. Used for determining the average latencies of RPC slow requests.
 | Zabbix agent |
perf_counter[“\MSExchange Store Interface(*)\RPC Slow Requests latency average (msec)”]
Update: 30
 |
| Exchange ADAccess Domain Controllers(*)\LDAP Read Time |
-
 | Zabbix agent |
perf_counter[“\MSExchange ADAccess Domain Controllers(*)\LDAP Read Time”]
Update: 30s
 |
| Exchange Mailbox Replication(*) CopyQueueLength |
Shows the number of transaction log files waiting to be copied to the passive copy log file folder. A copy isn’t considered complete until it has been checked for corruption. Should be less than 1 at all times for continuous replication.
 | Zabbix agent |
perf_counter[“\MSExchange Replication(*)\CopyQueueLength”]
Update: 30
 |
| Exchange Transport Q - Remote Delivery Q |
MODIFIED_FOR_EX2016-WAS:perf_counter[” MSExchangeTransport Queues(_total) Active Remote Delivery Queue Length”]
 | Zabbix agent |
perf_counter[“\MSExchangeTransport Queues(_total)\External Active Remote Delivery Queue Length”]
Update: 30s
 |
There are no triggers in this template.


--- layout: custom_detail_page title: "Concert For The Deaf" subtitle: "Winter 2013" comments: false sharing: false footer: true sub_header_title: "Concert for the Deaf" sub_header_date: "Winter 2013" sub_header_image: "/images/projects/concert_for_the_deaf.png" ---
Tile Titans is an HTML5 game that I developed as a side project over the summer of 2013. It is a turn based board game that plays like a mix between chess and tic-tac-toe.
When developing Tile Titans I spent too much time developing non-gameplay features such as a store for purchasing additional tiles and a way to add and challenge friends. I should have only focussed on developing the the core game and a simple matchmaking system and then developed the other features after launching it on Kongregate.
Developed in association with the University of Toronto TETRA society and several of its members. The Concert For The Deaf is an initiative to enable the deaf and hard of hearing to experience music.
We developed a small box that converts audio signals to tactile vibrations. The version 1 prototype was constructed during the LinkedIn Toronto Hackday 2013 and received 3rd place.
We developed a V2 with improved actuators and a more accurate response. The V2 was showcased at the Concert For The Deaf in March 2013.
{% include custom/mini-footer.html %}


Dead Men Don't Wear Plaid (1982) 89m.
It helps if you're both a Steve Martin fan and an old Hollywood movie buff to get the most out of this fastidiously engineered conceit. Martin, who co-wrote with George Gipe and director Carl Reiner, plays a private eye who is approached by slinky Rachel Ward (who brings her own performance to what might have otherwise just been a mock bombshell role) to find her missing father. The first-person narration, black and white photography, art deco titles, and opening score by Miklos Rosza establish within moments that this is going to be spoof on Raymond Chandler crime thrillers, but if you were to enter this film without knowing its central joke, then you'd no doubt be surprised to suddenly see Alan Ladd walking down a corridor while Martin rummages through an office. What DEAD MEN DON'T WEAR PLAID sets out to do - and it makes my head spin to think how many viewing hours must have been spent in order to knit this story together - is to seamlessly insert clips from classic Hollywood pictures into Martin's investigation. Among his many encounters he has telephone conversations with Bogart, shares a train compartment with Cary Grant, and makes a date with Ingrid Bergman. All in all, 18 different films and 18 different Hollywood players (some of them interweaving in and out of the same films) are edited effectively into the story. It's the visual equivalent of David Thomson's one-of-a-kind novel 'Suspects' - fortunately all the stars and their films are listed in the final credits so you don't have to drive yourself crazy trying to figure them out afterwards. The mixture of material makes it hard to determine what era DEAD MEN DON'T WEAR PLAID is supposed to be set in - Martin's reference to the Kinsey Report would place it somewhere in the 50s, which seems a bit out of place considering that all but one of the contributing films were made in the 40s.
I admire the effort that's been made with the matching. Not only the photography, but the sets, props and costumes (by no less than Edith Head!) are also tailored in service of the original footage. For the most part, the clips have also been well selected. The more familiar moments (e.g. Burt Lancaster getting plugged in THE KILLERS, James Cagney performing a casual execution in WHITE HEAT) don't work nearly as well - in fact it's annoying to see the Cagney scene, which was effectively chilling in the original, lifted out of context. Contrast this to Veronica Lake's bit, which is funny even though she says only two words. DEAD MEN DON'T WEAR PLAID was never meant to be a laugh riot - it's more an affectionate pastiche, if anything else - but some of Martin's hardboiled dialogue is hysterical. There's a few in-jokes (the 'You know how to whistle' line from TO HAVE OR HAVE NOT; a reference to Charles Laughton's star turn as THE HUNCHBACK OF NOTRE DAME) but the fun comes mainly from watching Martin delivering offbeat lines to Hollywood stars who are playing their scenes straight. It should be noted that unlike many other comedies that integrate found footage, the tone of Reiner's film is never campy or patronizing to its older source material. Finally, and most importantly, DEAD MEN DON'T WEAR PLAID has one rare distinction: it includes the only scene with an actor in drag that I've actually ever found funny. Poor Fred MacMurray just didn't know what hit him.
<EMAIL_ADDRESS>Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Hero cat saves one-year-old baby from falling down steep flight of stairs
Siamese cat Gatubela was keeping an eye on baby Samuel as he moved across the living room - in fact he jumped to help him as soon as the toddler got close to the stairs
by Chiara FiorilloA hero cat pounced on a baby crawling towards a steep flight of stairs and saved him from falling down.
Footage shot in a living room in Bogotá, Colombia, shows Siamese cat Gatubela leaping into action when one-year-old Samuel León heads towards the stairs.
The baby, wearing a red bodysuit, makes his way past a cot and a rocking chair, while the cat keeps an eye on him.
As Samuel continues to crawl across the living room, Gatubela moves closer to the edge of the sofa.
When the one-year-old gets moves towards the edge of the room, the cat suddenly launches himself from his seat, trying to pull Samuel away from the steep stairs.
The animal wraps its front paws across the toddler's body, forcing him to move backwards.
Later, the pair can be seen playing in the room while the Siamese cat keeps an eye on Samuel.
"The cat has been part of our family practically since birth, we had her here when she was a month, a month and a few days old, and she has become familiar with my children," said the father of the rescued toddler, Jesid Leon.
"She is two months older than my son."
The cat is named Gatubela, which translates to Catwoman, after the DC Comics character.
Diana Lorena Álvarez, the child’s mother, checked the home’s CCTV footage to figure out how her son had got out of his crib, Metro reports.
When she watched the footage, however, she discovered the cat's heroic rescue and realised Gatubela saved her son's life.
She said: "I arrived very early in the morning at my company and my son was still sleeping, for that reason I put him in his crib.
"I was a short distance from him when I suddenly noticed that he had woken up and had left the crib by himself, for this reason I wanted to go back over the recordings so that I could see how he got out of his crib," she added.
"It was at that moment that I discovered that the cat had saved his life. ‘If it had not been for the cat my son would have rolled down the stairs. Watching the footage, I felt really surprised and lucky."
The video, which appeared on Mail Online , was shared on the Facebook page for Fundación Gatos Bogotanos en Adopción, a cat rescue and adoption organisation based in Bogotá.
Astonished viewers have reacted to the video online.
YouTube user gracefulhaley wrote: "This cat deserves a lifetime supply of tuna."
Brandon Hall commented: "For anyone that is confused, the cat is actually the babysitter."
Rockit added: "When you see animals act like this, it shows they are happy in their family environment and want to protect it - that cat should get a LOT of praise and a good feed - and it would appreciate it."


I need help, please can you tell me some "must have" abiltys for characters.
STR, DEX, CON, INT, WIS, CHA. Those are the 'must haves'.
Of course, if you provide a bit of information on exactly what type of character you're talking about (i.e. race, class or classes, and purpose of the character), then perhaps we could even suggest what those abilities should be set at. _________________ Wave upon wave of demented avengers marched cheerfully out of obscurity into the dream...
Quote: Posted 01/15/06 19:29:39 (GMT) -- Cinnabar Din
Of course, if you provide a bit of information on exactly what ... you're talking about
Good boy Cinn, there's hope for you yet. _________________ Some Forum Members believe respect is a right and should be freely given. Myself: I work on a point-buy system, and today my friend you're all out of credit...
i'm talking about red dragon discible, maybe an elf or a human _________________ sorry of my bad english, but i can't do anything cause i'm german
Quote: Posted 01/18/06 16:53:17 (GMT) -- Drake 15
i'm talking about red dragon discible, maybe an elf or a human
Should have guessed that from the name.
The phrase 'blood out of a stone' comes to mind.... _________________ PocketBeetle: Well on the way to earning a PHD in "Applied Idiocy"
Quote: Posted 01/18/06 16:53:17 (GMT) -- Drake 15
i'm talking about red dragon discible, maybe an elf or a human
You will need to take some levels of Bard or Sorcerer to qualify. Look for any of the Ftr/Bard/RDD builds in the character builder forum for ideas.
TM
Go strength based Bard14/RDD10/Plaemaster16 for ultimate tank cheezyness. Great AC, good AB, nice crits, lots of use magic device and a bard/curse song to help even the odds.


It looks like you're trying to log in from a new device or location.
As an added security measure, please enter the 6-digit code we sent to ******@****.com.


Something went wrong!
Something came up while trying to complete the requested offer.
{% else %}The buy request has been completed!
A mail has been sent to both parties notifying them of the completion of the sale.
{% endif %} {% else %} {% if success == False %}Something went wrong!
Something came up while trying to decline the requested offer.
{% else %}The buy request has been declined!
A mail has been sent to both parties notifying them of the cancellation of the sale.
{% endif %} {% endif %} Return to profile page


Students will have access to a deck of events in their area and can RSVP with a click or a flick!
Students face an abundance of technical and design issues when trying to connect with recruiters that shouldn’t exist in the 21st century. Most college’s Career Centers use services like Simplicity, which have outdated, clunky User Interfaces that don’t allow for fluid interaction between student and recruiter.
Students are often forced to make multiple profiles across a variety of services, that don’t communicate with each other, and are very redundant. LinkUpWith.Me integrates existing services, so with one touch, students can link their Facebook, Twitter, and LinkedIn accounts, among other services, with their resumes, and answer industry standard questions, to qualify for as many positions as possible with a minimal input.
Students are also in full control of the image that they present to recruiters, by being able to control what makes themselves as marketable as possible. By using LinkUpWith.Me, instead of having to rely on word of mouth, students can trust that we’ll send exactly what they want us to opportunities that they haven’t even considered. By using our powerful search functions, they will be able to search for opportunities that aren’t traditionally found through just school career centers.
Students can look forward to a social community specifically focused around recruitment, and receive live statistics about expectations and match percentages to find their ideal role for the future. By making the power of big data analytics available to students in a simple, interactive event calendar, students can realistically move forwards into the job market with the path to their goals clearly laid out for them.


This is a paragraph.
This is another paragraph.
This is a paragraph.
This is another paragraph.
This is a paragraph.
This is another paragraph.
If you click on me, I will disappear.
If you double-click on me, I will disappear.
Enter this paragraph.
Leave this paragraph.
This is a paragraph with little content.
This is another small paragraph.


s6-linux-utils
Software
skarnet.org
The s6-ps program
s6-ps shows a list of processes on the system.
Interface
s6-ps [ -H ] [ -w spacing ] [ -W chanfile ] [ -l | -o field,field,... ]
- s6-ps assumes the proc filesystem is mounted on /proc.
It scans /proc for a list of all processes on the system.
- It prints a header line, then information about the processes it has found,
one process per line. Then it exits 0.
- If s6-ps is not allowed to read a field, it will print * (a star) instead
of the field's content. - (a dash) means the field is unapplicable here,
for instance the "tty" field for a process that has no controlling terminal.
Options
- -H : tree. s6-ps will display he process list as a tree,
as ps f does. It will print kernel processes first, then user processes.
By default, the processes are simply ordered by increasing pid number, without
care for the process hierarchy.
- -w spacing : leave at least spacing
space characters between two adjacent fields. Minimum is 1, default is 2,
maximum is 256.
- -W wchanfile : force wchanfile as the
file listing kernel addresses for WCHAN fields. By default, s6-ps tries to use
/proc/kallsyms, /boot/System.map-`uname -r`, and
/boot/System.map, in that order.
- -l : long. Equivalent to
-o user,pid,cpcpu,pmem,vsize,rss,tty,s,start,cttime,args.
- -o fieldlist : list of fields to print.
fieldlist must be a comma-separated list of fields, without spaces.
Fields cannot be duplicated. They will be printed in the given order.
The valid field names are listed below. The default field list is
user,pid,tty,s,start,args.
Fields
The -o option makes it possible to customize s6-ps's output. Here are the
recognized field keywords and the corresponding field they display.
- pid : the process id number.
- comm : the command name as known by the kernel.
- s : the one-character state of the process, then s
if the process is a session leader or + if it is a foreground
process group leader, then N if
the process is niced or < if it is anti-niced. Unlike ps, s6-ps
cannot tell whether a process has locked memory pages or not.
- ppid : the parent process' pid.
- pgrp : the process group number.
- sess : the session leader's pid.
- tty : the name of the process's controlling terminal.
- tpgid : the pid of the foreground process group.
- utime : the time the process spent in user mode.
- stime : the time the process spent in kernel mode.
- cutime : the time spent in user mode by the process and
all its dead children.
- cstime : the time spent in kernel mode by the process and
all its dead children.
- prio : the process' priority as computed by the kernel.
- nice : the process' nice value.
- thcount : the number of threads in the process.
- start : the start time of the process.
- vsize : the virtual memory size of the process.
- rss : the resident set size of the process.
- rsslimit : the maximum rss allowed for the process.
- psr : the number of the CPU the process is running on.
- rtprio : the real-time priority of the process.
- policy : the real-time policy of the process - a symbolic name.
- user : the user the process is running as.
- group : the group the process is running as.
- pmem : the percentage of the available virtual memory the process
is using. Be aware that it is a very rough estimate: determining exactly how much memory
a process is using is a complex task.
- wchan : the name or address of the kernel function where the
proces is sleeping. It is actually very rare that a kernel is configured to properly
export that value, because it incurs a small performance cost.
- args : the command line of the process.
- env : the process environment. s6-ps can normally only print
the environment for processes running as the same user, or if it is run as root.
Be aware that the environment is usually quite large, and will create very long
lines, likely to mess up the display on a standard terminal.
- pcpu : the percentage of CPU used by the process (total cpu time
divided by total running time). It is a mean value and does not reflect current CPU
usage.
- ttime : total CPU time used by the process (user + kernel mode).
- cttime : total CPU time used by the process and all its dead
children (user + kernel mode).
- tstart : the start time of the process as a
TAI64N value.
- cpcpu : the percentage of CPU used by the process and its dead
children (total cpu time
divided by total running time). It is a mean value and does not reflect current CPU
usage.


[t]Contact a candidate[/t]
[t]Your details have already been entered. Do you want extra information about this candidate, or invite him/her for an interview? You can tell us what you wish using the remarks field. After receiving your message we will contact you as soon as possible.[/t]


Developer, Learner
Wait a minute. Wait a minute, User. Uhhh... You are actually using my app!! That's awesome. Alright feel free to contact me if you need anything :) Thanks buddy


?L.
Catasus
Diciembre
2003
DISTRIBUTED
BY
THE
FIELD
COLUMBIAN
MUSEUM.
PLANTS
OF
THE
WEST
INDIES
COLLECTED
BY
H.
a.
VAN
HERMANN.
NEW
YORK
BOTANICAL
GARDEN
PROVINCE
OF
HAVANA
:
Nk&vi/Uo
190
CUBA
01362448
Legend -
Level of confidence that token is an accurately-transcribed word
extremely low
very low
low
undetermined
medium
high
very high


{% extends "withoutnav_template.html" %} {% from "govuk_frontend_jinja/components/button/macro.html" import govukButton %} {% block per_page_title %} Resend security code {% endblock %} {% block maincolumn_content %}
Text messages sometimes take a few minutes to arrive. If you do not receive a security code, Notify can send you a new one.
{{ govukButton({ "element": "a", "text": "Resend security code", "href": url_for('main.check_and_resend_verification_code', next=redirect_url) }) }}
You’ll need to:


| Top |
| GtkAccelGroup * | accel-group | Write |
| gboolean | always-show-image | Read / Write / Construct |
| GtkWidget * | image | Read / Write |
| gboolean | use-stock | Read / Write / Construct |
GObject ╰── GInitiallyUnowned ╰── GtkWidget ╰── GtkContainer ╰── GtkBin ╰── GtkMenuItem ╰── GtkImageMenuItem
GtkImageMenuItem implements AtkImplementorIface, GtkBuildable, GtkActivatable and GtkActionable.
A GtkImageMenuItem is a menu item which has an icon next to the text label.
This is functionally equivalent to:
1 2 3 4 5 6 7 8 9 10 11 |
GtkWidget *box = gtk_box_new (GTK_ORIENTATION_HORIZONTAL, 6); GtkWidget *icon = gtk_image_new_from_icon_name ("folder-music-symbolic", GTK_ICON_SIZE_MENU); GtkWidget *label = gtk_label_new ("Music"); GtkWidget *menu_item = gtk_menu_item_new (); gtk_container_add (GTK_CONTAINER (box), icon); gtk_container_add (GTK_CONTAINER (box), label); gtk_container_add (GTK_CONTAINER (menu_item), box); gtk_widget_show_all (menu_item); |
Note that the user may disable display of menu icons using the “gtk-menu-images” setting, so make sure to still fill in the text label. If you want to ensure that your menu items show an icon you are strongly encouraged to use a GtkMenuItem with a GtkImage instead.
GtkImageMenuItem has been deprecated since GTK+ 3.10. If you want to display an icon in a menu item, you should use GtkMenuItem and pack a GtkBox with a GtkImage and a GtkLabel instead. You should also consider using GtkBuilder and the XML GMenu description for creating menus, by following the GMenu guide. You should consider using icons in menu items only sparingly, and for "objects" (or "nouns") elements only, like bookmarks, files, and links; "actions" (or "verbs") should not have icons.
Furthermore, if you would like to display keyboard accelerator, you must
pack the accel label into the box using gtk_box_pack_end()
and align the
label, otherwise the accelerator will not display correctly. The following
code snippet adds a keyboard accelerator to the menu item, with a key
binding of Ctrl+M:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 |
GtkWidget *box = gtk_box_new (GTK_ORIENTATION_HORIZONTAL, 6); GtkWidget *icon = gtk_image_new_from_icon_name ("folder-music-symbolic", GTK_ICON_SIZE_MENU); GtkWidget *label = gtk_accel_label_new ("Music"); GtkWidget *menu_item = gtk_menu_item_new (); GtkAccelGroup *accel_group = gtk_accel_group_new (); gtk_container_add (GTK_CONTAINER (box), icon); gtk_label_set_use_underline (GTK_LABEL (label), TRUE); gtk_label_set_xalign (GTK_LABEL (label), 0.0); gtk_widget_add_accelerator (menu_item, "activate", accel_group, GDK_KEY_m, GDK_CONTROL_MASK, GTK_ACCEL_VISIBLE); gtk_accel_label_set_accel_widget (GTK_ACCEL_LABEL (label), menu_item); gtk_box_pack_end (GTK_BOX (box), label, TRUE, TRUE, 0); gtk_container_add (GTK_CONTAINER (menu_item), box); gtk_widget_show_all (menu_item); |
void gtk_image_menu_item_set_image (GtkImageMenuItem *image_menu_item
,GtkWidget *image
);
gtk_image_menu_item_set_image
has been deprecated since version 3.10 and should not be used in newly-written code.
Sets the image of image_menu_item
to the given widget.
Note that it depends on the show-menu-images setting whether
the image will be displayed or not.
GtkWidget *
gtk_image_menu_item_get_image (GtkImageMenuItem *image_menu_item
);
gtk_image_menu_item_get_image
has been deprecated since version 3.10 and should not be used in newly-written code.
Gets the widget that is currently set as the image of image_menu_item
.
See gtk_image_menu_item_set_image()
.
GtkWidget *
gtk_image_menu_item_new (void
);
gtk_image_menu_item_new
has been deprecated since version 3.10 and should not be used in newly-written code.
Use gtk_menu_item_new()
instead.
Creates a new GtkImageMenuItem with an empty label.
GtkWidget * gtk_image_menu_item_new_from_stock (const gchar *stock_id
,GtkAccelGroup *accel_group
);
gtk_image_menu_item_new_from_stock
has been deprecated since version 3.10 and should not be used in newly-written code.
Use gtk_menu_item_new_with_mnemonic()
instead.
Creates a new GtkImageMenuItem containing the image and text from a stock item. Some stock ids have preprocessor macros like GTK_STOCK_OK and GTK_STOCK_APPLY.
If you want this menu item to have changeable accelerators, then pass in
NULL
for accel_group. Next call gtk_menu_item_set_accel_path()
with an
appropriate path for the menu item, use gtk_stock_lookup()
to look up the
standard accelerator for the stock item, and if one is found, call
gtk_accel_map_add_entry()
to register it.
stock_id |
the name of the stock item. |
|
accel_group |
the GtkAccelGroup to add the menu items
accelerator to, or |
[allow-none] |
GtkWidget *
gtk_image_menu_item_new_with_label (const gchar *label
);
gtk_image_menu_item_new_with_label
has been deprecated since version 3.10 and should not be used in newly-written code.
Use gtk_menu_item_new_with_label()
instead.
Creates a new GtkImageMenuItem containing a label.
GtkWidget *
gtk_image_menu_item_new_with_mnemonic (const gchar *label
);
gtk_image_menu_item_new_with_mnemonic
has been deprecated since version 3.10 and should not be used in newly-written code.
Use gtk_menu_item_new_with_mnemonic()
instead.
Creates a new GtkImageMenuItem containing a label. The label
will be created using gtk_label_new_with_mnemonic()
, so underscores
in label
indicate the mnemonic for the menu item.
gboolean
gtk_image_menu_item_get_use_stock (GtkImageMenuItem *image_menu_item
);
gtk_image_menu_item_get_use_stock
has been deprecated since version 3.10 and should not be used in newly-written code.
Checks whether the label set in the menuitem is used as a stock id to select the stock item for the item.
TRUE
if the label set in the menuitem is used as a
stock id to select the stock item for the item
Since: 2.16
void gtk_image_menu_item_set_use_stock (GtkImageMenuItem *image_menu_item
,gboolean use_stock
);
gtk_image_menu_item_set_use_stock
has been deprecated since version 3.10 and should not be used in newly-written code.
If TRUE
, the label set in the menuitem is used as a
stock id to select the stock item for the item.
Since: 2.16
gboolean
gtk_image_menu_item_get_always_show_image
(GtkImageMenuItem *image_menu_item
);
gtk_image_menu_item_get_always_show_image
has been deprecated since version 3.10 and should not be used in newly-written code.
Returns whether the menu item will ignore the “gtk-menu-images” setting and always show the image, if available.
Since: 2.16
void gtk_image_menu_item_set_always_show_image (GtkImageMenuItem *image_menu_item
,gboolean always_show
);
gtk_image_menu_item_set_always_show_image
has been deprecated since version 3.10 and should not be used in newly-written code.
If TRUE
, the menu item will ignore the “gtk-menu-images”
setting and always show the image, if available.
Use this property if the menuitem would be useless or hard to use without the image.
Since: 2.16
void gtk_image_menu_item_set_accel_group (GtkImageMenuItem *image_menu_item
,GtkAccelGroup *accel_group
);
gtk_image_menu_item_set_accel_group
has been deprecated since version 3.10 and should not be used in newly-written code.
Specifies an accel_group
to add the menu items accelerator to
(this only applies to stock items so a stock item must already
be set, make sure to call gtk_image_menu_item_set_use_stock()
and gtk_menu_item_set_label()
with a valid stock item first).
If you want this menu item to have changeable accelerators then
you shouldnt need this (see gtk_image_menu_item_new_from_stock()
).
Since: 2.16
“accel-group”
property“accel-group” GtkAccelGroup *
The Accel Group to use for stock accelerator keys
GtkImageMenuItem:accel-group
has been deprecated since version 3.10 and should not be used in newly-written code.
Use gtk_widget_add_accelerator()
instead
Flags: Write
Since: 2.16
“always-show-image”
property“always-show-image” gboolean
If TRUE
, the menu item will always show the image, if available.
Use this property only if the menuitem would be useless or hard to use without the image.
GtkImageMenuItem:always-show-image
has been deprecated since version 3.10 and should not be used in newly-written code.
Use a GtkMenuItem containing a GtkBox with a GtkAccelLabel and a GtkImage instead
Flags: Read / Write / Construct
Default value: FALSE
Since: 2.16
“image”
property“image” GtkWidget *
Child widget to appear next to the menu text.
GtkImageMenuItem:image
has been deprecated since version 3.10 and should not be used in newly-written code.
Use a GtkMenuItem containing a GtkBox with a GtkAccelLabel and a GtkImage instead
Flags: Read / Write
“use-stock”
property“use-stock” gboolean
If TRUE
, the label set in the menuitem is used as a
stock id to select the stock item for the item.
GtkImageMenuItem:use-stock
has been deprecated since version 3.10 and should not be used in newly-written code.
Use a named icon from the GtkIconTheme instead
Flags: Read / Write / Construct
Default value: FALSE
Since: 2.16


Whitepaper
Features
Cases
Dapps
Mission
Market
Roadmap
Rating
Product
Miiix Rewards
Partners
Team
Advisors
Competitors
Meet Us At
Reviews
FAQ
Contacts


{{ partial "header.html" . }} 404 Not Found Sorry, but we couldn't find the page you're looking for. Please head back home. {{ partial "footer.html" . }}
Sorry, but we couldn't find the page you're looking for.
Please head back home.


|
Closest String Problem with ACO
AntColonyOptimizationalgorithmsfortheClosestStringProblem
|
class MaxMin: Max Min ant colony optimization metaheuristic for the Closest String Problem More...
#include <MaxMin.hpp>
Public Member Functions | |
| MaxMin (Instance &instance) | |
| costructor More... | |
| MaxMin (Instance &instance, Utils::Parameters ¶meters) | |
| costructor More... | |
| virtual void | solve (Solution &best) |
| solve the CSP problem More... | |
| Public Member Functions inherited from AntColony | |
| AntColony (Instance &instance) | |
| constructor More... | |
| AntColony (Instance &instance, Utils::Parameters ¶meters) | |
| constructor More... | |
| virtual void | displayPheromones () |
| display the pheromone matrix of the algorithm | |
| void | displayProbas () |
| display the probabilities matrix of the algorithm | |
| virtual | ~AntColony () |
| default destructor | |
Protected Member Functions | |
| virtual void | initPheromones () |
| init the pheromone matrix | |
| virtual void | depositPheromones (Solution &ant) |
| deposit pheromones More... | |
| virtual void | updateBounds (Solution &best) |
| update pheromone bounds bestAnt the best solution so far | |
| virtual void | checkBounds () |
| check if the pheromones satisfy the bounds | |
| Protected Member Functions inherited from AntColony | |
| virtual void | buildSolution (Solution &solution) |
| build a new solution based on the pheromones and the heuristic information More... | |
| virtual void | computeProbas () |
| compute the probabilites for each decision of the artifical ants | |
| int | randomChoice (int pos) |
| make a random choice based on _probas for a character in a given position More... | |
| void | evaporatePheromone () |
| evaporate the artificial pheromones | |
Additional Inherited Members | |
| Protected Attributes inherited from AntColony | |
| Instance & | _instance |
| std::vector< std::vector< double > > | _pheromones |
| std::vector< std::vector< double > > | _probas |
| double | _alpha |
| double | _beta |
| double | _rho |
| int | _nAnts |
| int | _nItMax |
| double | _initPheromone |
| std::vector< Solution > | _population |
class MaxMin: Max Min ant colony optimization metaheuristic for the Closest String Problem
| MaxMin::MaxMin | ( | Instance & | instance | ) |
costructor
| instance | instance of the Closest String Problem |
| MaxMin::MaxMin | ( | Instance & | instance, |
| Utils::Parameters & | parameters | ||
| ) |
costructor
| instance | instance of the Closest String Problem |
| parameters | parameters of the algorithm |
|
protectedvirtual |
deposit pheromones
| ant | the ant which deposits the pheromones |
Reimplemented from AntColony.
|
virtual |


class notes, text books, reference material
ClassesAtAmrita
Help at your service
Get notes
Get text book
Get PDF
Get code samples
Help us
Meet AUMS


On an emonPi I am editing in the EmonHub Config Editor to set up an additional node. Below is what I typed into the emonhub.conf area but this did not work.
[[11]]
nodename = emonGLCD
firmware = HomeEnergyMonitor.ino
hardware = emonglcd
[[[rx]]]
names = temp
datacode = h
scale = 0.01
units = F
Looking at the Nodes page I see this (with the word "temp" split up):￼
If I add two names and two units in the emonhub.conf area, then the Nodes page looks correct.
[[11]]
nodename = emonGLCD
firmware = HomeEnergyMonitor.ino
hardware = emonglcd
[[[rx]]]
names = temp,junk
datacode = h
scale = 0.01
units = F,C￼
Is this something I am configuring incorrectly or an issue with the emonhub within the emonPi?
Jon
Re: Issue creating new Node on emonPi
Hi Jon
What is most likely happening there is the emonHub code is trying to split the list of "names", but since there is only one item it is splitting the string. This is incorrect behavior from emonhub that you have side stepped by defining a second value.
I would need to look closer at how the names and units are parsed in the "emon-pi" variant of emonhub to be sure, but you may be able to make emonhub comprehend a "list of one names" by adding just a comma rather than a second "names".
Does your sketch have just one value? I would of expected a different error if you defined a second value when there is only one, but that seems to have slipped through.
Also the use of datacode rather than datacodes and scale rather than scales is open ended, the singular term datacode (or scale) denotes all the variables of an undefined quantity are the same datacode (or scale), where as the plural term denotes each variable's datacode (or scale) is explicitly defined and therefore the number of values is implied and must match (eg 5 datacodes for 4 values will fail) emonhub's use of the plural term becomes a little odd when there is only one value.(thankfully a rare occurrence) "data code = h" is undefined number of ints where as "datacodes = h" would actually mean explicitly one integer value.
There is no problem with using the singular datacode or scale, but I thought I would explain the singular/plural is not directly linked to the number of values but to "single global" or "one per value".
This intended behavior may not be consistent with the names or units as they were not written in at the same time as the original datacode(s) and scale(s). I will take a closer look to see how it's been done when I can though. I the meantime I hope this (rather confusing?) explanation helps you find an acceptable work around.
Paul
Re: Issue creating new Node on emonPi
Hi Paul,
Thank you for your quick reply! Yes, there is only one value from the emonGLCD (the temp). I had actually started out with "list of one names" by adding the comma.
[[11]]
nodename = emonGLCD
firmware = HomeEnergyMonitor.ino
hardware = emonglcd
[[[rx]]]
names = temp,
datacode = h
scale = 0.01
units = F,
That worked of for receiving the data from the emonGLCD, but in the Nodes page showed a blank name for RX ID 2. (See attached image).
And I believe I understand the datacode(s) and scale(s). I'll know for sure when I add a multi-value Node.
If code does change, please let me know if there is something I can test or assist with. I am happy to help!
Jon


Currently the game looks pretty easy(in design, not game itself), if given more time and resource, I think I can optimize the game in following aspects.
Adding a user id system.The game now keeps everything inside the memory, it does not interact with database system. Adding a database in the back of the game can ensure players keeping their scores, maintaining user identity and optimize the experience of the players. Thought this requires a lot of work, especially we have to integrate C++ with MySQL or MongoDB for backend support, but if we want the game to expand or attract more people this function definitely matters.
Adding more language.Currently the game only contains two languages, English and Italian, which is not enough. More language can attract more users.
Design more patterns.Like special effect, after 10 bumps the ball turns into a bigger ball, or turn into a bomb that blows up an area of bricks. Different effects can make the game more playable, avoid players getting bored.