Azure Event Hubs (Clusters)
Dynatrace ingests metrics from Azure Metrics API for Azure Event Hubs (Clusters). You can view metrics for each service instance, split metrics into multiple dimensions, and create custom charts that you can pin to your dashboards.
Prerequisites
- Dynatrace version 1.199+
- Environment ActiveGate version 1.195+
Enable monitoring
To enable monitoring for Azure Event Hubs, you first need to set up integration with Azure Monitor.
Add the service to monitoring
In order to view the service metrics, you must add the service to monitoring in your Dynatrace environment.
Monitor resources based on tags
You can choose to monitor resources based on existing Azure tags, as Dynatrace automatically imports them from service instances.
To monitor resources based on tags
- Go to Settings > Cloud and virtualization > Azure and select the Azure instance.
- For Resource monitoring method, select Monitor resources based on tags.
- Enter the Key and Value.
- Select Save.
Note: To import the Azure tags automatically into Dynatrace, enable Capture Azure tags automatically.
Configure service metrics
Once you add a service, Dynatrace starts automatically collecting a suite of metrics for this particular service. These are recommended metrics.
Recommended metrics:
- Are enabled by default
- Can't be disabled
- Can have recommended dimensions (enabled by default, can't be disabled)
- Can have optional dimensions (disabled by default, can be enabled).
Apart from the recommended metrics, most services have the possibility of enabling optional metrics.
Optional metrics:
- Can be added and configured manually
View service metrics
Once you add the service to monitoring, you can view the service metrics in your Dynatrace environment either on your dashboard page or on the custom device overview page.
Import preset dashboards
Dynatrace provides preset Azure dashboards that you can import from GitHub to your environment's Dashboards page.
Note: To save a preset dashboard locally, create a new JSON file on your local machine and copy-paste the content of the JSON file from GitHub into the new file.
Once you save a preset dashboard locally, there are two ways to import it.
Available metrics
Name | Description | Dimensions | Unit | Recommended |
---|---|---|---|---|
ActiveConnections | Total active connections for Microsoft.EventHub | Count | ||
AvailableMemory | Available memory for the Event Hub Cluster as a percentage of total memory | Role | Percent | ✔️ |
CPU | CPU utilization for the Event Hub Cluster as a percentage | Role | Percent | ✔️ |
CaptureBacklog | Captured backlog for Microsoft.EventHub | Count | ||
CapturedBytes | Captured bytes for Microsoft.EventHub | Byte | ||
CapturedMessages | Captured messages for Microsoft.EventHub | Count | ||
ConnectionsClosed | Connections closed for Microsoft.EventHub | Count | ||
ConnectionsOpened | Connections opened for Microsoft.EventHub | Count | ||
IncomingBytes | Incoming bytes for Microsoft.EventHub | Byte | ✔️ | |
IncomingMessages | Incoming messages for Microsoft.EventHub | Count | ✔️ | |
IncomingRequests | Incoming requests for Microsoft.EventHub | Count | ✔️ | |
OutgoingBytes | Outgoing bytes for Microsoft.EventHub | Byte | ✔️ | |
OutgoingMessages | Outgoing messages for Microsoft.EventHub | Count | ✔️ | |
QuotaExceededErrors | Quota exceeded errors for Microsoft.EventHub | Count | ✔️ | |
ServerErrors | Server errors for Microsoft.EventHub. | Count | ✔️ | |
Size | Size of an EventHub in Bytes. | Role | Byte | |
SuccessfulRequests | Successful requests for Microsoft.EventHub | Count | ||
ThrottledRequests | Throttled requests for Microsoft.EventHub | Count | ✔️ | |
UserErrors | User errors for Microsoft.EventHub | Count | ✔️ |