Azure Integration Service Environment
Dynatrace ingests metrics for multiple preselected namespaces, including Azure Integration Service Environment. 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.200+
- Environment ActiveGate version 1.198+
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.
Note: Azure Integration Service Environment can be connected with Azure Logic Apps. For more information, see Connect to Azure virtual networks from Azure Logic Apps by using an integration service environment.
Dashboard for Azure Integration Service Environment with Azure Logic Apps
Available metrics
Name | Description | Unit | Recommended |
---|---|---|---|
ActionLatency | Latency of completed workflow actions | Second | ✔️ |
ActionSuccessLatency | Latency of succeeded workflow actions | Second | ✔️ |
ActionThrottledEvents | Number of workflow action throttled events | Count | ✔️ |
ActionsCompleted | Number of workflow actions completed | Count | ✔️ |
ActionsFailed | Number of workflow actions failed | Count | ✔️ |
ActionsSkipped | Number of workflow actions skipped | Count | ✔️ |
ActionsStarted | Number of workflow actions started | Count | ✔️ |
ActionsSucceeded | Number of workflow actions succeeded | Count | ✔️ |
IntegrationServiceEnvironmentWorkflowMemoryUsage | Workflow memory usage for integration service environment | Percent | ✔️ |
IntegrationServiceEnvironmentWorkflowProcessorUsage | Workflow processor usage for integration service environment | Percent | ✔️ |
RunFailurePercentage | Percentage of workflow runs failed | Percent | |
RunLatency | Latency of completed workflow runs | Second | ✔️ |
RunStartThrottledEvents | Number of workflow run start throttled events | Count | ✔️ |
RunSuccessLatency | Latency of succeeded workflow runs | Second | ✔️ |
RunThrottledEvents | Number of workflow action or trigger throttled events | Count | ✔️ |
RunsCancelled | Number of workflow runs cancelled | Count | ✔️ |
RunsCompleted | Number of workflow runs completed | Count | ✔️ |
RunsFailed | Number of workflow runs failed | Count | ✔️ |
RunsStarted | Number of workflow runs started | Count | ✔️ |
RunsSucceeded | Number of workflow runs succeeded | Count | ✔️ |
TriggerFireLatency | Latency of fired workflow triggers | Second | ✔️ |
TriggerLatency | Latency of completed workflow triggers | Second | ✔️ |
TriggerSuccessLatency | Latency of succeeded workflow triggers | Second | ✔️ |
TriggerThrottledEvents | Number of workflow trigger throttled events | Count | ✔️ |
TriggersCompleted | Number of workflow triggers completed | Count | ✔️ |
TriggersFailed | Number of workflow triggers failed | Count | ✔️ |
TriggersFired | Number of workflow triggers fired | Count | ✔️ |
TriggersSkipped | Number of workflow triggers skipped | Count | ✔️ |
TriggersStarted | Number of workflow triggers started | Count | ✔️ |
TriggersSucceeded | Number of workflow triggers succeeded | Count | ✔️ |