@dynatrace-sdk/client-classic-environment-v2 5.2.3 → 6.1.0

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

@@ -1,521 +0,0 @@
-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';
-import { SecurityContextDtoImpl } from '../models/security-context-dto-impl';
-import { SecurityContextResultDto } from '../models/security-context-result-dto';
-import { ApiClientOptions } from './api-client-options';
-/**
- * Manage monitored entities - Deprecated in SaaS, use DQL (Smartscape on Grail) and OpenPipeline instead
- */
-export declare class MonitoredEntitiesClient {
-    private httpClient;
-    private shouldTransformDates;
-    /**
-     * @param {HttpClient} httpClientImplementation - You can provide custom http client as a parameter to constructor of a MonitoredEntitiesClient. Custom http client should implement {HttpClient} interface.
-     * @param {ApiClientOptions} [options] - Optional configuration for SDK Client.
-     * @example
-     * const monitoredEntitiesClientNodeJs = new MonitoredEntitiesClient(yourCustomImplementation);
-     */
-    constructor(httpClientImplementation: HttpClient, options?: ApiClientOptions);
-    /**
-     * Gets the information about monitored entities
-     *
-     * **Required scope:** environment-api:entities:read<br/>**Required permission:** environment:roles:viewer<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.
-     *
-     * @deprecated
-     *
-     * @returns {Promise<EntitiesList>} Success
-     *
-     * @example <caption>Code example</caption>
-     * import { monitoredEntitiesClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data = await monitoredEntitiesClient.getEntities();
-     *
-     * @throws {ErrorEnvelopeError} Client side error. | Server side error.
-     * @throws {InvalidResponseError}
-     * @throws {ApiClientError}
-     * @throws {ClientRequestError}
-     */
-    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 more 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 argument 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>()`. This 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 the response.
-         *
-         * The maximum 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`).
-         *
-         * When requesting large amounts of relationship fields, throttling can apply.
-         */ 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>;
-    /**
-     * Creates or updates a custom device
-     *
-     * **Required scope:** environment-api:entities:write<br/>**Required permission:** environment:roles:manage-settings
-     *
-     * @deprecated
-     *
-     * @returns {Promise<CustomDeviceCreationResult | void>} Success
-     *
-     * @example <caption>Code example</caption>
-     * import { monitoredEntitiesClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data = await monitoredEntitiesClient.pushCustomDevice(
-     *   { body: { customDeviceId: "...", displayName: "..." } },
-     * );
-     *
-     * @throws {ErrorEnvelopeError} Client side error. | Server side error.
-     * @throws {InvalidResponseError}
-     * @throws {ApiClientError}
-     * @throws {ClientRequestError}
-     */
-    pushCustomDevice(config: {
-        body: CustomDeviceCreation;
-        /** If true, it will be handled as if it was created via UI. It will be refreshed automatically and won't age out. */ uiBased?: boolean;
-        abortSignal?: AbortSignal;
-    }): Promise<CustomDeviceCreationResult | void>;
-    /**
-     * Sets the given security context for all entities matching the entity selector.
-     *
-     * **Required scope:** settings:objects:write<br/>**One of the following permissions is required:**
-     * + environment:roles:manage-settings
-     * + settings:objects:write
-     *
-     * <br/><br/>Matching entities will have a management zone assigned, if the given security context matches the name of an already existing management zone.
-     * This endpoint does not create a new management zone, if there is no management zone with the provided name.
-     * Automatic management zone rules will not apply to entities with a set security context. It will need to be removed, to have them apply again.
-     *
-     * @deprecated
-     *
-     * @returns {Promise<SecurityContextResultDto>} Success
-     *
-     * @example <caption>Code example</caption>
-     * import { monitoredEntitiesClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data =
-     *   await monitoredEntitiesClient.setSecurityContext({
-     *     entitySelector: "...",
-     *     body: {},
-     *   });
-     *
-     * @throws {ErrorEnvelopeError} Client side error. | Server side error.
-     * @throws {InvalidResponseError}
-     * @throws {ApiClientError}
-     * @throws {ClientRequestError}
-     */
-    setSecurityContext(config: {
-        body: SecurityContextDtoImpl;
-        /**
-         * Defines the scope of the entities to set the security context for. Only entities that can have management zones are considered for this operation
-         *
-         * 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 more 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 argument 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>()`. This 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 the response.
-         *
-         * The maximum 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 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;
-        abortSignal?: AbortSignal;
-    }): Promise<SecurityContextResultDto>;
-    /**
-     * Deletes the security context for all entities matching the entity selector.
-     *
-     * **Required scope:** settings:objects:write<br/>**One of the following permissions is required:**
-     * + environment:roles:manage-settings
-     * + settings:objects:write
-     *
-     * <br/><br/>Automatic management zone rules will apply again to entities without a security context.
-     *
-     * @deprecated
-     *
-     * @returns {Promise<SecurityContextResultDto>} Success
-     *
-     * @example <caption>Code example</caption>
-     * import { monitoredEntitiesClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data =
-     *   await monitoredEntitiesClient.deleteSecurityContext({
-     *     entitySelector: "...",
-     *   });
-     *
-     * @throws {ErrorEnvelopeError} Client side error. | Server side error.
-     * @throws {InvalidResponseError}
-     * @throws {ApiClientError}
-     * @throws {ClientRequestError}
-     */
-    deleteSecurityContext(config: {
-        /**
-         * Defines the scope of the entities to set the security context for. Only entities that can have management zones are considered for this operation
-         *
-         * 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 more 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 argument 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>()`. This 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 the response.
-         *
-         * The maximum 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 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;
-        abortSignal?: AbortSignal;
-    }): Promise<SecurityContextResultDto>;
-    /**
-     * Gets the properties of the specified monitored entity
-     *
-     * **Required scope:** environment-api:entities:read<br/>**Required permission:** environment:roles:viewer
-     *
-     * @deprecated
-     *
-     * @returns {Promise<Entity>} Success
-     *
-     * @example <caption>Code example</caption>
-     * import { monitoredEntitiesClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data = await monitoredEntitiesClient.getEntity({
-     *   entityId: "...",
-     * });
-     *
-     * @throws {ErrorEnvelopeError} Client side error. | Server side error.
-     * @throws {InvalidResponseError}
-     * @throws {ApiClientError}
-     * @throws {ClientRequestError}
-     */
-    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`).
-         *
-         * When requesting large amounts of relationship fields, throttling can apply.
-         */ fields?: string;
-        abortSignal?: AbortSignal;
-    }): Promise<Entity>;
-    /**
-     * Gets a list of properties for all entity types
-     *
-     * **Required scope:** environment-api:entities:read<br/>**Required permission:** environment:roles:viewer<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.
-     *
-     * @deprecated
-     *
-     * @returns {Promise<EntityTypeList>} Success
-     *
-     * @example <caption>Code example</caption>
-     * import { monitoredEntitiesClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data = await monitoredEntitiesClient.getEntityTypes();
-     *
-     * @throws {ErrorEnvelopeError} Client side error. | Server side error.
-     * @throws {InvalidResponseError}
-     * @throws {ApiClientError}
-     * @throws {ClientRequestError}
-     */
-    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>;
-    /**
-     * Gets a list of properties for the specified entity type
-     *
-     * **Required scope:** environment-api:entities:read<br/>**Required permission:** environment:roles:viewer
-     *
-     * @deprecated
-     *
-     * @returns {Promise<EntityType>} Success
-     *
-     * @example <caption>Code example</caption>
-     * import { monitoredEntitiesClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data = await monitoredEntitiesClient.getEntityType({
-     *   type: "...",
-     * });
-     *
-     * @throws {ErrorEnvelopeError} Client side error. | Server side error.
-     * @throws {InvalidResponseError}
-     * @throws {ApiClientError}
-     * @throws {ClientRequestError}
-     */
-    getEntityType(config: {
-        /** The required entity type. */ type: string;
-        abortSignal?: AbortSignal;
-    }): Promise<EntityType>;
-}
-export declare const monitoredEntitiesClient: MonitoredEntitiesClient;