Docs

Glossary

Every word Sypnia uses with a fixed meaning, defined in one or two sentences, with the name it has in the API and in Spanish.

Applies to EngineCloud At launch

View as Markdown
On this page
  1. The terms
  2. The same words in Spanish
  3. Names in code

This page is for anyone who meets a word in these docs and wants its exact meaning. The vocabulary is the same for the open-source engine Engine and for Sypnia Cloud Cloud; a definition says so when a thing exists in only one of them.

Sypnia uses one name per thing, everywhere: in these docs, in the app, in the API and in what the agent writes. Three choices are worth knowing before you read the list:

  • A group of failures with one cause is a problem. Sypnia never says «issue».
  • The agent is Sypnia’s own analysis. The tool that writes code for you, such as Cursor or Claude Code, is your coding agent.
  • The engine is the open-source part, and Sypnia Cloud is the paid service that runs it for you.

Wherever a word of this list appears underlined in a page, pointing at it shows its definition and following it brings you here.

The terms

Account
The team or company a person belongs to in your app. Your app sends it with identify(). It is not a Sypnia account.
The agent
Sypnia's analysis. It reads a problem and writes, in plain words, what happened, who it hit, since when, the likely cause and what to do. It is not your coding agent.
API token
A secret key that starts with sps_. It reads data through the API and the MCP server, within its scopes, read, replay and admin.
Sypnia Cloud
The paid service, with a free tier. It is the same engine, run by us, plus accounts, billing, the full app and the GitHub App.
Console
The one page built into the engine. It shows the problems list and the session replay viewer.
Dead click
A click on something that looks like it should do something, after which nothing happens.
Sypnia engine
The open-source part of Sypnia, one program that receives, stores and analyses your data. You can run it yourself for free.
Environment
Where a build of your app runs, such as production or development. Each event carries its environment, so you can tell real customers from your own testing.
Event
One thing your app reported to Sypnia, such as an error, a slow request, a click or a performance measurement.
Fix
What Sypnia hands to your coding agent for a problem. It comes three ways, a ready prompt, the MCP server and a pull request (Sypnia Cloud).
Ingest key
A public, write-only key that starts with spk_. Your app uses it to send events. It is safe to ship in a browser.
Mark
What Sypnia adds to an open problem on its own. There are three, «new» in its first 24 hours, «growing» when it reaches twice the people of its last alert and at least 5, and «came back» when it was resolved and happened again.
Outage
The time your app did not answer an uptime check. It opens after two failures in a row and closes at the first success.
Page snapshot
A copy of a page's structure, taken by the browser SDK with the same masking as a replay. Click maps are drawn over it.
Person
Someone using your app. A person has an id and, only if your app sends them with identify(), a name and an e-mail. A session with no person is anonymous.
Problem
A group of failures with one cause, told in one sentence. Sypnia says «problem», never «issue».
Project
One app that Sypnia watches. Every event, session and problem belongs to exactly one project, and nothing is shared between projects.
Rage click
A burst of three or more clicks on the same spot within one second. It tells you a person was stuck, even when no error was thrown.
Release
One version of your app that you shipped. Sypnia uses it to say since when a problem happens and what changed.
Replay
The recording of a session, played back as the person saw it. Typed input and masked fields are never recorded.
Root token
The first token of a self-hosted engine. You set it in the environment when you install, and use it to create projects and other tokens.
Session
One visit by one person, from the first page to the last, with every event that happened in between.
Span
One step of a trace, such as a request, a function or a database call, with its start, its duration and whether it failed.
Trace
The path of one request across your app, from the browser to the API to the database calls, with how long each step took.

The same words in Spanish

The Spanish docs use one fixed translation for each term, and keep some words in English because developers use them that way.

EnglishSpanish
problemproblema
sessionsesión
replaygrabación
tracetraza
eventevento
releaseversión (release)
environmententorno
projectproyecto
the agentel agente
enginemotor
the Consolela Consola
self-hostingalojamiento propio
ingest keyllave de ingesta
API tokentoken de API
rage click, dead clickclic de rabia, clic muerto
uptimedisponibilidad
alert, daily summaryalerta, resumen diario
masking, samplingenmascarado, muestreo
Kept in Englishspan, pull request, prompt, webhook, source maps, skill, MCP, SDK, CLI, Sypnia Cloud

Names in code

In the API, the events and the settings, the same things have short fixed names. The full list of event fields is in the event schema.

ThingIn the API and the CLILooks like
Projectproject, an id or a slugprj_5k2m9x4q7w1z, shop
Problemproblem, an id or a slugprb_8f3k2m9x4q7w, pay-button-does-nothing
Sessionsession, 32 hex characters chosen by the SDK8f3a6c1e9b2d4f07a5c3e1b8d6f4a2c0
Tracetrace_id, a W3C trace id7c2e9a4b1d8f4e6a9b3c5d7e1f2a4b6c
Releaseversion, the string your app sends as release4f2a91c
Ingest keyThe key itself, and its recordspk_…, key_…
API tokenThe token itself, and its recordsps_…, tok_…
Alert, uptime check, webhookTheir idsalt_…, chk_…, whk_…

Sections

Start hereWhat Sypnia is, how it works, what is open source and what is the paid cloud, and the two ways to get your first problem in plain words.ConceptsThe ten ideas Sypnia is made of, each defined precisely, from a project and its keys to problems, traces and alerts.SDKsHow your app sends data to Sypnia. One SDK for the browser, one for Node, one for Next.js, and the OpenTelemetry intake for every other backend.The agentHow Sypnia analyses a problem, what it writes, what it sends to a model and what it never does.MCP and skillsConnect your coding agent to Sypnia so it can ask what is failing in production, read what it needs to fix it, and set Sypnia up for you.API referenceThe Sypnia HTTP API: one API for the open-source engine and for Sypnia Cloud, with every endpoint, parameter, response and error.CLI referenceThe sypnia command: how to install it, the variables it reads, what its exit codes mean, and where each command is documented.Self-hostingWhat you run when you host the Sypnia engine yourself, what you need, what it costs, and what you do not get compared with Sypnia Cloud.How the engine is builtThe whole Sypnia engine on one page, from a click in your app to the sentence your coding agent reads, with the design rules and the code that holds them.Sypnia CloudHow the paid service works, from organizations and roles to plans, limits, billing, where your data lives, the GitHub App and support.Privacy and securityWhat Sypnia collects from your app and its users, what it never collects, how masking works, how to delete data, and how the service is protected.LicensingWhich licence covers each part of Sypnia, what you may do with it, how the name may be used, and the terms of a contribution.GuidesStep-by-step recipes for the common ways to use Sypnia, from apps made with AI builders and Next.js on Vercel to Supabase, source maps in CI, alert e-mails from your own engine, and moving from Sentry.ReferenceThe pages you look things up in, from the event schema and the glossary to what is planned, the changelog and the common questions.
↑↓ to move↵ to openEsc to close