@dynatrace-sdk/client-classic-environment-v2 0.6.1

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

@@ -0,0 +1,297 @@
+import { AbortSignal, HttpClient } from '@dynatrace-sdk/http-client';
+import { AggregatedLog } from '../models/aggregated-log';
+import { ExportedLogRecordList } from '../models/exported-log-record-list';
+import { LogMessageJson } from '../models/log-message-json';
+import { LogMessagePlain } from '../models/log-message-plain';
+import { LogRecordsList } from '../models/log-records-list';
+import { SuccessEnvelope } from '../models/success-envelope';
+/**
+ * Read and ingest logs
+ */
+export declare class LogsClient {
+    private httpClient;
+    /**
+     * @param {HttpClient} httpClientImplementation - You can provide custom http client as a parameter to constructor of a LogsClient. Custom http client should implement {HttpClient} interface.
+     * @example
+     * const queryClientNodeJs = new QueryClient(yourCustomImplementation);
+     */
+    constructor(httpClientImplementation: HttpClient);
+    /**
+     * Pushes log records to Dynatrace | maturity=EARLY_ADOPTER
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + 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 **5000**. Requests with a greater payload are rejected, and the API returns a 413 response code.
+     *
+     * <br />**Log events per minute (SaaS)**:
+     *
+     * Trial tenants: 10k, paid one: 100k 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)**:
+     *
+     * 10k/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 size limits or JSON parsing issues.
+     */
+    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/><br/>Returns the first *X* records (specified in the **pageSize** 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.
+     *
+     *  In order to fetch large amount of records (exceeding the **pageSize** value), one should repeat the **export** call with **nextPageKey** param.
+     * @returns Success
+     */
+    exportLogRecords(config: {
+        /**
+         * The start of the requested timeframe.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * If not set, the relative timeframe of two weeks is used (`now-2w`).
+         */ from?: string;
+        /**
+         * The end of the requested timeframe.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * 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.
+         *
+         * Each field has a sign prefix (+/-) for sorting order. If no sign prefix is set, then the `+` option will be applied.
+         *
+         * Currently, ordering is available only for the timestamp (+timestamp for the oldest records first, or -timestamp for the newest records first).
+         *
+         * 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<ExportedLogRecordList>;
+    /**
+     * Gets aggregated log records | maturity=EARLY_ADOPTER
+     *
+     * **Required scope:** environment-api<br/><br/>Returns the aggregated number of occurrences of log values divided into time slots.
+     *
+     * 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.
+     * @returns Success
+     */
+    getLogHistogramData(config: {
+        /**
+         * The start of the requested timeframe.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * If not set, the relative timeframe of two weeks is used (`now-2w`).
+         */ from?: string;
+        /**
+         * The end of the requested timeframe.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * 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 minimum length of a slot is 1 ms.
+         *
+         * 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<AggregatedLog>;
+    /**
+     * Reads log records | maturity=EARLY_ADOPTER
+     *
+     * **Required scope:** environment-api<br/><br/>Returns the first *X* records (specified in the **limit** query parameter). Log records are sorted by the criteria specified in the **sort** query parameter.
+     *
+     * If the query is too large to be processed in a single request, it is divided into slices. In that case the first response contains the **nextSliceKey** cursor for the second slice. Use it in the **nextSliceKey** query parameter to obtain the second slice, which contains **nextSliceKey** cursor for the third slice, and so on.
+     *
+     * Results can be distributed unevenly between slices and some slices might be empty.
+     * @returns Success
+     */
+    getLogRecords(config: {
+        /**
+         * The start of the requested timeframe.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * If not set, the relative timeframe of two weeks is used (`now-2w`).
+         */ from?: string;
+        /**
+         * The end of the requested timeframe.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * If not set, the current timestamp is used.
+         */ to?: string;
+        /**
+         * The desired amount of log records.
+         *
+         * The maximal allowed limit is 1000.
+         *
+         * If not set, 1000 is used.
+         */ limit?: 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.
+         *
+         * Each field has a sign prefix (+/-) for sorting order. If no sign prefix is set, then the `+` option will be applied.
+         *
+         * Currently, ordering is available only for the timestamp (+timestamp for the oldest records first, or -timestamp for the newest records first).
+         *
+         * 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;
+        /**
+         * The cursor for the next slice of results. You can find it in the **nextSliceKey** field of the previous response.
+         *
+         * The first slice is always returned if you don't specify this parameter.
+         *
+         * If this parameter is set, all other query parameters are ignored.
+         */ nextSliceKey?: string;
+        abortSignal?: AbortSignal;
+    }): Promise<LogRecordsList>;
+}
+export declare const logsClient: LogsClient;

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

@@ -0,0 +1,316 @@
+import { AbortSignal, HttpClient } from '@dynatrace-sdk/http-client';
+import { MetricData } from '../models/metric-data';
+import { MetricDescriptor } from '../models/metric-descriptor';
+import { MetricDescriptorCollection } from '../models/metric-descriptor-collection';
+import { ValidationResponse } from '../models/validation-response';
+/**
+ * Query and ingest metrics
+ */
+export declare class MetricsClient {
+    private httpClient;
+    /**
+     * @param {HttpClient} httpClientImplementation - You can provide custom http client as a parameter to constructor of a MetricsClient. Custom http client should implement {HttpClient} interface.
+     * @example
+     * const queryClientNodeJs = new QueryClient(yourCustomImplementation);
+     */
+    constructor(httpClientImplementation: HttpClient);
+    /**
+     * Gets the descriptor of the specified metric
+     *
+     * **Required scope:** environment-api:metrics:read
+     * @returns Success
+     */
+    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/><br/>Deletion cannot be undone! You can't delete a metric if it has data points ingested within the last two hours.
+     */
+    delete(config: {
+        /** The key of the required metric. */ metricKey: string;
+        abortSignal?: AbortSignal;
+    }): Promise<void>;
+    /**
+     * Lists all available metrics
+     *
+     * **Required scope:** environment-api:metrics:read<br/><br/>You can narrow down the output by selecting metrics in the **metricSelector** field.
+     *
+     * You can additionally limit the output by using pagination:
+     *
+     * 1. Specify the number of results per page in the **pageSize** query parameter.
+     *
+     * 2. Then use the cursor from the **nextPageKey** field of the response in the **nextPageKey** query parameter to obtain subsequent pages. All other query parameters must be omitted.
+     * @returns Success
+     */
+    allMetrics(config: {
+        /**
+         * 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 amount of metric schemata in a single response payload.
+         *
+         * The maximal allowed page size is 500.
+         *
+         * If not set, 100 is used.
+         *
+         *  If a value higher than 500 is used, only 500 results per page are returned.
+         */ pageSize?: number;
+        /**
+         * Selects metrics for the query by their keys.
+         *
+         *  You can specify multiple metric keys separated by commas (for example, `metrickey1,metrickey2`). To select multiple metrics belonging to the same parent, list the last part of the required metric keys in parentheses, separated by commas, while keeping the common part untouched. For example, to list the `builtin:host.cpu.idle` and `builtin:host.cpu.user` metric, write: `builtin:host.cpu.(idle,user)`.
+         *
+         * You can select a full set of related metrics by using a trailing asterisk (`*`) wildcard. For example, `builtin:host.*` selects all host-based metrics and `builtin:*` selects all Dynatrace-provided metrics.
+         *
+         * 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.
+         *
+         *  Only `aggregation`, `merge`, `parents`, and `splitBy` transformations are supported by this endpoint.
+         *
+         *  If the metric key contains any symbols you must quote (`"`) the key. The following characters inside of a quoted metric key must be escaped with a tilde (`~`):
+         *
+         * * Quotes (`"`)
+         * * Tildes (`~`)
+         *
+         * For example, to query the metric with the key of **ext:selfmonitoring.jmx.Agents: Type "APACHE"** you must specify this selector:
+         *
+         *  `"ext:selfmonitoring.jmx.Agents: Type ~"APACHE~""`
+         *
+         *
+         *
+         *  To find metrics based on a search term, rather than metricId, use the **text** query parameter instead of this one.
+         */ metricSelector?: string;
+        /** Metric registry search term. Only show metrics that contain the term in their key, display name, or description. Use the `metricSelector` parameter instead of this one to select a complete metric hierarchy instead of doing a text-based search. */ text?: string;
+        /**
+         * Defines the list of metric properties included in the response.
+         *
+         * `metricId` is **always** included in the result. The following additional properties are available:
+         *
+         * * `displayName`: The name of the metric in the user interface. Enabled by default.
+         * * `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).
+         * * `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.
+         * * `defaultAggregation`: The default aggregation of the metric. It is used when no aggregation is specified or the `:auto` transformation is set.
+         * * `dimensionDefinitions`: The fine metric division (for example, process group and process ID for some process-related metric).
+         * * `transformations`: A list of [transformations](https://dt-url.net/metricSelector) that can be applied to the metric.
+         * * `entityType`: A list of entity types supported by the metric.
+         * * `minimumValue`: The minimum allowed value of the metric.
+         * * `maximumValue`: The maximum allowed value of the metric.
+         * * `rootCauseRelevant`: Whether (true or false) the metric is related to a root cause of a problem. A root-cause relevant metric represents a strong indicator for a faulty component.
+         * * `impactRelevant`: Whether (true or false) the metric is relevant to a problem's impact. An impact-relevant metric is highly dependent on other metrics and changes because an underlying root-cause metric has changed.
+         * * `metricValueType`: The type of the metric's value. You have these options:
+         * 	 * `score`: A score metric is a metric where high values indicate a good situation, while low values indicate trouble. An example of such a metric is a success rate.
+         * 	 * `error`: An error metric is a metric where high values indicate trouble, while low values indicate a good situation. An example of such a metric is an error count.
+         * * `latency`: The latency of the metric, in minutes. The latency is the expected reporting delay (for example, caused by constraints of cloud vendors or other third-party data sources) between the observation of a metric data point and its availability in Dynatrace. The allowed value range is from `1` to `60` minutes.
+         * * `metricSelector`: The underlying metric selector used by a func: metric.
+         * * `scalar`: Indicates whether the metric expression resolves to a scalar (`true`) or to a series (`false`).
+         * A scalar result always contains one data point. The amount of data points in a series result depends on the resolution you're using.
+         * * `resolutionInfSupported`: If `true`, resolution=Inf can be applied to the metric query.
+         *
+         * 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=+aggregationTypes,-description`).
+         *
+         * If you specify just one property, the response contains the metric key and the specified property. To return metric keys only, specify `metricId` here.
+         */ fields?: string;
+        /**
+         * Filters the resulted set of metrics to those that have data points within the specified timeframe.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         */ writtenSince?: string;
+        /**
+         * The metadata scope of the query. Only metrics with specified properties are included to the response.
+         *
+         * You can set one or more of the following criteria. Values are case-sensitive and the `EQUALS` operator is used. If several values are specified, the **OR** logic applies.
+         *
+         * * `unit("unit-1","unit-2")`
+         * * `tags("tag-1","tag-2")`
+         * * `dimensionKey("dimkey-1","dimkey-2")`. The filtering applies only to dimensions that were written within the last 14 days.
+         *
+         * To set several criteria, separate them with a comma (`,`). For example, `tags("feature","cloud"),unit("Percent"),dimensionKey("location")`. Only results matching **all** criteria are included in response.
+         *
+         * 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';
+    }): Promise<MetricDescriptorCollection>;
+    /**
+     * Gets data points of the specified metrics
+     *
+     * **Required scope:** environment-api:metrics:read<br/><br/>The following limits apply:
+     * * The amount of aggregated data points in the response is limited to 1,000
+     * * The amount of series in the response is limited to 1,000
+     *    * The amount of data points per series is limited to 10,080 (minutes of one week)
+     *    * The overall amount of data points is limited to 100,000
+     *
+     * The **dataPointCountRatio** specifies the ratio of queried data points divided by the maximum number of data points per metric that are allowed in a single query.
+     * The **dimensionCountRatio** specifies the ratio of queried dimension tuples divided by the maximum number of dimension tuples allowed in a single query.
+     * @returns Success
+     */
+    query(config: {
+        /**
+         * Selects metrics for the query by their keys. You can select up to 10 metrics for one query.
+         *
+         *  You can specify multiple metric keys separated by commas (for example, `metrickey1,metrickey2`). To select multiple metrics belonging to the same parent, list the last part of the required metric keys in parentheses, separated by commas, while keeping the common part untouched. For example, to list the `builtin:host.cpu.idle` and `builtin:host.cpu.user` metric, write: `builtin:host.cpu.(idle,user)`.
+         *
+         *
+         *
+         *  If the metric key contains any symbols you must quote (`"`) the key. The following characters inside of a quoted metric key must be escaped with a tilde (`~`):
+         *
+         * * Quotes (`"`)
+         * * Tildes (`~`)
+         *
+         * For example, to query the metric with the key of **ext:selfmonitoring.jmx.Agents: Type "APACHE"** you must specify this selector:
+         *
+         *  `"ext:selfmonitoring.jmx.Agents: Type ~"APACHE~""`
+         *
+         * 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.
+         */ metricSelector?: string;
+        /**
+         * The desired resolution of data points.
+         *
+         * You can use one of the following options:
+         * * The desired amount of data points. This is the default option. This is a reference number of points, which is not necessarily equal to the number of the returned data points.
+         * * The desired timespan between data points. This is a reference timespan, which is not necessarily equal to the returned timespan. To use this option, specify the unit of the timespan.
+         *
+         * Valid units for the timespan are:
+         * * `m`: minutes
+         * * `h`: hours
+         * * `d`: days
+         * * `w`: weeks
+         * * `M`: months
+         * * `q`: quarters
+         * * `y`: years
+         *
+         * If not set, the default is **120 data points**.
+         *
+         * For example:
+         *
+         * * Get data points which are 10 minutes apart: `resolution=10m`
+         * * Get data points which are 3 weeks apart: `resolution=3w`
+         */ resolution?: string;
+        /**
+         * The start of the requested timeframe.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * If not set, the relative timeframe of two hours is used (`now-2h`).
+         */ from?: string;
+        /**
+         * The end of the requested timeframe.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * If not set, the current timestamp is used.
+         */ to?: string;
+        /**
+         * Specifies the entity scope of the query. Only data points delivered by matched entities are included in response.
+         *
+         * You must set one of these criteria:
+         *
+         * * Entity type: `type("TYPE")`
+         * * Dynatrace entity ID: `entityId("id")`. You can specify several IDs, separated by a comma (`entityId("id-1","id-2")`). All requested entities must be of the same type.
+         *
+         * You can add one or several of the following criteria. Values are case-sensitive and the `EQUALS` operator is used unless otherwise specified.
+         *
+         * * Tag: `tag("value")`. Tags in `[context]key:value`, `key:value`, and `value` formats are detected and parsed automatically. Any colons (`:`) that are part of the key or value must be escaped with a backslash(`\`), otherwise, it will be interpreted as the separator between the key and the value. All tag values are case-sensitive.
+         * * Management zone ID: `mzId(123)`
+         * * Management zone name: `mzName("value")`
+         * * Entity name:
+         * 	* `entityName.equals`: performs a non-casesensitive `EQUALS` query.
+         * 	* `entityName.startsWith`: changes the operator to `BEGINS WITH`.
+         * 	* `entityName.in`: enables you to provide multiple values. The `EQUALS` operator applies.
+         * 	* `caseSensitive(entityName.equals("value"))`: takes any entity name criterion as an arguments and makes the value case-sensitive.
+         * * Health state (HEALTHY,UNHEALTHY): `healthState("HEALTHY")`
+         * * First seen timestamp: `firstSeenTms.<operator>(now-3h)`. Use any timestamp format from the **from** /**to** parameters.
+         * 	The following operators are available:
+         * 	* `lte`: earlier than or at the specified time
+         * 	* `lt`: earlier than the specified time
+         * 	* `gte`: later than or at the specified time
+         * 	* `gt`: later than the specified time
+         * * Entity attribute: `<attribute>("value1","value2")` and `<attribute>.exists()`. To fetch the list of available attributes, execute the [GET entity type](https://dt-url.net/2ka3ivt) request and check the **properties** field of the response.
+         * * Relationships: `fromRelationships.<relationshipName>()` and `toRelationships.<relationshipName>()`. The criterion takes an entity selector as an attribute. To fetch the list of available relationships, execute the [GET entity type](https://dt-url.net/2ka3ivt) request and check the **fromRelationships** and **toRelationships** fields.
+         * * Negation: `not(<criterion>)`. Inverts any criterion except for **type**.
+         *
+         * For more information, see [Entity selector](https://dt-url.net/apientityselector) in Dynatrace Documentation.
+         *
+         * To set several criteria, separate them with a comma (`,`). For example, `type("HOST"),healthState("HEALTHY")`. Only results matching **all** criteria are included in response.
+         *
+         * Supported string length is 2,000 characters.
+         *
+         * Use the [`GET /metrics/{metricId}`](https://dt-url.net/6z23ifk) call to fetch the list of possible entity types for your metric.
+         *
+         * To set a universal scope matching all entities, omit this parameter.
+         */ entitySelector?: string;
+        /**
+         * The management zone scope of the query. Only metrics data relating to the specified management zones are included to the response.
+         *
+         * You can set one or more of the following criteria. Values are case-sensitive and the `EQUALS` operator is used. If several values are specified, the **OR** logic applies.
+         *
+         * * `mzId(123,456)`
+         * * `mzName("name-1","name-2")`
+         * 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';
+    }): Promise<MetricData>;
+    /**
+     * Pushes metric data points to Dynatrace
+     *
+     * **Required scope:** storage:metrics:write
+     * @returns The provided metric data points are accepted and will be processed in the background.
+     */
+    ingest(config: {
+        body: string;
+        abortSignal?: AbortSignal;
+    }): Promise<ValidationResponse>;
+}
+export declare const metricsClient: MetricsClient;