Azure Integration Service Environment monitoring

  • How-to guide
  • 3-min read
  • Published Aug 19, 2020

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 learn how to enable service monitoring, see Enable service monitoring.

View service metrics

You can view the service metrics in your Dynatrace environment either on the custom device overview page or on your Dashboards page.

View metrics on the custom device overview page

To access the custom device overview page

  1. Go to Technologies & Processes Classic.
  2. Filter by service name and select the relevant custom device group.
  3. Once you select the custom device group, you're on the custom device group overview page.
  4. The custom device group overview page lists all instances (custom devices) belonging to the group. Select an instance to view the custom device overview page.

View metrics on your dashboard

Once you add a service to monitoring, a preset dashboard for the respective service containing all recommended metrics is automatically created on your Dashboards page. You can look for specific dashboards by filtering by Preset and then by Name.

For existing monitored services, you might need to resave your credentials for the preset dashboard to appear on the Dashboards page. To resave your credentials, go to Settings > Cloud and virtualization > Azure, select the desired Azure instance, then select Save.

You can't make changes on a preset dashboard directly, but you can clone and edit it. To clone a dashboard, open the browse menu () and select Clone.
To remove a dashboard from the dashboards list, you can hide it. To hide a dashboard, open the browse menu () and select Hide.

Hiding a dashboard doesn't affect other users.

Clone hide azure

Azure Integration Service Environment

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

Azure Integration Service Environment + Logic Apps

Available metrics

NameDescriptionUnitRecommended
ActionLatencyLatency of completed workflow actionsSecondApplicable
ActionSuccessLatencyLatency of succeeded workflow actionsSecondApplicable
ActionThrottledEventsNumber of workflow action throttled eventsCountApplicable
ActionsCompletedNumber of workflow actions completedCountApplicable
ActionsFailedNumber of workflow actions failedCountApplicable
ActionsSkippedNumber of workflow actions skippedCountApplicable
ActionsStartedNumber of workflow actions startedCountApplicable
ActionsSucceededNumber of workflow actions succeededCountApplicable
IntegrationServiceEnvironmentWorkflowMemoryUsageWorkflow memory usage for integration service environmentPercentApplicable
IntegrationServiceEnvironmentWorkflowProcessorUsageWorkflow processor usage for integration service environmentPercentApplicable
RunFailurePercentagePercentage of workflow runs failedPercent
RunLatencyLatency of completed workflow runsSecondApplicable
RunStartThrottledEventsNumber of workflow run start throttled eventsCountApplicable
RunSuccessLatencyLatency of succeeded workflow runsSecondApplicable
RunThrottledEventsNumber of workflow action or trigger throttled eventsCountApplicable
RunsCancelledNumber of workflow runs cancelledCountApplicable
RunsCompletedNumber of workflow runs completedCountApplicable
RunsFailedNumber of workflow runs failedCountApplicable
RunsStartedNumber of workflow runs startedCountApplicable
RunsSucceededNumber of workflow runs succeededCountApplicable
TriggerFireLatencyLatency of fired workflow triggersSecondApplicable
TriggerLatencyLatency of completed workflow triggersSecondApplicable
TriggerSuccessLatencyLatency of succeeded workflow triggersSecondApplicable
TriggerThrottledEventsNumber of workflow trigger throttled eventsCountApplicable
TriggersCompletedNumber of workflow triggers completedCountApplicable
TriggersFailedNumber of workflow triggers failedCountApplicable
TriggersFiredNumber of workflow triggers firedCountApplicable
TriggersSkippedNumber of workflow triggers skippedCountApplicable
TriggersStartedNumber of workflow triggers startedCountApplicable
TriggersSucceededNumber of workflow triggers succeededCountApplicable
Related tags
Infrastructure Observability