NS$instance_name: Generator Object
The NS$instance_name: Generator object provides counters for monitoring generator threads of a Notification Services instance. Each generator thread processes notifications for one application.
The generator counters monitor one or all generator threads on the local server. If the engine is running on the local server but does not host the generator, the counters are available but do not return data.
| Counter | Description | Use |
|---|---|---|
Notifications Generated Per Second |
Number of notifications created per second. |
Use to analyze the volume of notifications produced by the generator over time. |
Quanta Behind |
Number of quanta that the generator is falling behind. |
Use to determine whether the generator can keep up with the current workload. This could be due to other processes running on the database server, the need to improve performance on the database server, or possibly the need to improve performance on the server that runs the generator component. |
Quanta Failed |
Number of failed quanta since the generator started. Quantum failure indicates that at least one of the rules in the quantum failed. Because rules fire in parallel, multiple rules can fail within a single quantum. |
Use to determine whether rule firings are failing. One possible cause of a firing failure is a rule-firing timeout. This could indicate problems connecting to the database server or with executing queries. |
Quanta Processed |
Number of quanta processed since the generator started. If the generator is trying to catch up, this number can be higher than you might typically expect. |
Use to determine how many quanta have been processed. |
Rule Firing Failures |
Number of failed rule firings since the generator started. |
Use to further analyze the Quanta Failed counter. The Rule Firing Failures counter shows you how many rule firings failed, which you can use to troubleshoot rule problems and connection problems. |
Rule Firings |
Number of rule firings since the generator started. |
Compare this value to the Rule Firing Failures counter to see the ratio of successfully fired rules to failed rules. |
Skipped Chronicle Rule Firings |
Number of quanta skipped for chronicle rule firings since the generator started. |
Use to determine whether chronicle rules have been skipped, which can indicate stale chronicle data or a problem with chronicle rules. |
Skipped Quanta |
Number of quanta the generator skipped since the generator started. |
Use to determine whether generation has fallen behind far enough to skip rule firings. To tune your applications, you might need to adjust the QuantumDuration and ChronicleQuantumLimit elements in the application definition file (ADF). |
Skipped Subscription Rule Firings |
Number of quanta skipped for subscription rule firings. |
Use to determine whether subscription rules are being skipped, which indicates skipped notifications. To tune your applications, you might need to adjust the QuantumDuration and SubscriptionQuantumLimit elements in the ADF. |
After selecting a counter, select an instance. You can select All instances, which returns values for all generator threads on the local server, or you can select one of the generator thread instances; generator thread instance names are the same as application names, such as stock.
Important
Performance counter instances are available only when the instance is running.
See Also
Concepts
Notification Services Performance Objects
Specifying Application Execution Settings