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

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

@@ -0,0 +1,68 @@
+import { AbortSignal, HttpClient } from '@dynatrace-sdk/http-client';
+import { Unit } from '../models/unit';
+import { UnitConversionResult } from '../models/unit-conversion-result';
+import { UnitList } from '../models/unit-list';
+/**
+ * View metric units
+ */
+export declare class MetricsUnitsClient {
+    private httpClient;
+    /**
+     * @param {HttpClient} httpClientImplementation - You can provide custom http client as a parameter to constructor of a MetricsUnitsClient. Custom http client should implement {HttpClient} interface.
+     * @example
+     * const queryClientNodeJs = new QueryClient(yourCustomImplementation);
+     */
+    constructor(httpClientImplementation: HttpClient);
+    /**
+     * Converts a value of the given source unit into a given target unit if specified, or finds an appropriate unit if no target is specified, respecting the preferred number format if specified.
+     *
+     * **Required scope:** environment-api:metrics:read
+     * @returns Success
+     */
+    convert(config: {
+        /** The ID of the source unit. */ unitId: string;
+        /** The value to be converted. */ value: number;
+        /** The ID of the target unit. */ targetUnit?: string;
+        /** The preferred number format. Only taken into account if no target unit is specified. */ numberFormat?: string;
+        abortSignal?: AbortSignal;
+    }): Promise<UnitConversionResult>;
+    /**
+     * Gets the properties of the specified unit
+     *
+     * **Required scope:** environment-api:metrics:read
+     * @returns Success
+     */
+    unit(config: {
+        unitId: string;
+        abortSignal?: AbortSignal;
+    }): Promise<Unit>;
+    /**
+     * Lists all available units
+     *
+     * **Required scope:** environment-api:metrics:read<br/><br/>You can narrow down the output by providing filter criteria in the **unitSelector** field.
+     * @returns Success
+     */
+    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;
+        /**
+         * 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.
+         *
+         * 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<UnitList>;
+}
+export declare const metricsUnitsClient: MetricsUnitsClient;

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

@@ -0,0 +1,248 @@
+import { AbortSignal, HttpClient } from '@dynatrace-sdk/http-client';
+import { CustomDeviceCreation } from '../models/custom-device-creation';
+import { CustomDeviceCreationResult } from '../models/custom-device-creation-result';
+import { EntitiesList } from '../models/entities-list';
+import { Entity } from '../models/entity';
+import { EntityType } from '../models/entity-type';
+import { EntityTypeList } from '../models/entity-type-list';
+/**
+ * Manage monitored entities
+ */
+export declare class MonitoredEntitiesClient {
+    private httpClient;
+    /**
+     * @param {HttpClient} httpClientImplementation - You can provide custom http client as a parameter to constructor of a MonitoredEntitiesClient. Custom http client should implement {HttpClient} interface.
+     * @example
+     * const queryClientNodeJs = new QueryClient(yourCustomImplementation);
+     */
+    constructor(httpClientImplementation: HttpClient);
+    /**
+     * Gets the information about monitored entities
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + environment-api:entities:read
+     * <br/><br/>Lists entities observed within the specified timeframe along with their properties.
+     *
+     * When you query entities of the `SERVICE_METHOD` type, only the following requests are returned:
+     *
+     * * [Key requests](https://dt-url.net/a903u9s)
+     * * Top X requests that are used for [baselining](https://dt-url.net/0j23uqb)
+     * * Requests that have caused a [problem](https://dt-url.net/pf43uqg)
+     *
+     * You can limit the output by using pagination:
+     * 1. Specify the number of results per page in the **pageSize** query parameter.
+     * 2. Use the cursor from the **nextPageKey** field of the previous response in the **nextPageKey** query parameter to obtain subsequent pages.
+     * @returns Success
+     */
+    getEntities(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 entities.
+         *
+         * If not set, 50 is used.
+         */ pageSize?: number;
+        /**
+         * Defines the scope of the query. Only entities matching the specified criteria are included into 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.
+         *
+         * The field is **required** when you're querying the first page of results.
+         */ entitySelector?: 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 three days is used (`now-3d`).
+         */ 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;
+        /**
+         * Defines the list of entity properties included in the response. The ID and the name of an entity are **always** included to the response.
+         *
+         * To add properties, list them with leading plus `+`. You can specify several properties, separated by a comma (for example `fields=+lastSeenTms,+properties.BITNESS`).
+         *
+         * Use the [GET entity type](https://dt-url.net/2ka3ivt) request to fetch the list of properties available for your entity type. Fields from the **properties** object must be specified in the `properties.FIELD` format (for example, `properties.BITNESS`).
+         */ fields?: string;
+        /**
+         * Defines the ordering of the entities returned.
+         *
+         * This field is **optional**, each field has a sign prefix (+/-), which corresponds to sorting order ( + for ascending and - for descending). If no sign prefix is set, then default ascending sorting order will be applied.
+         *
+         * Currently ordering is only available for the display name (for example `sort=name or sort =+name for ascending, sort=-name for descending`)
+         */ sort?: string;
+        abortSignal?: AbortSignal;
+    }): Promise<EntitiesList>;
+    /**
+     * Gets the properties of the specified monitored entity
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + environment-api:entities:read
+     * @returns Success
+     */
+    getEntity(config: {
+        /** The ID of the required entity. */ entityId: 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 three days is used (`now-3d`).
+         */ 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;
+        /**
+         * Defines the list of entity properties included in the response. The ID and the name of an entity are **always** included to the response.
+         *
+         * To add properties, list them with leading plus `+`. You can specify several properties, separated by a comma (for example `fields=+lastSeenTms,+properties.BITNESS`).
+         *
+         * Use the [GET entity type](https://dt-url.net/2ka3ivt) request to fetch the list of properties available for your entity type. Fields from the **properties** object must be specified in the `properties.FIELD` format (for example, `properties.BITNESS`).
+         */ fields?: string;
+        abortSignal?: AbortSignal;
+    }): Promise<Entity>;
+    /**
+     * Gets a list of properties for the specified entity type
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + environment-api:entities:read
+     * @returns Success
+     */
+    getEntityType(config: {
+        /** The required entity type. */ type: string;
+        abortSignal?: AbortSignal;
+    }): Promise<EntityType>;
+    /**
+     * Gets a list of properties for all entity types
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + environment-api:entities:read
+     * <br/><br/>You can limit the output by using pagination:
+     * 1. Specify the number of results per page in the **pageSize** query parameter.
+     * 2. Use the cursor from the **nextPageKey** field of the previous response in the **nextPageKey** query parameter to obtain subsequent pages.
+     * @returns Success
+     */
+    getEntityTypes(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 entity types in a single response payload.
+         *
+         * The maximal allowed page size is 500.
+         *
+         * If not set, 50 is used.
+         */ pageSize?: number;
+        abortSignal?: AbortSignal;
+    }): Promise<EntityTypeList>;
+    /**
+     * Creates or updates a custom device
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + environment-api:entities:write
+     * @returns Success
+     */
+    pushCustomDevice(config: {
+        body: CustomDeviceCreation;
+        abortSignal?: AbortSignal;
+    }): Promise<CustomDeviceCreationResult | void>;
+}
+export declare const monitoredEntitiesClient: MonitoredEntitiesClient;

