|
Measures reported by AzrEvtHubTest
Azure Event Hubs is a big data streaming platform and event ingestion service. It can receive and process millions of events per second.
Typically, Event Hubs represent the “front door” for an event pipeline, often called an event ingestor in solution architectures. An event ingestor is a component or service that sits between event publishers(a.k.a event producers) and event consumers (a.k.a event receivers) to decouple the production of an event stream from the consumption of those events.
Data sent to an event hub can also be transformed and stored using any real-time analytics provider or batching/storage adapters.
The advanced analytics that can be derived from the event hubs play a crucial role in anomaly detection, application logging, transaction processing, data archiving, and more. In such scenarios naturally, errors in the event hub or the failure of the hub to respond to requests from clients/consumers, can result in serious consequences - eg., delays in problem detection, lapses in application logging, etc.
To avoid this, it is important that administrators constantly monitor the status of the Event hubs, continuously measure their ability to process requests, and promptly capture and resolve request processing bottlenecks, before they disrupt the critical services that these hubs provide. This is exactly what the AzrEvtHubTest does!
This test auto-discovers the Event hubs created for the target subscription. For each Event hub, the test then reports the hub status, so that hubs in an abnormal state can be quickly identified. Additionally, the test also promptly alerts administrators to errors impacting a hub's operations, and pinpoints what could be causing those errors - a problematic client? or a faulty server? Furthermore, the test tracks requests received by each hub from clients, observes how every hub processes those requests, and raises an alarm if any hub fails to service the requests. This way, the test enables administrators to rapidly capture and fix hub-related anomalies, so that every hub provides uninterrupted event streaming services.
Outputs of the test : One set of results for each Event Hub configured for every resource group in the target Azure Subscription
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| Status |
Indicates the current status of this Event hub. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
| Measure Value |
Numeric Value |
| Creating |
1 |
| Created |
2 |
| Activating |
3 |
| Enabling |
4 |
| Active |
5 |
| Disabling |
6 |
| Disabled |
7 |
| Soft Deleting |
8 |
| Soft Deleted |
9 |
| Removing |
10 |
| Removed |
11 |
| Failed |
12 |
| Unknown |
0 |
Note:
By default, this measure reports the Measure Values listed in the table above to indicate the current status of the the Event hub. The graph of this measure however, represents the status of a server using the numeric equivalents only.
Use the detailed diagnosis of this measure to know the location of the event hub, when it was created, the pricing tier, and throughput units assigned to the hub. |
| Prvsng_status |
Indicates the provisioning status of this Event hub. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
| Measure Value |
Numeric Value |
| Succeeded |
1 |
| Updating |
2 |
| Error |
3 |
| Unknown |
0 |
Note:
By default, this measure reports the Measure Values listed in the table above to indicate the current provisioning status of the Event hub. In the graph of this measure however, the same is represented using the numeric equivalents only. |
| Incmng_snd_req |
Indicates the number of requests made to this Event Hub. |
Number |
|
| Succ_req |
Indicates the number of successful requests made to this Event hub. |
Number |
Ideally, the value of this measure should be equal to or close to the value of the Incoming send requests measure. On the other hand, if the value of this measure is much lower than the value of the Incoming send requests measure, it implies that many requests failed. |
| Faild_req |
Indicates the number of requests to this Event hub that failed. |
Number |
Ideally, the value of this measure should be 0 or very low. |
| Srvr_busy_err |
Indicates the number of ServerBusy errors that this Event hub encountered. |
Number |
A ServerBusyException is thrown when a server is busy. Callers should wait a while and retry the operation.
Ideally, the value of this measure should be 0. |
| Intrnl_srvr_err |
Indicates the number of internal server errors sent back to the sender or receiver while performing run-time operations. |
Number |
InternalServerErrors occur due to either service-side or network problems.
Ideally, the value of this measure should be 0. |
| Misc_err |
Indicates the number of OtherErrors. |
Number |
OtherErrors are types of errors are due to faults at the sender or receiver side, such as providing bad parameters, not enough credentials, or trying to perform an operation on a nonexistent entity.
Ideally, the value of this measure should be 0. |
| Incmng_msg |
Indicates the number of events or messages sent this Event hub. |
Number |
|
| Outgng_msg |
Indicates the number of events or messages received from this Event hub. |
Number |
|
| Incmng_byts |
Indicates the incoming bytes for this Event hub. |
MB |
|
| Outgng_byts |
Indicates the outgoing bytes for this Event hub. |
MB |
|
| Archv_bklog_msg |
Indicates the number of archive messages in the backlog of this Event hub. |
Number |
|
| Archv_msg |
Indicates the number of archive messages in this Event hub. |
Number |
|
| Archv_msg_thrputl |
Indciates the archive message throughput for the Event hub. |
MB |
|
|