anchor.diff:  
   [[actuator.metrics.export.dynatrace.version-independent-settings]]
   ===== Version-independent Settings
  +
   In addition to the API endpoint and token, you can also change the interval at which metrics are sent to Dynatrace.
   The default export interval is `60s`.
   The following example sets the export interval to 30 seconds:
  
positive.code: 	        api-token: "YOUR_TOKEN"
  ----
  
  When using the Dynatrace v2 API, the following optional features are available:
  
  * Metric key prefix: Sets a prefix that is prepended to all exported metric keys.
  * Enrich with Dynatrace metadata: If a OneAgent or Dynatrace operator is running, enrich metrics with additional metadata (for example, about the host, process, or pod).
  * Default dimensions: Specify key-value pairs that are added to all exported metrics.
    If tags with the same key are specified with Micrometer, they overwrite the default dimensions.
  
  It is possible to not specify a URI and API token, as shown in the following example.
  In this scenario, the local OneAgent endpoint is used:
  
  [source,yaml,indent=0,subs="verbatim",configprops,configblocks]
  ----
  
negative.code: 	          default-dimensions:
  	            key1: "value1"
  	            key2: "value2"
  	          use-dynatrace-summary-instruments: true # (default: true)
  ----
  
  [[actuator.metrics.export.dynatrace.v1-api]]
  ===== v1 API (Legacy)
  
  The Dynatrace v1 API metrics registry pushes metrics to the configured URI periodically by using the {dynatrace-help}/dynatrace-api/environment-api/metric-v1/[Timeseries v1 API].
  For backwards-compatibility with existing setups, when `device-id` is set (required for v1, but not used in v2), metrics are exported to the Timeseries v1 endpoint.
  To export metrics to {micrometer-registry-docs}/dynatrace[Dynatrace], your API token, device ID, and URI must be provided:
  