Penstock

Guide / Test and run

Heat map and replay

Paint a diagram by how often, how long and how badly each element ran on the engine, step through a real instance with its variables, and start a new one from a chosen token. Both are read from the engine you already connected.

Pro A deployment profile with an address. Replay and what-if start only on an engine marked deployment.forTests.

Heat map and bottlenecks

Pro heatmap

  1. Open the Monitor tab. See Monitor.
  2. Choose a period: the last hour, day, week or 30 days.
  3. The diagram is painted by how often, how long and how badly each element ran. A badge and a tooltip show the visits, the average and 95th percentile duration, the incidents and the failure rate.
  4. The slowest and most failing lists name elements. A click selects the element on the canvas.

It is read-only. It asks the Camunda 7 history REST API, or the Camunda 8 element-instance and incident search, of the connection you already chose, and nothing else. Every read is capped in pages, rows, bytes and time. An answer that is too large, malformed or cut short is shown as partial instead of as a number. The percentile and the rates are computed in Penstock from the rows, never taken from the engine's text.

Replay a real instance

Pro replay

Under the instance list of the History section, press Replay this instance. Penstock steps through what the engine recorded, one element at a time, on the diagram, with the variables at each step. Changed names are marked, and values that look like secrets are shown as <redacted>.

The variables are what the history says on Camunda 7. On Camunda 8 they are the values the instance has now, and the panel says which. The free stepping of the Timeline stays as it is.

What if from this token

Press What if from this token to start a new instance at the chosen element with the variables you edited. It uses the same start call as the debug and scenario runs.

Only on a test engine

It starts only on an engine marked deployment.forTests. On a local engine on this machine it asks first. A production connection is refused, with the reason, before anything is sent. A variable that is still <redacted> stops the start: type its value first. See Security and privacy.

Common problems

The heat map says partial.
The engine's answer was too large, malformed or cut short, or hit a cap. Choose a shorter period.
What if is refused.
The connection is not marked deployment.forTests: true. Use a test engine. See Deployment.
The replay variables are the current ones.
On Camunda 8 the engine gives the values the instance has now, not the value at each step. The panel says so.