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

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

@@ -1,324 +0,0 @@
-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';
-import { ApiClientOptions } from './api-client-options';
-/**
- * Manage custom tags of monitored entities
- */
-export declare class MonitoredEntitiesCustomTagsClient {
-    private httpClient;
-    private shouldTransformDates;
-    /**
-     * @param {HttpClient} httpClientImplementation - You can provide custom http client as a parameter to constructor of a MonitoredEntitiesCustomTagsClient. Custom http client should implement {HttpClient} interface.
-     * @param {ApiClientOptions} [options] - Optional configuration for SDK Client.
-     * @example
-     * const monitoredEntitiesCustomTagsClientNodeJs = new MonitoredEntitiesCustomTagsClient(yourCustomImplementation);
-     */
-    constructor(httpClientImplementation: HttpClient, options?: ApiClientOptions);
-    /**
-     * Gets a list of custom tags applied to the specified entities
-     *
-     * **Required scope:** environment-api:entities:read<br/>**Required permission:** environment:roles:viewer<br/><br/>Automatically applied tags and imported tags are not included.
-     *
-     * @returns {Promise<CustomEntityTags>} Success
-     *
-     * @example <caption>Code example</caption>
-     * import { monitoredEntitiesCustomTagsClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data =
-     *   await monitoredEntitiesCustomTagsClient.getTags({
-     *     entitySelector: "...",
-     *   });
-     *
-     * @throws {ErrorEnvelopeError} Client side error. | Server side error.
-     * @throws {InvalidResponseError}
-     * @throws {ApiClientError}
-     * @throws {ClientRequestError}
-     */
-    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 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 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:entities:write<br/>**Required permission:** environment:roles:manage-settings<br/><br/>All existing tags remain unaffected.
-     *
-     * @returns {Promise<AddedEntityTags>} Success
-     *
-     * @example <caption>Code example</caption>
-     * import { monitoredEntitiesCustomTagsClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data =
-     *   await monitoredEntitiesCustomTagsClient.postTags({
-     *     entitySelector: "...",
-     *     body: { tags: [{ key: "..." }] },
-     *   });
-     *
-     * @throws {ErrorEnvelopeError} Client side error. | Server side error.
-     * @throws {InvalidResponseError}
-     * @throws {ApiClientError}
-     * @throws {ClientRequestError}
-     */
-    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 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 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:entities:write<br/>**Required permission:** environment:roles:manage-settings
-     *
-     * @returns {Promise<DeletedEntityTags>} Success
-     *
-     * @example <caption>Code example</caption>
-     * import { monitoredEntitiesCustomTagsClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data =
-     *   await monitoredEntitiesCustomTagsClient.deleteTags({
-     *     key: "...",
-     *     entitySelector: "...",
-     *   });
-     *
-     * @throws {ErrorEnvelopeError} Client side error. | Server side error.
-     * @throws {InvalidResponseError}
-     * @throws {ApiClientError}
-     * @throws {ClientRequestError}
-     */
-    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 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 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;

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

@@ -1,124 +0,0 @@
-import { AbortSignal, HttpClient } from '@dynatrace-sdk/http-client';
-import { MonitoredStates } from '../models/monitored-states';
-import { ApiClientOptions } from './api-client-options';
-/**
- * Read state of monitored entities
- */
-export declare class MonitoredEntitiesMonitoringStateClient {
-    private httpClient;
-    private shouldTransformDates;
-    /**
-     * @param {HttpClient} httpClientImplementation - You can provide custom http client as a parameter to constructor of a MonitoredEntitiesMonitoringStateClient. Custom http client should implement {HttpClient} interface.
-     * @param {ApiClientOptions} [options] - Optional configuration for SDK Client.
-     * @example
-     * const monitoredEntitiesMonitoringStateClientNodeJs = new MonitoredEntitiesMonitoringStateClient(yourCustomImplementation);
-     */
-    constructor(httpClientImplementation: HttpClient, options?: ApiClientOptions);
-    /**
-     * Lists monitoring states of entities
-     *
-     * **Required scope:** environment-api:entities:read<br/>**Required permission:** environment:roles:viewer<br/><br/>Only process group instances are supported.
-     *
-     * @returns {Promise<MonitoredStates>} Success
-     *
-     * @example <caption>Code example</caption>
-     * import { monitoredEntitiesMonitoringStateClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data =
-     *   await monitoredEntitiesMonitoringStateClient.getStates();
-     *
-     * @throws {ErrorEnvelopeError} Unavailable | Client side error. | Server side error.
-     * @throws {InvalidResponseError}
-     * @throws {ApiClientError}
-     * @throws {ClientRequestError}
-     */
-    getStates(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 monitoring states in a single response payload.
-         *
-         * The maximal allowed page size is 500.
-         *
-         * If not set, 500 is used.
-         */ pageSize?: number;
-        /**
-         * Specifies the process group instances where you're querying the state. Use the `PROCESS_GROUP_INSTANCE` entity type.
-         *
-         * 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 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<MonitoredStates>;
-}
-export declare const monitoredEntitiesMonitoringStateClient: MonitoredEntitiesMonitoringStateClient;

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

@@ -1,199 +0,0 @@
-import { AbortSignal, HttpClient } from '@dynatrace-sdk/http-client';
-import { EntityShortRepresentation } from '../models/entity-short-representation';
-import { NetworkZone } from '../models/network-zone';
-import { NetworkZoneConnectionStatistics } from '../models/network-zone-connection-statistics';
-import { NetworkZoneList } from '../models/network-zone-list';
-import { NetworkZoneSettings } from '../models/network-zone-settings';
-import { ApiClientOptions } from './api-client-options';
-/**
- * Manage network zones
- */
-export declare class NetworkZonesClient {
-    private httpClient;
-    private shouldTransformDates;
-    /**
-     * @param {HttpClient} httpClientImplementation - You can provide custom http client as a parameter to constructor of a NetworkZonesClient. Custom http client should implement {HttpClient} interface.
-     * @param {ApiClientOptions} [options] - Optional configuration for SDK Client.
-     * @example
-     * const networkZonesClientNodeJs = new NetworkZonesClient(yourCustomImplementation);
-     */
-    constructor(httpClientImplementation: HttpClient, options?: ApiClientOptions);
-    /**
-     * Gets the global configuration of network zones
-     *
-     * **Required scope:** environment-api:network-zones:read<br/>**Required permission:** environment:roles:viewer
-     *
-     * @returns {Promise<NetworkZoneSettings>} Success
-     *
-     * @example <caption>Code example</caption>
-     * import { networkZonesClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data =
-     *   await networkZonesClient.getNetworkZoneSettings();
-     *
-     * @throws {ErrorEnvelopeError} Client side error. | Server side error.
-     * @throws {InvalidResponseError}
-     * @throws {ApiClientError}
-     * @throws {ClientRequestError}
-     */
-    getNetworkZoneSettings(config?: {
-        abortSignal?: AbortSignal;
-    } | AbortSignal): Promise<NetworkZoneSettings>;
-    /**
-     * Updates the global configuration of network zones
-     *
-     * **Required scope:** environment-api:network-zones:write<br/>**Required permission:** environment:roles:manage-settings
-     *
-     * @example <caption>Code example</caption>
-     * import { networkZonesClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data =
-     *   await networkZonesClient.updateNetworkZoneSettings({
-     *     body: {},
-     *   });
-     *
-     * @throws {ErrorEnvelopeError} Client side error. | Server side error.
-     * @throws {InvalidResponseError}
-     * @throws {ApiClientError}
-     * @throws {ClientRequestError}
-     */
-    updateNetworkZoneSettings(config: {
-        body: NetworkZoneSettings;
-        abortSignal?: AbortSignal;
-    }): Promise<void>;
-    /**
-     * Lists all existing network zones
-     *
-     * **Required scope:** environment-api:network-zones:read<br/>**Required permission:** environment:roles:viewer
-     *
-     * @returns {Promise<NetworkZoneList>} Success
-     *
-     * @example <caption>Code example</caption>
-     * import { networkZonesClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data = await networkZonesClient.getAllNetworkZones();
-     *
-     * @throws {ErrorEnvelopeError} Client side error. | Server side error.
-     * @throws {InvalidResponseError}
-     * @throws {ApiClientError}
-     * @throws {ClientRequestError}
-     */
-    getAllNetworkZones(config?: {
-        abortSignal?: AbortSignal;
-    } | AbortSignal): Promise<NetworkZoneList>;
-    /**
-     * Gets parameters of the specified network zone
-     *
-     * **Required scope:** environment-api:network-zones:read<br/>**Required permission:** environment:roles:viewer
-     *
-     * @returns {Promise<NetworkZone>} Success
-     *
-     * @example <caption>Code example</caption>
-     * import { networkZonesClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data = await networkZonesClient.getSingleNetworkZone({
-     *   id: "...",
-     * });
-     *
-     * @throws {ErrorEnvelopeError} Client side error. | Server side error.
-     * @throws {InvalidResponseError}
-     * @throws {ApiClientError}
-     * @throws {ClientRequestError}
-     */
-    getSingleNetworkZone(config: {
-        /** The ID of the required network zone. */ id: string;
-        abortSignal?: AbortSignal;
-    }): Promise<NetworkZone>;
-    /**
-     * Updates an existing network zone or creates a new one
-     *
-     * **Required scope:** environment-api:network-zones:write<br/>**Required permission:** environment:roles:manage-settings<br/><br/>If the network zone with the specified ID does not exist, a new network zone is created.
-     *
-     *  The ID is not case sensitive. Dynatrace stores the ID in lowercase.
-     *
-     * @returns {Promise<EntityShortRepresentation | void>} Success. The new network zone has been created. The response body contains the ID of the new network zone.
-     *
-     * @example <caption>Code example</caption>
-     * import { networkZonesClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data =
-     *   await networkZonesClient.createOrUpdateNetworkZone({
-     *     id: "...",
-     *     body: {},
-     *   });
-     *
-     * @throws {ErrorEnvelopeError} Failed. The input is invalid. | Client side error. | Server side error.
-     * @throws {InvalidResponseError}
-     * @throws {ApiClientError}
-     * @throws {ClientRequestError}
-     */
-    createOrUpdateNetworkZone(config: {
-        body: NetworkZone;
-        /**
-         * The ID of the network zone to be updated.
-         *
-         *  If you set the ID in the body as well, it must match this ID.
-         *
-         *  The ID is not case sensitive. Dynatrace stores the ID in lowercase.
-         */ id: string;
-        abortSignal?: AbortSignal;
-    }): Promise<EntityShortRepresentation | void>;
-    /**
-     * Deletes the specified network zone
-     *
-     * **Required scope:** environment-api:network-zones:write<br/>**Required permission:** environment:roles:manage-settings<br/><br/>You can only delete an empty network zone (a zone that no ActiveGate or OneAgent is using).
-     *
-     *  If the network zone is used as an alternative zone for any OneAgent, it will be automatically removed from the list of possible alternatives.
-     *
-     * @example <caption>Code example</caption>
-     * import { networkZonesClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data = await networkZonesClient.deleteNetworkZone({
-     *   id: "...",
-     * });
-     *
-     * @throws {ErrorEnvelopeError} Failed. See error message in the response body for details. | Client side error. | Server side error.
-     * @throws {InvalidResponseError}
-     * @throws {ApiClientError}
-     * @throws {ClientRequestError}
-     */
-    deleteNetworkZone(config: {
-        /** The ID of the network zone to be deleted. */ id: string;
-        abortSignal?: AbortSignal;
-    }): Promise<void>;
-    /**
-     * Gets the statistics about hosts using the network zone
-     *
-     * **Required scope:** environment-api:network-zones:read<br/>**Required permission:** environment:roles:manage-settings
-     *
-     * @returns {Promise<NetworkZoneConnectionStatistics>} Success
-     *
-     * @example <caption>Code example</caption>
-     * import { networkZonesClient } from "@dynatrace-sdk/client-classic-environment-v2";
-     *
-     * const data = await networkZonesClient.getHostStats({
-     *   id: "...",
-     * });
-     *
-     * @throws {ErrorEnvelopeError} Client side error. | Server side error.
-     * @throws {InvalidResponseError}
-     * @throws {ApiClientError}
-     * @throws {ClientRequestError}
-     */
-    getHostStats(config: {
-        /** The ID of the required network zone. */ id: string;
-        /**
-         * Filters the resulting set of hosts:
-         *
-         * * `all`: All hosts using the zone.
-         * * `configuredButNotConnectedOnly`: Hosts from the network zone that use other zones.
-         * * `connectedAsAlternativeOnly`: Hosts that use the network zone as an alternative.
-         * * `connectedAsFailoverOnly`: Hosts from other zones that use the zone (not configured as an alternative) even though ActiveGates of higher priority are available.
-         * * `connectedAsFailoverWithoutOwnActiveGatesOnly`: Hosts from other zones that use the zone (not configured as an alternative) and **no** ActiveGates of higher priority are available.
-         *
-         * If not set, `all` is used.
-         */ filter?: 'all' | 'configuredButNotConnectedOnly' | 'connectedAsAlternativeOnly' | 'connectedAsFailoverOnly' | 'connectedAsFailoverWithoutOwnActiveGatesOnly';
-        abortSignal?: AbortSignal;
-    }): Promise<NetworkZoneConnectionStatistics>;
-}
-export declare const networkZonesClient: NetworkZonesClient;