Events flag conditions that need attention; logs preserve timestamped output explaining what happened. ARGUS manages and records both. Open Events or Logs in the left sidebar, or use their Node Board views beside your main tab.

Events

Plugins and automation report events such as a disconnected device or high pressure. Use the Interface to investigate the condition and respond. Engine Events and Logs explains how events are produced and handled.

Viewing Events

Open Events in the left sidebar to see live events and recorded history. Select an event to inspect its details and available actions.

Use Search events and the filter menu to narrow by severity, type, node, system, subsystem, or status.

Choose Calendar → Calendar or Session, select the period, and Apply. The blue dots represent days on which recorded content exists, and the blue outlined section represents the current range that is loaded.

White sections select start and end days with the grey highlighting days in between, and the light grey highlighted day represents the current day.

Click an event and scroll its details to read the description, resolution, origins, and graphs. Use its actions to acknowledge or resolve it, answer a prompt, or release a hold. Select several events for bulk actions.

Open Node Board near the bottom of the sidebar to keep events beside your main tab; the activity bar also opens aborts, holds, and prompts. See Node Activity.

For saved occurrences and responses, open Data → Databases → ARGUS Events and set its range and filters. You can review history while events remain active. See Historical Queries.

Event Metadata

These details identify the condition and help you investigate. Availability depends on its producer and recorded history; see Event Metadata for exact behavior.

Clicking an event shows its Info Panel on the right, which these metadata fields can be viewed in.

The Event Info Panel contains useful information used to react to the event, who may have reacted to the event, or figure out where it came from and what limits may have triggered it.

Types

The type tells you why an event needs attention.

States

Handling and firing are separate: acknowledging high pressure does not stop the pressure condition. See Event States for lifecycle details.

New active and Acknowledged active indicate firing. Firing unknown means the owner’s current state is unavailable. Observed is a resolved observation record.

Actions

Available controls depend on type, state, and permissions. They do not themselves prove equipment recovery; see Event Actions.

It is best practice to Acknowledge an event once you have read it. Once you diagnose it and resolve the issue, (and it has stopped firing), you can resolve it to remove it from the board.

Never acknowledge an Event without really knowing what triggered it or what the severity may be. You could forget about the occurrence, and that could mean the difference between hardware working when it needs to, and when it does not.

Silencing an event will prevent it from showing up on the board. You can go to the Events resource to unsilence it.

Export Events

You may want to export events for further analysis outside of DARTWIC. You can export events from the Events resource, the Events Node Board, or the Events Database in the Data Resource.

Export ranges available are chosen from the selected ranges in the Calendar Picker. Configure your range, then click the Export button adjacent to it, and select a range to start the export.

Selected range, Loaded range, and Visible range, with the same bounds shown in the calendar’s information popup are offered.

A live or unavailable range cannot be exported until it has concrete bounds. Each choice exports matching recorded events and occurrences as .jsonl, including results not loaded into the preview. See Export Formats.

On the Node Board, Selected events exports selected items as shown, and Current board captures all matching events, including those outside the scroll viewport. Use a calendar range export for recorded occurrence history.

To include channel samples, use a paused graph’s telemetry export or export a dataframe.

Logs

Logs help investigate startup, device errors, and script progress. A stream groups output by source; a session identifies one Engine run. Open Logs to follow incoming output or inspect earlier messages. Write Logs covers producing output from plugins and automation.

Viewing Logs

Open Logs in the left sidebar and choose an output stream, such as the Engine or a device plugin.

Select a stream, then use Search logs and filters to find the relevant output. The stream list shows unread warning/error icons; its filter can limit the list to streams needing attention.

Use Calendar → Calendar or Session and Apply to inspect an earlier period. The blue dots represent days on which recorded content exists, and the blue outlined section represents the current range that is loaded.

White sections select start and end days with the grey highlighting days in between, and the light grey highlighted day represents the current day.

To watch a driver’s output while configuring its module or starting a task, keep its logs open in Node Board.

Log Metadata

Each record identifies the message, its source, and timing. See Log Metadata for the stored format.

Info gives context, Warning flags a problem, and Error reports a failure. Logs have no acknowledgement or resolution states. Live follows incoming output; Recorded only reads saved history.

Export Logs

You may want to export logs for further analysis outside of DARTWIC. You can export logs from the Logs resource, the Logs Node Board, or the Logs Database in the Data Resource.

Export ranges available are chosen from the selected ranges in the Calendar Picker. Configure your range, then click the Export button adjacent to it, and select a range to start the export.

Selected range, Loaded range, and Visible range, with the same bounds shown in the calendar’s information popup are offered.

Each choice exports matching recorded output as .jsonl, including results not loaded into the preview. See Export Formats.

You can export while the Engine is running. Keep the view and connection open until completion; Cancel export stops remaining work. To include channels, use a paused graph’s visible-range export.