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

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

@@ -0,0 +1,354 @@
+import { AbortSignal, HttpClient } from '@dynatrace-sdk/http-client';
+import { RemediationItemList } from '../models/remediation-item-list';
+import { RemediationItemMuteStateChange } from '../models/remediation-item-mute-state-change';
+import { SecurityProblemDetails } from '../models/security-problem-details';
+import { SecurityProblemEventsList } from '../models/security-problem-events-list';
+import { SecurityProblemList } from '../models/security-problem-list';
+import { SecurityProblemMute } from '../models/security-problem-mute';
+import { SecurityProblemUnmute } from '../models/security-problem-unmute';
+import { VulnerableFunctionsContainer } from '../models/vulnerable-functions-container';
+/**
+ * Manage security problems
+ */
+export declare class SecurityProblemsClient {
+    private httpClient;
+    /**
+     * @param {HttpClient} httpClientImplementation - You can provide custom http client as a parameter to constructor of a SecurityProblemsClient. Custom http client should implement {HttpClient} interface.
+     * @example
+     * const queryClientNodeJs = new QueryClient(yourCustomImplementation);
+     */
+    constructor(httpClientImplementation: HttpClient);
+    /**
+     * Lists all events of a security problem | maturity=EARLY_ADOPTER
+     *
+     * **Required scope:** environment-api:security-problems:read
+     * @returns Success. The response contains the list of security problem events.
+     */
+    getEventsForSecurityProblem(config: {
+        /** The ID of the required security problem. */ id: 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 thirty days is used (`now-30d`).
+         */ 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<SecurityProblemEventsList>;
+    /**
+     * Lists remediation items of a third-party security problem
+     *
+     * **Required scope:** environment-api:security-problems:read
+     * @returns Success. The response contains the list of remediation items of a problem.
+     */
+    getRemediationItems(config: {
+        /** The ID of the required third-party security problem. */ id: string;
+        /**
+         * Defines the scope of the query. Only remediable entities matching the specified criteria are included in the response.
+         *
+         * You can add one or more of the following criteria. Values are *not* case-sensitive and the `EQUALS` operator is used unless otherwise specified.
+         *
+         * * Vulnerability state: `vulnerabilityState("value")`. Find the possible values in the description of the **vulnerabilityState** field of the response. If not set, all entities are returned.
+         * * Muted: `muted("value")`. Possible values are `TRUE` or `FALSE`.
+         * * Reachable data asset assessment: `assessment.dataAssets("value")` Possible values are `REACHABLE`, and `NOT_DETECTED`.
+         * * Network exposure assessment: `assessment.exposure("value")` Possible values are `PUBLIC_NETWORK`, and `NOT_DETECTED`.
+         * * Vulnerable function usage assessment: `assessment.vulnerableFunctionUsage("value")` Possible values are `IN_USE`, and `NOT_IN_USE`.
+         * * Vulnerable function in use contains: `assessment.vulnerableFunctionInUseContains("value")`. Possible values are `class::function`, `class::` and `function`. The `CONTAINS` operator is used. Only vulnerable functions in use are considered.
+         * * Assessment accuracy: `assessment.accuracy("value")` Possible values are `FULL` and `REDUCED`.
+         * * Entity name contains: `entityNameContains("value-1")`. The `CONTAINS` operator is used.
+         *
+         * To set several criteria, separate them with a comma (`,`). Only results matching **all** criteria are included in the response.
+         *
+         * Specify the value of a criterion as a quoted string. The following special characters must be escaped with a tilde (`~`) inside quotes:
+         * * Tilde `~`
+         * * Quote `"`
+         */ remediationItemSelector?: string;
+        abortSignal?: AbortSignal;
+    }): Promise<RemediationItemList>;
+    /**
+     * Gets parameters of a security problem
+     *
+     * **Required scope:** environment-api:security-problems:read
+     * @returns Success. The response contains parameters of the security problem.
+     */
+    getSecurityProblem(config: {
+        /** The ID of the required security problem. */ id: string;
+        /**
+         * A list of additional security problem properties you can add to the response.
+         *
+         * The following properties are available (all other properties are always included and you can't remove them from the response):
+         *
+         * * `riskAssessment`: A risk assessment of the security problem.
+         * * `managementZones`: The management zone where the security problem occurred.
+         * * `codeLevelVulnerabilityDetails`: Details of the code-level vulnerability.
+         * * `description`: The description of the vulnerability.
+         * * `events`: The security problem's last 10 events within the last 365 days, sorted from newest to oldest.
+         * * `vulnerableComponents`: A list of vulnerable components of the security problem within the provided filter range.
+         * * `affectedEntities`: A list of affected entities of the security problem within the provided filter range.
+         * * `exposedEntities`: A list of exposed entities of the security problem within the provided filter range.
+         * * `reachableDataAssets`: A list of data assets reachable by affected entities of the security problem within the provided filter range.
+         * * `relatedEntities`: A list of related entities of the security problem within the provided filter range.
+         * * `relatedContainerImages`: A list of related container images of the security problem within the provided filter range.
+         * * `relatedAttacks`: A list of attacks detected on the exposed security problem.
+         *
+         * To add properties, specify them in a comma-separated list and prefix each property with a plus (for example, `+riskAssessment,+managementZones`).
+         */ fields?: string;
+        /**
+         * Based on the timeframe start the affected-, related- and vulnerable entities are being calculated.
+         * 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 default timeframe start of 24 hours in the past is used (`now-24h`).
+         *
+         * The timeframe start must not be older than 365 days.
+         */ from?: string;
+        abortSignal?: AbortSignal;
+    }): Promise<SecurityProblemDetails>;
+    /**
+     * Lists all security problems
+     *
+     * **Required scope:** environment-api:security-problems:read
+     * @returns Success. The response contains the list of security problems.
+     */
+    getSecurityProblems(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 security problems in a single response payload.
+         *
+         * The maximal allowed page size is 500.
+         *
+         * If not set, 100 is used.
+         */ pageSize?: number;
+        /**
+         * Defines the scope of the query. Only security problems matching the specified criteria are included in the response.
+         *
+         * You can add one or more of the following criteria. Values are *not* case-sensitive and the `EQUALS` operator is used unless otherwise specified.
+         *
+         * * Status: `status("value")`. Find the possible values in the description of the **status** field of the response. If not set, all security problems are returned.
+         * * Muted: `muted("value")`. Possible values are `TRUE` or `FALSE`.
+         * * Risk level: `riskLevel("value")`. The Davis risk level. Find the possible values in the description of the **riskLevel** field of the response.
+         * * Minimum risk score: `minRiskScore("5.5")`. The Davis minimum risk score. The `GREATER THAN OR EQUAL TO` operator is used. Specify a number between `1.0` and `10.0`.
+         * * Maximum risk score: `maxRiskScore("5.5")`. The Davis maximum risk score. The `LESS THAN` operator is used. Specify a number between `1.0` and `10.0`.
+         * * Base risk level: `baseRiskLevel("value")`. The Base risk level from the CVSS. Find the possible values in the description of the **riskLevel** field of the response.
+         * * Minimum base risk score: `minBaseRiskScore("5.5")`. The minimum base risk score from the CVSS. The `GREATER THAN OR EQUAL TO` operator is used. Specify a number between `1.0` and `10.0`.
+         * * Maximum base risk score: `maxBaseRiskScore("5.5")`. The maximum base risk score from the CVSS. The `LESS THAN` operator is used. Specify a number between `1.0` and `10.0`.
+         * * External vulnerability ID contains: `externalVulnerabilityIdContains("id-1")`. The `CONTAINS` operator is used. Maximum value length is 48 characters.
+         * * External vulnerability ID: `externalVulnerabilityId("id-1","id-2")`.
+         * * CVE ID: `cveId("id")`.
+         * * Risk assessment `riskAssessment("value-1","value-2")` Possible values are `EXPOSED`, `SENSITIVE`, `EXPLOIT`, `VULNERABLE_FUNCTION_IN_USE` and `ACCURACY_REDUCED`.
+         * * Related host ID: `relatedHostIds("value-1", "value-2")`. Specify Dynatrace entity IDs here.
+         * * Related host name: `relatedHostNames("value-1", "value-2")`. Values are case-sensitive.
+         * * Related host name contains: `relatedHostNameContains("value-1")`. The `CONTAINS` operator is used.
+         * * Related Kubernetes cluster ID: `relatedKubernetesClusterIds("value-1", "value-2")`. Specify Dynatrace entity IDs here.
+         * * Related Kubernetes cluster name: `relatedKubernetesClusterNames("value-1", "value-2")`. Values are case-sensitive.
+         * * Related Kubernetes cluster name contains: `relatedKubernetesClusterNameContains("value-1")`. The `CONTAINS` operator is used.
+         * * Related Kubernetes workload ID: `relatedKubernetesWorkloadIds("value-1", "value-2")`. Specify Dynatrace entity IDs here.
+         * * Related Kubernetes workload name: `relatedKubernetesWorkloadNames("value-1", "value-2")`. Values are case-sensitive.
+         * * Related Kubernetes workload name contains: `relatedKubernetesWorkloadNameContains("value-1")`. The `CONTAINS` operator is used.
+         * * Management zone ID: `managementZoneIds("mzId-1","mzId-2")`.
+         * * Management zone name: `managementZones("name-1","name-2")`. Values are case-sensitive.
+         * * Affected process group ID: `affectedPgIds("pgId-1", "pgId-2")`. Specify Dynatrace entity IDs here.
+         * * Affected process group name: `affectedPgNames("name-1", "name-2")`. Values are case-sensitive.
+         * * Affected process group name contains: `affectedPgNameContains("name-1")`. The `CONTAINS` operator is used.
+         * * Vulnerable component ID: `vulnerableComponentIds("componentId-1", "componentId-2")`. Specify component IDs here.
+         * * Vulnerable component name: `vulnerableComponentNames("name-1", "name-2")`. Values are case-sensitive.
+         * * Vulnerable component name contains: `vulnerableComponentNameContains("name-1")`. The `CONTAINS` operator is used.
+         * * Host tags: `hostTags("hostTag-1")`. The `CONTAINS` operator is used. Maximum value length is 48 characters.
+         * * Process group tags: `pgTags("pgTag-1")`. The `CONTAINS` operator is used. Maximum value length is 48 characters.
+         * * Process group instance tags: `pgiTags("pgiTag-1")`. The `CONTAINS` operator is used. Maximum value length is 48 characters.
+         * * Tags: `tags("tag-1")`. The `CONTAINS` operator is used. This selector picks hosts, process groups, and process group instances at the same time. Maximum value length is 48 characters.
+         * * Display ID: `displayIds("S-1234","S-5678")`. The `EQUALS` operator is used.
+         * * Technology: `technology("technology-1","technology-2")`. Find the possible values in the description of the **technology** field of the response. The `EQUALS` operator is used.
+         * * Vulnerability type: `vulnerabilityType("type-1","type-2")`. Possible values are `THIRD_PARTY`, `CODE_LEVEL`, `RUNTIME`.
+         *
+         * Risk score and risk category are mutually exclusive (cannot be used at the same time).
+         *
+         * To set several criteria, separate them with a comma (`,`). Only results matching **all** criteria are included in the response.
+         *
+         * Specify the value of a criterion as a quoted string. The following special characters must be escaped with a tilde (`~`) inside quotes:
+         * * Tilde `~`
+         * * Quote `"`
+         */ securityProblemSelector?: string;
+        /**
+         * Specifies one or more fields for sorting the security problem list. Multiple fields can be concatenated using a comma (`,`) as a separator (e.g. `+status,-timestamp`).
+         *
+         * You can sort by the following properties with a sign prefix for the sorting order.
+         *
+         * * `status`: The security problem status (`+` open first or `-` resolved first)
+         * * `muted`: The security problem mute state (`+` unmuted first or `-` muted first)
+         * * `technology`: The security problem technology
+         * * `firstSeenTimestamp`: The timestamp of the first occurrence of the security problem (`+` new problems first or `-` old problems first)
+         * * `lastUpdatedTimestamp`: The timestamp of the last update of the security problem (`+` recently updated problems first or `-`  earlier updated problems first)
+         * * `securityProblemId`: The auto-generated ID of the security problem (`+` lower number first or `-` higher number first)
+         * * `externalVulnerabilityId`: The ID of the external vulnerability (`+` lower number first or `-` higher number first)
+         * * `displayId`: The display ID (`+` lower number first or `-` higher number first)
+         * * `riskAssessment.riskScore`: The Davis security score (`+` lower score first or `-` higher score first)
+         * * `riskAssessment.riskLevel`: The Davis security level (`+` lower level first or `-` higher level first)
+         * * `riskAssessment.exposure`: Whether the problem is exposed to the internet
+         * * `riskAssessment.dataAssets`: Whether data assets are affected
+         * * `riskAssessment.vulnerableFunctionUsage`: Whether vulnerable functions are used
+         * * `riskAssessment.assessmentAccuracy`: The assessments accuracy (`+` less accuracy first or `-` more accuracy first)
+         *
+         * If no prefix is set, `+` is used.
+         */ sort?: string;
+        /**
+         * A list of additional security problem properties you can add to the response.
+         *
+         * The following properties are available (all other properties are always included and you can't remove them from the response):
+         *
+         * * `riskAssessment`: A risk assessment of the security problem.
+         * * `managementZones`: The management zone where the security problem occurred.
+         * * `codeLevelVulnerabilityDetails`: Details of the code-level vulnerability.
+         *
+         * To add properties, specify them in a comma-separated list and prefix each property with a plus (for example, `+riskAssessment,+managementZones`).
+         */ fields?: 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 thirty days is used (`now-30d`).
+         */ 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.
+         *
+         * The end of the timeframe must not be older than 365 days.
+         */ to?: string;
+        abortSignal?: AbortSignal;
+    }): Promise<SecurityProblemList>;
+    /**
+     * Lists all vulnerable functions and their usage for a third-party security problem
+     *
+     * **Required scope:** environment-api:security-problems:read
+     * @returns Success. The response contains the list of vulnerable functions.
+     */
+    getVulnerableFunctions(config: {
+        /** The ID of the required third-party security problem. */ id: string;
+        /**
+         * Defines the scope of the query. Only vulnerable functions matching the specified criteria are included in the response.
+         *
+         * You can add the following criteria. Values are *not* case sensitive and the `EQUALS` operator is used unless otherwise specified.
+         *
+         * * Management zone ID: `managementZoneIds("mzId-1","mzId-2")`.
+         * * Management zone name: `managementZones("name-1","name-2")`. Values are case sensitive.
+         * * Process group ID: `processGroupIds("pgId-1", "pgId-2")`. Specify Dynatrace entity IDs here.
+         * * Process group name: `processGroupNames("name-1", "name-2")`. Values are case sensitive.
+         * * Process group name contains: `processGroupNameContains("name-1")`. The `CONTAINS` operator is used.
+         *
+         * Specify the value of a criterion as a quoted string. The following special characters must be escaped with a tilde (`~`) inside quotes:
+         * * Tilde `~`
+         * * Quote `"`
+         */ vulnerableFunctionsSelector?: string;
+        /**
+         * Defines additional grouping types in which vulnerable functions should be displayed.
+         *
+         * You can add one of the following grouping types.
+         *
+         * * Process group: `PROCESS_GROUP`
+         */ groupBy?: string;
+        abortSignal?: AbortSignal;
+    }): Promise<VulnerableFunctionsContainer>;
+    /**
+     * Mutes a security problem
+     *
+     * **Required scope:** environment-api:security-problems:write
+     */
+    muteSecurityProblem(config: {
+        body: SecurityProblemMute;
+        /** The ID of the required security problem. */ id: string;
+        abortSignal?: AbortSignal;
+    }): Promise<void>;
+    /**
+     * Sets the mute state of a remediation item | maturity=EARLY_ADOPTER
+     *
+     * **Required scope:** environment-api:security-problems:write
+     */
+    setRemediationItemMuteState(config: {
+        body: RemediationItemMuteStateChange;
+        /** The ID of the required third-party security problem. */ id: string;
+        /** The ID of the remediation item. */ itemId: string;
+        abortSignal?: AbortSignal;
+    }): Promise<void>;
+    /**
+     * Un-mutes a security problem
+     *
+     * **Required scope:** environment-api:security-problems:write
+     */
+    unmuteSecurityProblem(config: {
+        body: SecurityProblemUnmute;
+        /** The ID of the required security problem. */ id: string;
+        abortSignal?: AbortSignal;
+    }): Promise<void>;
+}
+export declare const securityProblemsClient: SecurityProblemsClient;

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

@@ -0,0 +1,269 @@
+import { AbortSignal, HttpClient } from '@dynatrace-sdk/http-client';
+import { AbstractSloAlertDto } from '../models/abstract-slo-alert-dto';
+import { CreateAlertQueryTimeFrame } from '../models/create-alert-query-time-frame';
+import { GetSloByIdQueryTimeFrame } from '../models/get-slo-by-id-query-time-frame';
+import { GetSloQueryEnabledSlos } from '../models/get-slo-query-enabled-slos';
+import { GetSloQueryEvaluate } from '../models/get-slo-query-evaluate';
+import { GetSloQueryTimeFrame } from '../models/get-slo-query-time-frame';
+import { SLOs } from '../models/sl-os';
+import { SLO } from '../models/slo';
+import { SloConfigItemDtoImpl } from '../models/slo-config-item-dto-impl';
+/**
+ * Manage SLOs
+ */
+export declare class ServiceLevelObjectivesClient {
+    private httpClient;
+    /**
+     * @param {HttpClient} httpClientImplementation - You can provide custom http client as a parameter to constructor of a ServiceLevelObjectivesClient. Custom http client should implement {HttpClient} interface.
+     * @example
+     * const queryClientNodeJs = new QueryClient(yourCustomImplementation);
+     */
+    constructor(httpClientImplementation: HttpClient);
+    /**
+     * Creates an alert of the provided alert type for an SLO
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + environment-api:slo:write
+     */
+    createAlert(config: {
+        body: AbstractSloAlertDto;
+        /** The ID of the required SLO. */ id: string;
+        /**
+         * The start of the requested timeframe.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * If not set, the relative timeframe of two weeks is used (`now-2w`).
+         */ from?: string;
+        /**
+         * The end of the requested timeframe.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * If not set, the current timestamp is used.
+         */ to?: string;
+        /**
+         * The timeframe to calculate the SLO values:
+         *
+         * * `CURRENT`: SLO's own timeframe.
+         * * `GTF`: timeframe specified by **from** and **to** parameters.
+         *
+         * If not set, the `CURRENT` value is used.
+         */ timeFrame?: CreateAlertQueryTimeFrame;
+        abortSignal?: AbortSignal;
+    }): Promise<void>;
+    /**
+     * Lists all available SLOs along with calculated values
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + environment-api:slo:read
+     * <br/><br/>By default the values are calculated for the SLO's own timeframe. You can use a custom timeframe:
+     *
+     * 1. Set the **timeFrame** parameter to `GTF`.
+     * 2. Provide the timeframe in **from** and **to** parameters.
+     * @returns Success. The response contains the parameters and calculated values of the requested SLO.
+     */
+    getSlo(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 SLOs in a single response payload.
+         *
+         * The maximal allowed page size is 10000.
+         *
+         * If not set, 10 is used.
+         */ pageSize?: number;
+        /**
+         * The start of the requested timeframe.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * If not set, the relative timeframe of two weeks is used (`now-2w`).
+         */ from?: string;
+        /**
+         * The end of the requested timeframe.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * If not set, the current timestamp is used.
+         */ to?: string;
+        /**
+         * The scope of the query. Only SLOs matching the provided criteria are included in the response.
+         *
+         * You can add one or several of the criteria listed below.
+         * * SLO ID: id("id-1","id-2").
+         * * Name: name("name"). Filters for an SLO with the given name. The filter is case-sensitive.
+         * * Health state: healthState("HEALTHY") or healthState("UNHEALTHY"). You can specify only one health state.
+         * * Text: text("value"). Filters for all SLOs that contain the given value in their name or description. The filter is case-insensitive.
+         * * Problem: problemDisplayName("value"). Filters for all SLOs that are related to a given problem display name (e.g. P-12345).
+         *
+         * To set several criteria, separate them with comma (,). Only results matching all criteria are included in the response.
+         * e.g., .../api/v2/slo?sloSelector=name("Service Availability"), .../api/v2/slo?sloSelector=id("id"), .../api/v2/slo?sloSelector=text("Description"),healthState("HEALTHY").
+         *
+         * The special characters ~ and " need to be escaped using a ~ (e.g. double quote search text("~"").
+         */ sloSelector?: string;
+        /**
+         * The sorting of SLO entries:
+         * * `name`: Names in ascending order.
+         * * `-name`: Names in descending order.
+         *
+         * If not set, the ascending order is used.
+         */ sort?: string;
+        /**
+         * The timeframe to calculate the SLO values:
+         *
+         * * `CURRENT`: SLO's own timeframe.
+         * * `GTF`: timeframe specified by **from** and **to** parameters.
+         *
+         * If not set, the `CURRENT` value is used.
+         */ timeFrame?: GetSloQueryTimeFrame;
+        /** Get your SLOs (`false`) or a set of demo SLOs (`true`). */ demo?: boolean;
+        /** Get your SLOs without them being evaluated (`false`) or with evaluations (`true`) with maximum `pageSize` of 25. */ evaluate?: GetSloQueryEvaluate;
+        /** Get your enabled SLOs (`true`), disabled ones (`false`) or both enabled and disabled ones (`all`). */ enabledSlos?: GetSloQueryEnabledSlos;
+        /** Get your global SLOs (`true`) regardless of the selected filter or filter them out (`false`). */ showGlobalSlos?: boolean;
+        abortSignal?: AbortSignal;
+    }): Promise<SLOs>;
+    /**
+     * Creates a new SLO
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + environment-api:slo:write
+     */
+    createSlo(config: {
+        body: SloConfigItemDtoImpl;
+        abortSignal?: AbortSignal;
+    }): Promise<void>;
+    /**
+     * Gets parameters and calculated values of a specific SLO
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + environment-api:slo:read
+     * <br/><br/>If **from** and **to** parameters are provided, the SLO is calculated for that timeframe; otherwise the SLO's own timeframe is used.
+     * @returns Success. The response contains the parameters and calculated values of the requested SLO.
+     */
+    getSloById(config: {
+        /** The ID of the required SLO. */ id: string;
+        /**
+         * The start of the requested timeframe.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * If not set, the relative timeframe of two weeks is used (`now-2w`).
+         */ from?: string;
+        /**
+         * The end of the requested timeframe.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * If not set, the current timestamp is used.
+         */ to?: string;
+        /**
+         * The timeframe to calculate the SLO values:
+         *
+         * * `CURRENT`: SLO's own timeframe.
+         * * `GTF`: timeframe specified by **from** and **to** parameters.
+         *
+         * If not set, the `CURRENT` value is used.
+         */ timeFrame?: GetSloByIdQueryTimeFrame;
+        abortSignal?: AbortSignal;
+    }): Promise<SLO>;
+    /**
+     * Updates an existing SLO
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + environment-api:slo:write
+     */
+    updateSloById(config: {
+        body: SloConfigItemDtoImpl;
+        /** The ID of the required SLO. */ id: string;
+        abortSignal?: AbortSignal;
+    }): Promise<void>;
+    /**
+     * Deletes an SLO
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + environment-api:slo:write
+     */
+    deleteSlo(config: {
+        id: string;
+        abortSignal?: AbortSignal;
+    }): Promise<void>;
+}
+export declare const serviceLevelObjectivesClient: ServiceLevelObjectivesClient;