QuorumWiki
Jugar
Tutoriales

Gana Conocimiento e investiga

Mira cómo Analítica convierte tu tráfico en Conocimiento y haz tus primeros Estudios, Stripe Billing y Logs estructurados.

In this lesson you find where Insight comes from and spend it on two Studies: Stripe Billing, which collects revenue for you, and Structured logs, which shows why a request failed. Both run in the Garage or in Pre-seed.

Find your Insight#

Insight is what you learn from watching your own traffic. Analytics samples the Nodes that link into it, and each sampled request kind fills its own Insight pool.

  1. Look at the Analytics card on the board. It shows Sampling, Kept, and up to three rows with a pool icon and a rate, such as +0.4/s.

  2. Look under the HUD, at the top left. The Insight card lists each pool that you hold or earn, with its amount and its rate.

The Insight card appears as soon as your pools hold enough for the cheapest Research item. In a new Company, that happens within about a minute.

Each pool has its own icon and color. The color matches the request kind's particles on the board, so page-view Insight looks like page-view traffic.

AnalíticaOpenTelemetryEnlaza cualquier nodo con ella. Muestrea ese tráfico y lo convierte en Conocimiento.

Read the help#

  1. Select the ? button on the Insight card. About Insight opens.

  2. Read the four parts: Pools, Earn, Spend, and Keep.

  3. Press Esc to close it.

Two rules matter most. A pool earns with the square root of its samples, so a new request kind earns more than more of the same traffic, and it stops filling at its rate times the Analytics retention window. Spend Insight rather than hoard it.

Open Research#

  1. Press R. You can also select the top row of the Insight card. The Research screen opens.

  2. Look at the tree. Each track grows up from its root, through one band per Era. Items in later Eras are greyed or faded.

Each item shows its cost as chips, one chip per pool that pays for it. The pools that pay are the item's recipe. Most Garage items cost page and read Insight. Most Pre-seed items cost write and login Insight.

Run your first Study#

  1. Click Stripe Billing in the tree. Its detail panel opens at the bottom right.

  2. Read the blurb: Payments collect themselves.

  3. Read the Cost rows. Each row shows the pool, the cost, and how much you hold.

  4. Select Start Study. The button also shows how long the Study takes.

A Study does not take all its Insight at once. It takes Insight from its pools while it runs, so the pools fall slowly. The pool that runs low first sets the pace.

  1. Press Esc to close the Research screen.

  2. Watch the Insight card. Its top row shows Stripe Billing and a percentage, with a progress bar.

When the Study ends, look at the Payments card. Its button now reads Collected automatically, and revenue goes straight to Cash. Pressing C is optional.

Queue a second Study#

  1. Press R again.

  2. Click Structured logs, in the Observability track.

  3. Select Start Study.

If a Study already runs, the new one joins the Queue in the detail panel. The first Study in the queue runs, and the others wait. You can move a Study up or down, or cancel it. A cancelled Study loses its progress and the Insight it took.

You can also double-click an item in the tree to queue it.

  1. Logs estructurados
  2. Métricas
  3. Percentiles
  4. Alertas
  5. Trazado distribuido
  6. Búsqueda de trazas
  7. Notebooks
  8. Cuadros de mando de SLO
  9. Profiling continuo
  10. Muestreo de cola
  11. Monitorización de usuarios reales
  12. Detección de anomalías

See what logs show#

When Structured logs is yours, errors have causes.

  1. Wait until the Errors row shows on the HUD. It appears when the first request fails.

  2. Hold the pointer over the Errors row. Its title lists each cause and its rate.

  3. Select the Users Node. The Inspector shows Errors by cause.

Causes such as stranded and down tell you what to fix. Without logs, you see only that requests fail.

When a pool runs short#

In Pre-seed, some items cost write and login Insight, and login arrives at a small share of the mix. A Study on one of those runs at login's pace.

  1. Press R and click the item that runs now.

  2. Look under the login cost row. The card says your Login Insight is too low, and it gives both rates: what login earns a second and what the Study needs. Its button names the step and its Dev Hours, and under the title it shows what that step reaches and what it costs in user growth.

  3. Select Build. The step joins the Team backlog, and a Team spends the Dev Hours on it.

  4. Press Esc, then T, and watch the item reach Shipping. When its deploy lands, the kind's share rises and its pool earns faster. The running Study picks up speed.

A step also takes a little off user growth and loads the Nodes that serve the kind, so a login lever shows up on the App Servers. Start with the pool the card names, not the busiest pool on the board.

Earn Insight faster#

  • Link more Nodes into Analytics. Drag from a Node's blue output port to the Analytics card. The Database is a good first choice.

  • Serve new request kinds. Each new kind fills a pool of its own.

  • Select More samples in the Analytics Inspector to sample a larger share of the traffic. Sampling costs a little CPU on each Node that it samples.

With logs, an error carries a cause, and the cause usually names the Node to fix next. Find the bottleneck covers that walk, and Insight and observability is where the pools come from.