• Home
  • Deploy Dynatrace
  • Set up Dynatrace on cloud platforms
  • Microsoft Azure
  • Integrations
  • Azure cloud services
  • Monitori Azure Spring Apps

Monitori Azure Spring Apps

Dynatrace ingests metrics for multiple preselected namespaces, including Azure Spring Apps. 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.195+

Enable monitoring

To enable monitoring for this service, you first need to set up integration with Azure Monitor.

Activate OneAgent recommended

For an end-to-end view into your Spring Apps workloads, you can set up OneAgent integration with Azure Spring Apps.

Add the service to monitoring

In order to view the service metrics, you must add the service to monitoring in your Dynatrace environment.

To add a service to monitoring
  1. In the Dynatrace menu, go to Settings > Cloud and virtualization and select Azure.
  2. On the Azure overview page, select Edit for the desired Azure instance.
  3. Go to Services and select Add service, choose the desired service name from the list, and select Add service.
  4. Select Save changes to save your configuration.

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

  1. In the Dynatrace menu, go to Settings > Cloud and virtualization > Azure and select Edit for the desired Azure instance.
  2. For Resources to be monitored, select Monitor resources selected by tags.
  3. Enter the Key and Value.
  4. Select Save to save your configuration.

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
To add and configure metrics
  1. In the Dynatrace menu, go to Settings > Cloud and virtualization and select Azure.
  2. On the Azure overview page, scroll down and select Edit for the desired Azure instance.
  3. Go to Services and select Manage services.
  4. To add a metric, select the service for which you want to add metrics.
  5. Select Add new metric.
  6. From the menu, select the metric you want.
  7. Select Add metric to add the metric to monitoring.
  8. To configure a metric, select Edit.
  9. Select Apply to save your configuration.

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. In the Dynatrace menu, go to Technologies.
  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.

Note: 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.

Note: Hiding a dashboard doesn't affect other users.

Clone hide azure

Spring

Available metrics

NameDescriptionDimensionsUnitRecommended
jvm.gc.live.data.sizeSize of old generation memory pool after a full GCAppName, PodByte✔️
jvm.gc.max.data.sizeMax size of old generation memory poolAppName, PodByte✔️
jvm.gc.memory.allocatedIncremented for an increase in the size of the young generation memory pool after one GC to before the nextAppName, PodByte✔️
jvm.gc.memory.promotedCount of positive increases in the size of the old generation memory pool before GC to after GCAppName, PodByte✔️
jvm.gc.pause.total.countGC pause countAppName, PodCount✔️
jvm.gc.pause.total.timeGC pause total timeAppName, PodMilliSecond✔️
jvm.memory.committedMemory assigned to JVM in bytesAppName, PodByte✔️
jvm.memory.maxThe maximum amount of memory in bytes that can be used for memory managementAppName, PodByte✔️
jvm.memory.usedApp memory used in bytesAppName, PodByte✔️
process.cpu.usageApp JVM CPU usage percentageAppName, PodPercent✔️
system.cpu.usageThe recent CPU usage for the whole systemAppName, PodPercent✔️
tomcat.global.errorTomcat global errorAppName, PodCount✔️
tomcat.global.receivedTomcat total received bytesAppName, PodByte✔️
tomcat.global.request.avg.timeTomcat request average timeAppName, PodMilliSecond✔️
tomcat.global.request.maxTomcat request maximum timeAppName, PodMilliSecond✔️
tomcat.global.request.total.countTomcat request total countAppName, PodCount✔️
tomcat.global.request.total.timeTomcat request total timeAppName, PodMilliSecond✔️
tomcat.global.sentTomcat total sent bytesAppName, PodByte✔️
tomcat.sessions.active.currentTomcat session active countAppName, PodCount✔️
tomcat.sessions.active.maxTomcat session maximum active countAppName, PodCount✔️
tomcat.sessions.alive.maxTomcat session maximum alive timeAppName, PodMilliSecond✔️
tomcat.sessions.createdTomcat session created countAppName, PodCount✔️
tomcat.sessions.expiredTomcat session expired countAppName, PodCount✔️
tomcat.sessions.rejectedTomcat session rejected countAppName, PodCount✔️
tomcat.threads.config.maxTomcat configuration maximum thread countAppName, PodCount✔️
tomcat.threads.currentTomcat current thread countAppName, PodCount✔️
Related topics
  • Monitor Azure Spring Apps

    Learn how to configure OneAgent for monitoring Azure Spring Apps.