Collect Organization, Environment, Application, Endpoint, APIs and Workers metrics for your Mulesoft Cloudhub apps.

Metrics

• vCores Production - The number of vCores active on the organization for Production environments
• vCores Sandbox - The number of vCores active on the organization for Sandbox environments
• vCores Design - The number of vCores active on the organization for Design environments
• VPCs - The number of VPCs active on the organization
• VPNs - The number of VPNs active on the organization
• Gateways - The number of Gateways active on the organization
• Applications - The number of Applications on the organization
• Started Applications - The number of Applications that are started on the organization
• Workers - The number of Workers for an application
• Remaining Workers - The number of Workers remaining for an application
• Requests - The number of requests for an application
• Errors - The number of errors for an application
• Response Time - The average response time for an application
• JVM Heap Used - The amount of JVM Heap used for the worker
• JVM Heap Total - The total amount of JVM Heap for the worker
• Thread Count - The number of threads for the worker
• CPU - The CPU usage for the worker
• Load Average - The load average for the worker
• Available Processors - The number of available processors for the worker
• Requests - Per endpoint and response type
• Response time - Per endpoint and response type
• Outbound Response Time - Per endpoint and response type
• Outbound Requests - Per endpoint and response type
• API Requests - Per API, response_code
• API Request Size - Per API, response_code
• API Response Size - Per API, response_code
• API Response Time - Per API, response_code
• API Policy Violations - Per API, policy
• API Requests by Location" - Per API and Location

Requirements

• Monitoring needs to be enabled for Cloudhub 1.0 apps, see here
• Cloudhub 2.0 apps are not supported at this time

Mulesoft configuration

• On your Mulesoft account, under Access Management create a Connected App.

Give the connected app the following scopes:

• Monitoring Viewer
  • Note, you MUST include the root organization (business unit) on this scope
• View Organization
• View Environment
• Read Applications
• View APIs Configuration

Dynatrace configuration

Under Extensions on the left menu, select Mulesoft Cloudhub.

Add a monitoring configuration.

• Mulesoft Domain URL
  • This is the URL to access your Mulesoft account, for most cases this is https://anypoint.mulesoft.com
  • For Europe, this is https://eu1.anypoint.mulesoft.com
  • For Government Cloud this is https://gov.anypoint.mulesoft.com
• Mulesoft Client ID
  • From the connected app you created, copy the Client ID
• Mulesoft Client Secret
  • From the connected app you created, copy the Client Secret
• Mulesoft Organization/Business Group ID
  • Optional, if empty the default Organization ID will be used
  • You can get a list of all organizations under https://anypoint.mulesoft.com/accounts/businessGroups
• Frequency
  • How often should we collect data
• Environments filter
  • Optionally you can filter to only monitor certain environments and applications
  • These filters behave as "contains"
  • You can have multiple filters for a single monitoring configuration
• Proxy
  • If you need to use a proxy to access the Mulesoft API, you can configure it here

Q: What is the DDU Consumption of this extension?

A: The formula for DDU consumption of the extension is:

8 + (7 * <applications>) + (6 * <workers>) + (6 * <apis>) * 525.6 DDUs/year

Example, monitoring 25 applications, with 3 workers per application and 10 APIs gives:

(8 + (7 * 25) + (6 * 75) + (6*10)) * 525.6 DDUs/year = 364,240 (364k) DDUs/year