-
Notifications
You must be signed in to change notification settings - Fork 1
Performance Monitoring
Ryan Mahoney edited this page Jul 26, 2018
·
2 revisions
A notification must go through a few stages before it can be received by a subscriber. The time of each stage is measured on a per-notification basis.
The time spent in the process of comparing subscriptions to alerts (currently includes sleeping period between alert-processing runs and the time of parsing the alert feed)
The time spent waiting in a queue to be sent after a match has occurred.
Before pushing a notification to be sent as an email or an SMS, the following fields are logged:
| Field | Description |
|---|---|
| alert_age_in_seconds | Age in seconds of an alert until the time of notification sending |
| seconds_until_match | Age in seconds that a notification spent until being matched |
| seconds_in_sending_queue | Age in seconds that notification spent waiting in the sending queue |
| seconds_processing | Combined age of matching and waiting in sending queue |
| time_optimal | The absolute ideal time of sending |
| time_matched | The actual time of matching |
| time_sent | The actual time of sending |
After an entire round of matching a batch of alerts to all subscribers occurs, the total time spent in matching is logged.