Skip to content

Browse state and watch live events

Goal: look up what is in the context's state store (configuration, scenarios, books, saved worker state), and watch the CloudEvents on chosen topics as they arrive.

Prerequisites

  • Signed in (any user: both views only read).
  • The context is active. The States view needs a state store with Dapr Query API support.

Steps: state

  1. Open Infra > States (route /infra/states). The table lists the store's keys (Key, Value preview, ETag), up to 1000, updated on state-change events.
  2. Filter, e.g. name:cfg.scenario.* (a glob over the key), value:BTC_USDT, or a word. Escape clears the filter.
  3. Tree: press Tree to see the keys as a name tree by their dot-separated segments (cfg › scenario › …) with counts; ▸/▾ open and close; click a segment to show only the keys under it (under cfg.scenario, all to go back). Flat returns to the table.
  4. Open a key: select it and press Open (or Enter). The dialog shows its etag, Value (pretty-printed JSON) and Stream (each value read while the dialog was shown, newest first).

Steps: live events

  1. Open Infra > Events (route /infra/events).
  2. Topics… The dialog Topics to follow lists the topics the api has seen, most recently published first. Search, tick the ones you want, or type a topic it has not seen and press Add. Follow.
  3. Watch the table: Time (UTC), Topic, Type, Source, Data; ● live once the subscription is up; N received. The newest 500 events are kept.
  4. Pause to read in peace (events keep arriving: paused, N waiting); Resume. Clear empties the list.
  5. Filter with the value filter (name:act.*, type:…, value:…), or Tree for the topic name tree.
  6. Open (or Enter) an event for its attributes (type, source, id, time, subject) and data.

The followed topics are remembered in this browser, per context.

What you should see

  • States: the key count, the first 1000 keys only when there are more; values change as workers save.
  • Events: rows arriving at the top while ● live.

Troubleshooting

Symptom Cause and fix
States: a red stale since … / failed line The store could not be read (e.g. no Query API support): the last list stays shown.
A key you expect is missing Only the first 1000 keys are read: filter does not widen that. Use a script (vf.state.get({ key })) for one key.
Events: ○ connecting… stays The subscription is not live: the api is down (see the context dot) or refuses; it is reopened with backoff.
Events: Follow some topics: Topics… No topics are followed on this context yet.
A topic you expect is not in the picker The api has not seen it published yet: type it and Add.

More: Views > States, Views > Events.