The Events tab displays metrics collected related to the Events API. The Integrity Events API uses Vector to stream DDI events to external applications. For information on configuring the Events API, refer to Events API.
To view events metrics:
- Select the Overview tab in the sidebar, then select Dashboards.
- Select the name of the Address Manager server that you would like to retrieve events metrics for.
- Select the Events tab.
From this tab, the following graphs display metrics about Address Manager:
- Events received—displays the number of events Vector has received from the Events API and accepted for processing since it started. The polling of totals is executed every minute.
- Events sent—displays the number of events Vector has successfully sent to its external destination since Vector started. For the event to count, it must have passed through buffering/retries and been acknowledged by the destination. For HTTP / Elasticsearch sinks, the count increments when the HTTP request succeeds and the remote system responds with success. For Kafka sinks, the count increments when the broker acknowledges the message.
- Errors—displays the total number of errors Vector has encountered while
attempting to send events to its destination. This typically includes:
- Delivery failures: HTTP 4xx / 5xx responses depending on sink behaviour, connection timeouts, TLS errors, DNS resolution failures, and authentication failures
- Retry-triggering failures: If a send attempt fails and Vector retries it, that failure usually increments this counter.
- Batch-level failures: A failed batch submission increments the error counter.
- Retries—displays the difference between the total number of outbound HTTP requests Vector has sent and the total number of HTTP responses received by Vector’s internal HTTP client.
- Processing time—displays the cumulative total of HTTP round-trip time (RTT), in seconds, for all completed outbound HTTP requests made by Vector. RTT (round-trip time) is the time between when Vector sends an HTTP request and when it receives the full HTTP response, therefore this includes network latency, TLS handshake time, server processing time, and response transfer time.
- Buffered events—displays the total number of events that have been successfully removed from Vector's buffer and handed off to the sink for delivery.
- Buffer size—displays the current number of bytes stored in Vector's buffer. Vector uses a buffer to temporarily store events, handle backpressure, enable retries, and batch events before sending. The buffer size indicates how much data (in bytes) is currently sitting in that buffer waiting to be processed or sent.
- Data sent—displays the total number of bytes successfully sent from Vector to its external destination since Vector started.