Skip to content

Campaigns

Luke Switzer edited this page Oct 26, 2026 · 1 revision

A campaign tags everything the node logs between a start and a stop with a name, so you can pull one site's or one day's data back out later.

How it works

When you start a campaign, every log line the node writes carries the campaign name until you stop it. This lets you keep one survey's results separate from another's on the same card.

Start

  • Web UI: Data tab.
  • Over mesh: @ALL CAMPAIGN_START:site-a starts a campaign named site-a. @ALL CAMPAIGN_STOP ends it. @ALL CAMPAIGN_STATUS reports whether one is running.

Getting the data

Export the campaign's logs from the Data tab. Each record from the campaign window carries the name you set, so you can filter by it.

If records are not tagged

A campaign tags only the records written while it is running. Start the campaign before the scan, and confirm it is running with CAMPAIGN_STATUS. Records written before the start or after the stop are not tagged.

Clone this wiki locally