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: 	          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:
  
negative.code: * 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.
  * Use Dynatrace Summary instruments: In some cases the Micrometer Dynatrace registry created metrics that were rejected.
  In Micrometer 1.9.x, this was fixed by introducing Dynatrace-specific summary instruments.
  Setting this toggle to `false` forces Micrometer to fall back to the behavior that was the default before 1.9.x.
  It should only be used when encountering problems while migrating from Micrometer 1.8.x to 1.9.x.
  
  It is possible to not specify a URI and API token, as shown in the following example.
  In this scenario, the automatically configured endpoint is used:
  