Start here

upzero is an observability platform. Your apps, and the uptime monitors you create, send it data, it works out what that data means, and your team acts on what it finds. Everything the product does falls into one of five groups. Knowing them makes the rest of these docs easier to place.

The five groups

Signals are the raw data: logs, traces and metrics, including the results of uptime checks. Nothing here is ever edited. A signal is written once and ages out after your retention window.

Correlation is what upzero computes from signals without you asking: which error messages are really the same error, which services call which other services, how a slow request maps to a trace. This is recalculated continuously and there is nothing to manage by hand.

Operational objects are the things a person on your team works on: an issue (a recurring error class), an alert (a rule's condition is currently true), an incident (your team coordinating a response), and an objective (a reliability target you set). These have a status and someone owns them.

Subjects are the things being observed: a service, a monitor, a deployment, an environment. Some are discovered automatically from the data your apps send; a monitor is one you create yourself.

People and access covers who is on your team, which organization they belong to, and what they are allowed to do.

Signals feed correlation, correlation is what turns into an issue or an incident, and every signal, pattern and object is about a subject that someone on your team owns.

Now: create your account, install the CLI, send your first signal, create your first monitor, and meet your first issue.