Skip to main content
MKA1 publishes service level objectives (SLOs) for the API services below. After each month ends, your organization gets a report showing whether each service it used met its objectives.

​
Objectives

Services that stream output or run long jobs have no latency objective. Their request duration reflects the work you asked for, not how responsive the service is.

​
How service levels are measured

Every request through the MKA1 API gateway is recorded with its organization, service, status code, and duration.
  • Availability is the share of your organization’s requests to a service that did not get a 5xx server error. Client errors such as 400, 401, and 429 count as available.
  • p95 latency is the 95th-percentile request duration measured at the gateway, from receiving the request to sending the last byte of the response.
  • Months are calendar months in UTC. A report is generated about an hour after the month ends.
  • A report covers only the services above that your organization called that month. If your organization made no requests to them, there is no report for that month. Requests that are not tied to an organization are excluded.
The targets that applied when a report was generated are stored with it, so a later change to an objective does not alter past reports.

​
View your monthly report

Organization owners and admins can view their organization’s reports in the console:
  1. Open Audit.
  2. Select the Service levels tab.
  3. Choose a month. Each service shows its request count, measured availability and p95 latency, the target for each, and whether it was met or missed.
  4. Click Download CSV to export the month’s report.
Cluster admins choose an organization from the organization selector first. Reports are per organization, so the all-organizations view has none.