Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

ServiceLevelObjective

import type { ServiceLevelObjective } from "https://googleapis.deno.dev/v1/monitoring:v3.ts";

A Service-Level Objective (SLO) describes a level of desired good service. It consists of a service-level indicator (SLI), a performance goal, and a period over which the objective is to be evaluated against that goal. The SLO can use SLIs defined in a number of different manners. Typical SLOs might include "99% of requests in each rolling week have latency below 200 milliseconds" or "99.5% of requests in each calendar month return successfully."

interface ServiceLevelObjective {
calendarPeriod?:
| "CALENDAR_PERIOD_UNSPECIFIED"
| "DAY"
| "WEEK"
| "FORTNIGHT"
| "MONTH"
| "QUARTER"
| "HALF"
| "YEAR";
displayName?: string;
goal?: number;
name?: string;
rollingPeriod?: number;
serviceLevelIndicator?: ServiceLevelIndicator;
userLabels?: {
[key: string]: string;
}
;
}

§Properties

§
calendarPeriod?: "CALENDAR_PERIOD_UNSPECIFIED" | "DAY" | "WEEK" | "FORTNIGHT" | "MONTH" | "QUARTER" | "HALF" | "YEAR"
[src]

A calendar period, semantically "since the start of the current ". At this time, only DAY, WEEK, FORTNIGHT, and MONTH are supported.

§
displayName?: string
[src]

Name used for UI elements listing this SLO.

§
goal?: number
[src]

The fraction of service that must be good in order for this objective to be met. 0 < goal <= 0.9999.

§
name?: string
[src]

Identifier. Resource name for this ServiceLevelObjective. The format is: projects/[PROJECT_ID_OR_NUMBER]/services/[SERVICE_ID]/serviceLevelObjectives/[SLO_NAME]

§
rollingPeriod?: number
[src]

A rolling time period, semantically "in the past ". Must be an integer multiple of 1 day no larger than 30 days.

§
serviceLevelIndicator?: ServiceLevelIndicator
[src]

The definition of good service, used to measure and calculate the quality of the Service's performance with respect to a single aspect of service quality.

§
userLabels?: {
[key: string]: string;
}
[src]

Labels which have been used to annotate the service-level objective. Label keys must start with a letter. Label keys and values may contain lowercase letters, numbers, underscores, and dashes. Label keys and values have a maximum length of 63 characters, and must be less than 128 bytes in size. Up to 64 label entries may be stored. For labels which do not have a semantic value, the empty string may be supplied for the label value.