Azure Data Explorer
Dynatrace ingests metrics from Azure Metrics API for Azure Data Explorer. 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.203+
- Environment ActiveGate version 1.195+
Enable monitoring
To enable monitoring for this service, 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 | Unit | Dimensions | Recommended |
---|---|---|---|---|
BatchBlobCount | The number of data sources in an aggregated batch for ingestion | Count | Database | ✔️ |
BatchDuration | The duration of the aggregation phase in the ingestion flow | Second | Database | |
BatchSize | The uncompressed, expected data size in an aggregated batch for ingestion | Byte | Database | ✔️ |
BatchesProcessed | The number of batches aggregated for ingestion | Count | Database, SealReason | |
CPU | The CPU utilization level | Percent | ✔️ | |
CacheUtilization | The utilization level in the cluster scope | Percent | ✔️ | |
ContinuousExportMaxLatenessMinutes | The lateness (in minutes) reported by the continuous export jobs in the cluster | Count | ✔️ | |
ContinuousExportNumOfRecordsExported | The number of records exported, fired for every storage artifact written during the export operation | Count | ✔️ | |
ContinuousExportPendingCount | The number of pending continuous export jobs ready for execution | Count | ✔️ | |
ContinuousExportResult | Indicates whether continuous export succeeded or failed | Count | ContinuousExportName, Result, Database | ✔️ |
EventsProcessedForEventHubs | The number of events processed by the cluster when ingesting from Event/IoT Hub | Count | EventStatus | |
ExportUtilization | The export utilization | Percent | ✔️ | |
IngestionLatencyInSeconds | The ingestion time from the source (for example, if message is in EventHub) to the cluster in seconds | Second | ✔️ | |
IngestionResult | The number of ingestion operations | Count | IngestionResultDetails | |
IngestionUtilization | The ratio of used ingestion slots in the cluster | Percent | ✔️ | |
IngestionVolumeInMB | The overall volume of ingested data to the cluster (in MB) | MegaByte | ✔️ | |
InstanceCount | The total instance count | Count | ||
KeepAlive | Sanity check, indicating how the cluster responds to queries | Count | ✔️ | |
QueryDuration | The queries duration in seconds | MilliSecond | QueryStatus | ✔️ |
SteamingIngestRequestRate | The streaming ingest request rate (requests per second) | Count | ||
StreamingIngestDataRate | The streaming ingest data rate (MB per second) | Count | ||
StreamingIngestDuration | The streaming ingest duration in milliseconds | MilliSecond | ||
StreamingIngestResults | The streaming ingest result | Count | Result | |
TotalNumberOfConcurrentQueries | The total number of concurrent queries | Count | ✔️ | |
TotalNumberOfExtents | The total number of data extents | Count | ✔️ | |
TotalNumberOfThrottledCommands | The total number of throttled commands | Count | CommandType | |
TotalNumberOfThrottledQueries | The total number of throttled queries | Count | ✔️ |