Tiers and SLA reports

https://docs.evohub.io/mcp

claude mcp add --transport http evohub-docs https://docs.evohub.io/mcp

{
  "mcpServers": {
    "evohub-docs": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://docs.evohub.io/mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "evohub-docs": {
      "url": "https://docs.evohub.io/mcp"
    }
  }
}

{
  "servers": {
    "evohub-docs": {
      "type": "http",
      "url": "https://docs.evohub.io/mcp"
    }
  }
}

A tier says how critical a service is and what that promises. Catalog measures each service against its targets every month, from the Uptime monitors and On-Call integrations that watch it.

#Tiers

Tiers are your organization's own. Open Catalog → Settings → Tiers and SLAs. A new organization starts with Tier 1 to Tier 4; the first tier is the most critical.

Select Add a tier to add one. Each tier has a Name, a description of what belongs in it (for example "Anything a customer sees or pays through"), a Colour, and its targets:

Every target is optional. Use the arrows to make a tier More critical or Less critical; a service's tier number follows the order.

Changing a tier's name, description or targets makes a new version of it. Versions are kept, so a past month's SLA report reads the targets that applied then; Every version of this tier lists them. Changing only the colour is not a new version.

A tier is never deleted. Archive takes it out of use: it can no longer be chosen, and the services already in it keep it. An organization can have up to 50 tiers in use.

#A service's SLA

Choose a service's Tier on its page. The service takes the tier's targets, and its SLA section can change any of them for itself: empty fields take the tier's value, shown greyed, and the targets the service changes are marked. A service with no tier has only its own targets.

#Responsibilities

The owner team answers for a service. If you need more, add a RACI under Responsibilities on the service's page with Add a RACI. Each line is a role and a team or a person:

A RACI is optional, saved as a whole, and must have exactly one Accountable line. It can have up to 50 lines.

#The SLA report

Each service's page has an SLA report for each of the last twelve calendar months, in UTC. The current month is measured up to now.

To be measured, a service needs what watches it to be tied to it: set the Catalog service field on its Uptime monitors and on its On-Call integrations.

• Availability is summed over the Uptime monitors tied to the service, with each monitor's checks, and compared with the availability target.
• Response and resolution come from the On-Call alerts raised by the integrations and monitors tied to the service, per severity: how many alerts, how many were acknowledged and resolved, the median and 90th percentile times, and how many breached the targets.

Each part shows Met or Missed against its target. A part that has nothing to measure, or cannot be read at the moment, says so without failing the rest of the report.

The targets used are the service's tier as it read at the end of the month, with the service's own changes over it.

#Permissions

Reading tiers and SLA reports needs catalog:component:read. Creating, editing, reordering and archiving tiers, changing a service's targets and setting its RACI need catalog:component:write, which Members hold by default. See Catalog permissions.

#Related

• Catalog overview
• Uptime monitoring
• Alerts and incidents