package/types/packages/client/classic-environment-v2/src/lib/apis/monitored-entities-custom-tags-api.d.ts

@@ -0,0 +1,277 @@
+import { AbortSignal, HttpClient } from '@dynatrace-sdk/http-client';
+import { AddEntityTags } from '../models/add-entity-tags';
+import { AddedEntityTags } from '../models/added-entity-tags';
+import { CustomEntityTags } from '../models/custom-entity-tags';
+import { DeletedEntityTags } from '../models/deleted-entity-tags';
+/**
+ * Manage custom tags of monitored entities
+ */
+export declare class MonitoredEntitiesCustomTagsClient {
+    private httpClient;
+    /**
+     * @param {HttpClient} httpClientImplementation - You can provide custom http client as a parameter to constructor of a MonitoredEntitiesCustomTagsClient. Custom http client should implement {HttpClient} interface.
+     * @example
+     * const queryClientNodeJs = new QueryClient(yourCustomImplementation);
+     */
+    constructor(httpClientImplementation: HttpClient);
+    /**
+     * Gets a list of custom tags applied to the specified entities
+     *
+     * **Required scope:** environment-api<br/><br/>Automatically applied tags and imported tags are not included.
+     * @returns Success
+     */
+    getTags(config: {
+        /**
+         * Specifies the entities where you want to read tags.
+         *
+         * 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.
+         */ entitySelector: 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 24 hours is used (`now-24h`).
+         */ 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;
+        abortSignal?: AbortSignal;
+    }): Promise<CustomEntityTags>;
+    /**
+     * Adds custom tags to the specified entities
+     *
+     * **Required scope:** environment-api<br/><br/>All existing tags remain unaffected.
+     * @returns Success
+     */
+    postTags(config: {
+        body: AddEntityTags;
+        /**
+         * Specifies the entities where you want to update tags.
+         *
+         * 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.
+         */ entitySelector: 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 24 hours is used (`now-24h`).
+         */ 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;
+        abortSignal?: AbortSignal;
+    }): Promise<AddedEntityTags>;
+    /**
+     * Deletes the specified tag from the specified entities
+     *
+     * **Required scope:** environment-api
+     * @returns Success
+     */
+    deleteTags(config: {
+        /**
+         * The key of the tag to be deleted.
+         *
+         * If **deleteAllWithKey** is `true`, then all tags with this key are deleted. Otherwise, only tags with exact match of key **and** value are deleted.
+         *
+         * For value-only tags, specify the value here.
+         */ key: string;
+        /**
+         * The value of the tag to be deleted. The value is ignored if **deleteAllWithKey** is `true`.
+         *
+         * For value-only tags, specify the value in the **key** parameter.
+         */ value?: string;
+        /**
+         * * If `true`, all tags with the specified key are deleted, regardless of the value.
+         * * If `false`, only tags with exact match of key **and** value are deleted.
+         *
+         * If not set, `false` is used.
+         */ deleteAllWithKey?: boolean;
+        /**
+         * Specifies the entities where you want to delete tags.
+         *
+         * 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.
+         */ entitySelector: 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 24 hours is used (`now-24h`).
+         */ 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;
+        abortSignal?: AbortSignal;
+    }): Promise<DeletedEntityTags>;
+}
+export declare const monitoredEntitiesCustomTagsClient: MonitoredEntitiesCustomTagsClient;