@dynatrace-sdk/client-classic-environment-v2 1.2.3 → 1.3.0

package/types/packages/client/classic-environment-v2/src/lib/apis/logs-api.d.ts

@@ -17,88 +17,22 @@ export declare class LogsClient {
      */
     constructor(httpClientImplementation: HttpClient);
     /**
-     * Pushes log records to Dynatrace
-     *
-     * **Required scope:** storage:logs:write<br/>**Required permission:** storage:logs:write<br/><br/>Ingested logs are stored in the indexed log storage.
-     *
-     * This endpoint requires an ActiveGate with the **Log Analytics Collector** module enabled.
-     *
-     * The maximum payload size of a single request is **5 MB**. Requests with a greater payload are rejected, and the API returns a 413 response code.
-     *
-     * If the ingested payload is a JSON array, the maximum array size is **50000**. Requests with a greater payload are rejected, and the API returns a 413 response code.
-     *
-     * <br />**Log events per minute (SaaS)**:
-     *
-     * Grail tenants: no limit, other tenants: 1M per minute by default.
-     *
-     * If your log data stream within your cluster exceeds the limit, all log events above the limit are ignored.
-     *
-     * <br />**Log events per minute (Managed)**:
-     *
-     * 1k/minute per cluster by default.
-     *
-     * If your log data stream within your cluster exceeds the limit, all log events above the limit are ignored.
-     *
-     * If you increase resources (RAM) in your nodes, you can increase the limit based on the cluster resources size using an API call or Cluster Management Console (CMC).
-     *
-     * <br />Refresh cluster limit using the API call
-     *
-     * See [Update log events per cluster for Log Monitoring](https://dt-url.net/f123yeu).
-     *
-     * <br />Refresh cluster limit using Cluster Management Console (CMC)
-     *
-     * 1. In the CMC, select **Environments** and the environment for which you wish to update the total log events per cluster.
-     *
-     * 2. On the environment details page, in the **Cluster overload prevention settings** section, select the **Refresh cluster limit**.
-     *
-     * **High-cardinality attributes:**
-     *
-     * Unique log data attributes (high-cardinality attributes) such as `span_id` and `trace_id` generate unnecessarily excessive facet lists that may impact log viewer performance. Because of this, they aren't listed in log viewer facets. You can still use them in a log viewer advanced search query.
-     *
-     * @returns Only a part of input events were ingested due to event invalidity. For details, check the response body.
-     *
-     * @example <caption>Code example</caption>
-     * import { logsClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data = await logsClient.storeLog({
-     *   body: {} as LogMessageJson,
-     * });
-     */
-    storeLog(config: ({
-        body: LogMessageJson;
-        type: 'application/json; charset=utf-8';
-    } | {
-        body: LogMessagePlain;
-        type: 'text/plain; charset=utf-8';
-    }) & {
-        abortSignal?: AbortSignal;
-    }): Promise<SuccessEnvelope | void>;
-    /**
-     * Exports log records | maturity=EARLY_ADOPTER
-     *
-     * **Required scope:** environment-api<br/>**Required permission:** environment:roles:logviewer<br/><br/>Returns the first *X* records (specified in the **pageSize** query parameter).
+     * Gets aggregated log records | maturity=EARLY_ADOPTER
      *
-     *  Unlike the **search** API, this API does not split the result into slices and has no limit for the total number of records. Log records are sorted by the criteria specified in the **sort** query parameter.
+     * **Required scope:** storage:logs:read<br/>**Required permission:** environment:roles:logviewer<br/><br/>Returns the aggregated number of occurrences of log values divided into time slots.
      *
-     *  In order to fetch large amount of records (exceeding the **pageSize** value), one should repeat the **export** call with **nextPageKey** param.
+     * It is possible that the timeframe covered by results exceeds the specified timeframe. In that case the request returns fewer time slots than specified in the **timeBuckets** query parameter.
      *
-     * Disabled on *Log Management and Analytics, powered by Grail*.
+     * If *Log Management and Analytics, powered by Grail* is enabled, then an OAuth token is required with *storage:logs:read* and *storage:buckets:read* scopes.
      *
      * @returns Success
      *
      * @example <caption>Code example</caption>
      * import { logsClient } from "@dynatrace-sdk/client-classic-environment-v2";
      *
-     * const data = await logsClient.exportLogRecords({
-     *   from: "...",
-     *   to: "...",
-     *   nextPageKey: "...",
-     *   pageSize: 123,
-     *   query: "...",
-     *   sort: "...",
-     * });
+     * const data = await logsClient.getLogHistogramData();
      */
-    exportLogRecords(config?: {
+    getLogHistogramData(config?: {
         /**
          * The start of the requested timeframe.
          *
@@ -135,54 +69,57 @@ export declare class LogsClient {
          *
          * If not set, the current timestamp is used.
          */ to?: string;
-        /**
-         * The cursor for the next page of results. You can find it in the **nextPageKey** field of the previous response.
-         *
-         * The first page is always returned if you don't specify the **nextPageKey** query parameter.
-         *
-         * When the **nextPageKey** is set to obtain subsequent pages, you must omit all other query parameters.
-         */ nextPageKey?: string;
-        /** The number of results per result page. */ pageSize?: number;
         /**
          * The log search query.
          *
          * The query must use the [Dynatrace search query language](https://dt-url.net/pe03s6f).
          */ query?: string;
         /**
-         * Defines the ordering of the log records.
+         * The number of time slots in the result.
          *
-         * Each field has a sign prefix (+/-) for sorting order. If no sign prefix is set, then the `+` option will be applied.
+         * The query timeframe is divided equally into the specified number of slots.
          *
-         * Currently, ordering is available only for the timestamp (+timestamp for the oldest records first, or -timestamp for the newest records first).
+         * The minimum length of a slot is 1 ms.
          *
-         * When millisecond resolution provided by the timestamp is not enough, log records are sorted based on the order in which they appear in the log source (remote process writing to REST API endpoint or remote process from which logs are collected).
-         */ sort?: string;
+         * If not set, 1 is used.
+         */ timeBuckets?: number;
+        /**
+         * The maximum number of values in each group.
+         *
+         * You can get up to 100 values per group.
+         *
+         * If not set, 10 is used.
+         */ maxGroupValues?: number;
+        /**
+         * The groupings to be included in the response.
+         *
+         * You can specify several groups in the following format: `groupBy=status&groupBy=log.source`.
+         *
+         * If not set, all possible groups are returned. You can use this option to check for possible grouping values.
+         *
+         * Unique log data attributes (high-cardinality attributes) for example, `span_id` or `trace_id` cannot be used for grouping.
+         */ groupBy?: string[];
         abortSignal?: AbortSignal;
-    }): Promise<ExportedLogRecordList>;
+    }): Promise<AggregatedLog>;
     /**
-     * Gets aggregated log records | maturity=EARLY_ADOPTER
+     * Exports log records | maturity=EARLY_ADOPTER
      *
-     * **Required scope:** storage:logs:read<br/>**Required permission:** environment:roles:logviewer<br/><br/>Returns the aggregated number of occurrences of log values divided into time slots.
+     * **Required scope:** environment-api<br/>**Required permission:** environment:roles:logviewer<br/><br/>Returns the first *X* records (specified in the **pageSize** query parameter).
      *
-     * It is possible that the timeframe covered by results exceeds the specified timeframe. In that case the request returns fewer time slots than specified in the **timeBuckets** query parameter.
+     *  Unlike the **search** API, this API does not split the result into slices and has no limit for the total number of records. Log records are sorted by the criteria specified in the **sort** query parameter.
      *
-     * If *Log Management and Analytics, powered by Grail* is enabled, then an OAuth token is required with *storage:logs:read* and *storage:buckets:read* scopes.
+     *  In order to fetch large amount of records (exceeding the **pageSize** value), one should repeat the **export** call with **nextPageKey** param.
+     *
+     * Disabled on *Log Management and Analytics, powered by Grail*.
      *
      * @returns Success
      *
      * @example <caption>Code example</caption>
      * import { logsClient } from "@dynatrace-sdk/client-classic-environment-v2";
      *
-     * const data = await logsClient.getLogHistogramData({
-     *   from: "...",
-     *   to: "...",
-     *   query: "...",
-     *   timeBuckets: 123,
-     *   maxGroupValues: 123,
-     *   groupBy: [],
-     * });
+     * const data = await logsClient.exportLogRecords();
      */
-    getLogHistogramData(config?: {
+    exportLogRecords(config?: {
         /**
          * The start of the requested timeframe.
          *
@@ -220,37 +157,111 @@ export declare class LogsClient {
          * If not set, the current timestamp is used.
          */ to?: string;
         /**
-         * The log search query.
-         *
-         * The query must use the [Dynatrace search query language](https://dt-url.net/pe03s6f).
-         */ query?: string;
-        /**
-         * The number of time slots in the result.
-         *
-         * The query timeframe is divided equally into the specified number of slots.
+         * The cursor for the next page of results. You can find it in the **nextPageKey** field of the previous response.
          *
-         * The minimum length of a slot is 1 ms.
+         * The first page is always returned if you don't specify the **nextPageKey** query parameter.
          *
-         * If not set, 1 is used.
-         */ timeBuckets?: number;
+         * When the **nextPageKey** is set to obtain subsequent pages, you must omit all other query parameters.
+         */ nextPageKey?: string;
+        /** The number of results per result page. */ pageSize?: number;
         /**
-         * The maximum number of values in each group.
-         *
-         * You can get up to 100 values per group.
+         * The log search query.
          *
-         * If not set, 10 is used.
-         */ maxGroupValues?: number;
+         * The query must use the [Dynatrace search query language](https://dt-url.net/pe03s6f).
+         */ query?: string;
         /**
-         * The groupings to be included in the response.
+         * Defines the ordering of the log records.
          *
-         * You can specify several groups in the following format: `groupBy=status&groupBy=log.source`.
+         * Each field has a sign prefix (+/-) for sorting order. If no sign prefix is set, then the `+` option will be applied.
          *
-         * If not set, all possible groups are returned. You can use this option to check for possible grouping values.
+         * Currently, ordering is available only for the timestamp (+timestamp for the oldest records first, or -timestamp for the newest records first).
          *
-         * Unique log data attributes (high-cardinality attributes) for example, `span_id` or `trace_id` cannot be used for grouping.
-         */ groupBy?: string[];
+         * When millisecond resolution provided by the timestamp is not enough, log records are sorted based on the order in which they appear in the log source (remote process writing to REST API endpoint or remote process from which logs are collected).
+         */ sort?: string;
         abortSignal?: AbortSignal;
-    }): Promise<AggregatedLog>;
+    }): Promise<ExportedLogRecordList>;
+    /**
+     * Pushes log records to Dynatrace
+     *
+     * **Required scope:** storage:logs:write<br/>**Required permission:** storage:logs:write<br/><br/>Ingested logs are stored in the indexed log storage.
+     *
+     * This endpoint requires an ActiveGate with the **Log Analytics Collector** module enabled.
+     *
+     * The maximum payload size of a single request is **5 MB**. Requests with a greater payload are rejected, and the API returns a 413 response code.
+     *
+     * If the ingested payload is a JSON array, the maximum array size is **50000**. Requests with a greater payload are rejected, and the API returns a 413 response code.
+     *
+     * <br />**Log events per minute (SaaS)**:
+     *
+     * Grail tenants: no limit, other tenants: 1M per minute by default.
+     *
+     * If your log data stream within your cluster exceeds the limit, all log events above the limit are ignored.
+     *
+     * <br />**Log events per minute (Managed)**:
+     *
+     * 1k/minute per cluster by default.
+     *
+     * If your log data stream within your cluster exceeds the limit, all log events above the limit are ignored.
+     *
+     * If you increase resources (RAM) in your nodes, you can increase the limit based on the cluster resources size using an API call or Cluster Management Console (CMC).
+     *
+     * <br />Refresh cluster limit using the API call
+     *
+     * See [Update log events per cluster for Log Monitoring](https://dt-url.net/f123yeu).
+     *
+     * <br />Refresh cluster limit using Cluster Management Console (CMC)
+     *
+     * 1. In the CMC, select **Environments** and the environment for which you wish to update the total log events per cluster.
+     *
+     * 2. On the environment details page, in the **Cluster overload prevention settings** section, select the **Refresh cluster limit**.
+     *
+     * **High-cardinality attributes:**
+     *
+     * Unique log data attributes (high-cardinality attributes) such as `span_id` and `trace_id` generate unnecessarily excessive facet lists that may impact log viewer performance. Because of this, they aren't listed in log viewer facets. You can still use them in a log viewer advanced search query.
+     *
+     * @returns Only a part of input events were ingested due to event invalidity. For details, check the response body.
+     *
+     * @example <caption>Code example</caption>
+     * import { logsClient } from "@dynatrace-sdk/client-classic-environment-v2";
+     *
+     * const data = await logsClient.storeLog({
+     *   type: "application/json; charset=utf-8",
+     *   body: [
+     *     {
+     *       content:
+     *         "Exception: Custom error log sent via Generic Log Ingest",
+     *       "log.source": "/var/log/syslog",
+     *       timestamp: "2022-01-17T22:12:31.0000",
+     *       severity: "error",
+     *       "custom.attribute": "attribute value",
+     *     },
+     *     {
+     *       content:
+     *         "Exception: Custom error log sent via Generic Log Ingest",
+     *       "log.source": "/var/log/syslog",
+     *       timestamp: "2022-01-17T22:12:35.0000",
+     *     },
+     *     {
+     *       content:
+     *         "Exception: Custom error log sent via Generic Log Ingest",
+     *       "log.source": "/var/log/syslog",
+     *     },
+     *     {
+     *       content:
+     *         "Exception: Custom error log sent via Generic Log Ingest",
+     *     },
+     *   ],
+     * });
+     */
+    storeLog(config: ({
+        body: LogMessageJson;
+        type: 'application/json; charset=utf-8';
+    } | {
+        body: LogMessagePlain;
+        type: 'text/plain; charset=utf-8';
+    }) & {
+        abortSignal?: AbortSignal;
+    }): Promise<SuccessEnvelope | void>;
     /**
      * Reads log records | maturity=EARLY_ADOPTER
      *
@@ -267,14 +278,7 @@ export declare class LogsClient {
      * @example <caption>Code example</caption>
      * import { logsClient } from "@dynatrace-sdk/client-classic-environment-v2";
      *
-     * const data = await logsClient.getLogRecords({
-     *   from: "...",
-     *   to: "...",
-     *   limit: 123,
-     *   query: "...",
-     *   sort: "...",
-     *   nextSliceKey: "...",
-     * });
+     * const data = await logsClient.getLogRecords();
      */
     getLogRecords(config?: {
         /**

package/types/packages/client/classic-environment-v2/src/lib/apis/metrics-api.d.ts

@@ -14,45 +14,6 @@ export declare class MetricsClient {
      * const queryClientNodeJs = new QueryClient(yourCustomImplementation);
      */
     constructor(httpClientImplementation: HttpClient);
-    /**
-     * Gets the descriptor of the specified metric
-     *
-     * **Required scope:** environment-api:metrics:read<br/>**Required permission:** environment:roles:viewer
-     *
-     * @returns Success
-     *
-     * @example <caption>Code example</caption>
-     * import { metricsClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data = await metricsClient.metric({
-     *   metricKey: "...",
-     * });
-     */
-    metric(config: {
-        /**
-         * The key of the required metric.
-         *
-         * You can set additional transformation operators, separated by a colon (`:`). See [Metrics selector transformations](https://dt-url.net/metricSelector) in Dynatrace Documentation for additional information on available result transformations and syntax.
-         */ metricKey: string;
-        abortSignal?: AbortSignal;
-        acceptType: 'application/json; charset=utf-8' | 'text/csv; header=present; charset=utf-8' | 'text/csv; header=absent; charset=utf-8';
-    }): Promise<MetricDescriptor>;
-    /**
-     * Deletes the specified metric
-     *
-     * **Required scope:** environment-api:metrics:write<br/>**Required permission:** environment:roles:manage-settings<br/><br/>Deletion cannot be undone! You can't delete a metric if it has data points ingested within the last two hours.
-     *
-     * @example <caption>Code example</caption>
-     * import { metricsClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data = await metricsClient.delete({
-     *   metricKey: "...",
-     * });
-     */
-    delete(config: {
-        /** The key of the required metric. */ metricKey: string;
-        abortSignal?: AbortSignal;
-    }): Promise<void>;
     /**
      * Lists all available metrics
      *
@@ -70,13 +31,7 @@ export declare class MetricsClient {
      * import { metricsClient } from "@dynatrace-sdk/client-classic-environment-v2";
      *
      * const data = await metricsClient.allMetrics({
-     *   nextPageKey: "...",
-     *   pageSize: 123,
-     *   metricSelector: "...",
-     *   text: "...",
-     *   fields: "...",
-     *   writtenSince: "...",
-     *   metadataSelector: "...",
+     *   acceptType: "application/json; charset=utf-8",
      * });
      */
     allMetrics(config: {
@@ -130,7 +85,8 @@ export declare class MetricsClient {
          * * `description`: A short description of the metric. Enabled by default.
          * * `unit`: The unit of the metric. Enabled by default.
          * * `tags`: The tags of the metric.
-         * + `dduBillable`:  An indicator whether the usage of metric consumes [Davis data units](https://dt-url.net/ddu).
+         * + `dduBillable`:  An indicator whether the usage of metric consumes [Davis data units](https://dt-url.net/ddu). Deprecated and always `false` for Dynatrace Platform Subscription. Superseded by `billable`.
+         * + `billable`:  An indicator whether the usage of metric is billable.
          * * `created`:  The timestamp (UTC milliseconds) when the metrics has been created.
          * * `lastWritten`:  The timestamp (UTC milliseconds) when metric data points have been written for the last time.
          * * `aggregationTypes`: The list of allowed aggregations for the metric. Note that it may be different after a [transformation](https://dt-url.net/metricSelector) is applied.
@@ -190,8 +146,26 @@ export declare class MetricsClient {
          * For example, to list metrics that have the tags **feature** AND **cloud** with a unit of **Percent** OR **MegaByte** AND a dimension with a dimension key **location**, use this **metadataSelector**: `tags("feature"),unit("Percent","MegaByte"),tags("cloud"),dimensionKey("location")`.
          */ metadataSelector?: string;
         abortSignal?: AbortSignal;
-        acceptType: 'application/json; charset=utf-8' | 'text/csv; header=present; charset=utf-8' | 'text/csv; header=absent; charset=utf-8';
+        acceptType: 'application/json; charset=utf-8' | 'text/csv; header=absent; charset=utf-8' | 'text/csv; header=present; charset=utf-8';
     }): Promise<MetricDescriptorCollection>;
+    /**
+     * Pushes metric data points to Dynatrace
+     *
+     * **Required scope:** storage:metrics:write<br/>**Required permission:** storage:metrics:write
+     *
+     * @returns The provided metric data points are accepted and will be processed in the background.
+     *
+     * @example <caption>Code example</caption>
+     * import { metricsClient } from "@dynatrace-sdk/client-classic-environment-v2";
+     *
+     * const data = await metricsClient.ingest({
+     *   body: "server.cpu.temperature,cpu.id=0 42",
+     * });
+     */
+    ingest(config: {
+        body: string;
+        abortSignal?: AbortSignal;
+    }): Promise<ValidationResponse>;
     /**
      * Gets data points of the specified metrics
      *
@@ -210,12 +184,7 @@ export declare class MetricsClient {
      * import { metricsClient } from "@dynatrace-sdk/client-classic-environment-v2";
      *
      * const data = await metricsClient.query({
-     *   metricSelector: "...",
-     *   resolution: "...",
-     *   from: "...",
-     *   to: "...",
-     *   entitySelector: "...",
-     *   mzSelector: "...",
+     *   acceptType: "application/json; charset=utf-8",
      * });
      */
     query(config: {
@@ -345,25 +314,47 @@ export declare class MetricsClient {
          * To set several criteria, separate them with a comma (`,`). For example, `mzName("name-1","name-2"),mzId(1234)`. Only results matching **all** of the criteria are included in the response.For example, to list metrics that have the id **123** OR **234** AND the name **name-1** OR **name-2**, use this **mzSelector**: `mzId(123,234),mzName("name-1","name-2").
          */ mzSelector?: string;
         abortSignal?: AbortSignal;
-        acceptType: 'application/json; charset=utf-8' | 'text/csv; header=present; charset=utf-8' | 'text/csv; header=absent; charset=utf-8';
+        acceptType: 'application/json; charset=utf-8' | 'text/csv; header=absent; charset=utf-8' | 'text/csv; header=present; charset=utf-8';
     }): Promise<MetricData>;
     /**
-     * Pushes metric data points to Dynatrace
+     * Gets the descriptor of the specified metric
      *
-     * **Required scope:** storage:metrics:write<br/>**Required permission:** storage:metrics:write
+     * **Required scope:** environment-api:metrics:read<br/>**Required permission:** environment:roles:viewer
      *
-     * @returns The provided metric data points are accepted and will be processed in the background.
+     * @returns Success
      *
      * @example <caption>Code example</caption>
      * import { metricsClient } from "@dynatrace-sdk/client-classic-environment-v2";
      *
-     * const data = await metricsClient.ingest({
-     *   body: "server.cpu.temperature,cpu.id=0 42" as string,
+     * const data = await metricsClient.metric({
+     *   acceptType: "application/json; charset=utf-8",
+     *   metricKey: "...",
      * });
      */
-    ingest(config: {
-        body: string;
+    metric(config: {
+        /**
+         * The key of the required metric.
+         *
+         * You can set additional transformation operators, separated by a colon (`:`). See [Metrics selector transformations](https://dt-url.net/metricSelector) in Dynatrace Documentation for additional information on available result transformations and syntax.
+         */ metricKey: string;
         abortSignal?: AbortSignal;
-    }): Promise<ValidationResponse>;
+        acceptType: 'application/json; charset=utf-8' | 'text/csv; header=absent; charset=utf-8' | 'text/csv; header=present; charset=utf-8';
+    }): Promise<MetricDescriptor>;
+    /**
+     * Deletes the specified metric
+     *
+     * **Required scope:** environment-api:metrics:write<br/>**Required permission:** environment:roles:manage-settings<br/><br/>Deletion cannot be undone! You can't delete a metric if it has data points ingested within the last two hours.
+     *
+     * @example <caption>Code example</caption>
+     * import { metricsClient } from "@dynatrace-sdk/client-classic-environment-v2";
+     *
+     * const data = await metricsClient.delete({
+     *   metricKey: "...",
+     * });
+     */
+    delete(config: {
+        /** The key of the required metric. */ metricKey: string;
+        abortSignal?: AbortSignal;
+    }): Promise<void>;
 }
 export declare const metricsClient: MetricsClient;

package/types/packages/client/classic-environment-v2/src/lib/apis/metrics-units-api.d.ts

@@ -14,40 +14,39 @@ export declare class MetricsUnitsClient {
      */
     constructor(httpClientImplementation: HttpClient);
     /**
-     * Converts a value from a source unit into a target unit
+     * Lists all available units
      *
-     * **Required scope:** environment-api:metrics:read<br/>**Required permission:** environment:roles:viewer<br/><br/>If no target unit is set, the request finds an appropriate target unit automatically, taking into account the preferred number format (if specified).
+     * **Required scope:** environment-api:metrics:read<br/>**Required permission:** environment:roles:viewer<br/><br/>You can narrow down the output by providing filter criteria in the **unitSelector** field.
      *
      * @returns Success
      *
      * @example <caption>Code example</caption>
      * import { metricsUnitsClient } from "@dynatrace-sdk/client-classic-environment-v2";
      *
-     * const data = await metricsUnitsClient.convert({
-     *   unitId: "...",
-     *   value: 123,
-     *   targetUnit: "...",
-     *   numberFormat: "...",
-     * });
+     * const data = await metricsUnitsClient.allUnits();
      */
-    convert(config: {
-        /** The ID of the source unit. */ unitId: string;
-        /** The value to be converted. */ value: number;
+    allUnits(config?: {
         /**
-         * The ID of the target unit.
-         *
-         * If not set, the request finds an appropriate target unit automatically, based on the specified number format.
-         */ targetUnit?: string;
+         * Selects units to be included to the response. Available criteria:
+         * * Compatibility: `compatibleTo("unit","display-format")`. Returns units that can be converted to the specified unit. The optional display format (`binary` or `decimal`) argument is supported by bit- and byte-based units and returns only units for the specified format.
+         */ unitSelector?: string;
         /**
-         * The preferred number format of the target value. You can specify the following formats:
+         * Defines the list of properties to be included in the response. The ID of the unit is **always** included. The following additional properties are available:
          *
-         * * `binary`
-         * * `decimal`
+         * * `displayName`: The display name of the unit.
+         * * `symbol`: The symbol of the unit.
+         * * `description`: A short description of the unit.
          *
-         * `Only used if the target unit if not set.
-         */ numberFormat?: string;
+         * By default, the ID, the display name, and the symbol are included.
+         *
+         * To add properties, list them with leading plus `+`. To exclude default properties, list them with leading minus `-`.
+         *
+         * To specify several properties, join them with a comma (for example `fields=+description,-symbol`).
+         *
+         * If you specify just one property, the response contains the unitId and the specified property. To return unit IDs only, specify `unitId` here.
+         */ fields?: string;
         abortSignal?: AbortSignal;
-    }): Promise<UnitConversionResult>;
+    }): Promise<UnitList>;
     /**
      * Gets the properties of the specified unit
      *
@@ -67,41 +66,37 @@ export declare class MetricsUnitsClient {
         abortSignal?: AbortSignal;
     }): Promise<Unit>;
     /**
-     * Lists all available units
+     * Converts a value from a source unit into a target unit
      *
-     * **Required scope:** environment-api:metrics:read<br/>**Required permission:** environment:roles:viewer<br/><br/>You can narrow down the output by providing filter criteria in the **unitSelector** field.
+     * **Required scope:** environment-api:metrics:read<br/>**Required permission:** environment:roles:viewer<br/><br/>If no target unit is set, the request finds an appropriate target unit automatically, taking into account the preferred number format (if specified).
      *
      * @returns Success
      *
      * @example <caption>Code example</caption>
      * import { metricsUnitsClient } from "@dynatrace-sdk/client-classic-environment-v2";
      *
-     * const data = await metricsUnitsClient.allUnits({
-     *   unitSelector: "...",
-     *   fields: "...",
+     * const data = await metricsUnitsClient.convert({
+     *   unitId: "...",
+     *   value: 10,
      * });
      */
-    allUnits(config?: {
-        /**
-         * Selects units to be included to the response. Available criteria:
-         * * Compatibility: `compatibleTo("unit","display-format")`. Returns units that can be converted to the specified unit. The optional display format (`binary` or `decimal`) argument is supported by bit- and byte-based units and returns only units for the specified format.
-         */ unitSelector?: string;
+    convert(config: {
+        /** The ID of the source unit. */ unitId: string;
+        /** The value to be converted. */ value: number;
         /**
-         * Defines the list of properties to be included in the response. The ID of the unit is **always** included. The following additional properties are available:
-         *
-         * * `displayName`: The display name of the unit.
-         * * `symbol`: The symbol of the unit.
-         * * `description`: A short description of the unit.
-         *
-         * By default, the ID, the display name, and the symbol are included.
+         * The ID of the target unit.
          *
-         * To add properties, list them with leading plus `+`. To exclude default properties, list them with leading minus `-`.
+         * If not set, the request finds an appropriate target unit automatically, based on the specified number format.
+         */ targetUnit?: string;
+        /**
+         * The preferred number format of the target value. You can specify the following formats:
          *
-         * To specify several properties, join them with a comma (for example `fields=+description,-symbol`).
+         * * `binary`
+         * * `decimal`
          *
-         * If you specify just one property, the response contains the unitId and the specified property. To return unit IDs only, specify `unitId` here.
-         */ fields?: string;
+         * `Only used if the target unit if not set.
+         */ numberFormat?: string;
         abortSignal?: AbortSignal;
-    }): Promise<UnitList>;
+    }): Promise<UnitConversionResult>;
 }
 export declare const metricsUnitsClient: MetricsUnitsClient;