Concepts
The ten ideas Sypnia is made of, each defined precisely, from a project and its keys to problems, traces and alerts.
This section defines how Sypnia behaves. Read it when you want to know exactly what a word means or what a number counts: what starts a session, what makes two failures the same problem, what a rage click is, when an alert is sent.
Every page applies to the open-source engine and to Sypnia Cloud, and says where they differ. The examples all come from one small shop with a checkout.
-
Projects, environments, keys and tokens
Where data belongs and what each key can do. - What your app reports, and which events count towards a plan.
- What starts and ends a session, and what a replay records.
- What makes failures one problem, and when it is new, growing, resolved or back.
- One request followed from the browser to your API and the calls behind it.
- Page speed and API speed, how percentiles are shown, and the element behind each number.
- The exact rules for both, and what does not count.
- What a check does, when your app counts as down, and when you are told.
- How Sypnia knows which change broke it, and shows your real code.
- What triggers an alert, what it contains, and what waits for the morning.