Skip to main content
Activity log monitoring captures application events from BRICKS Foundation devices and uploads them to a cloud-based time-series database. Use it to analyze device behavior, track user interactions, and monitor application health over time.
Activity log monitoring is available on Business plan workspaces.

​
Enable logging

Enable activity log on a device from BRICKS Controller:
  1. Open the device detail page
  2. Go to Settings > Activity Log
  3. Toggle Enabled on
You can also enable logging for all devices in a group by deploying activity log settings from the Device Group tab.

​
Event ID filter

Use the Event ID Filter field to set a regex pattern that controls which events are logged. Only events with IDs matching the pattern are captured. Leave empty to log all events.

​
What is logged

Each log entry contains:
FieldDescription
Event IDUnique identifier for the event type
TimestampWhen the event occurred
Event dataCustom event-specific content
Device metadataSender, subspace ID, and property details
Events are categorized by ID range:
RangeCategory
0–999System events (BRICKS Foundation)
1000–1999Brick events (UI interactions)
2000–3999Generator events (I/O and data)

​
How it works

Events are captured on the device, cached locally, and uploaded in batches to the activity log server at regular intervals (default: every 2 minutes). You can also trigger an immediate upload from the device control panel in BRICKS Controller.

​
Device control actions

From the device detail page in BRICKS Controller:
  • Temporary enable Fast Mode (10min) — Switches to high-frequency logging for short-term debugging
  • Upload logs now — Triggers an immediate upload of cached events

​
Query logs

Activity logs are stored in a Prometheus-compatible database and queried via the Prometheus API.
1

Create a query token

In BRICKS Controller, go to Workspace Settings and create a workspace token with the query_activity_log permission type.
2

Get the query endpoint

Open the Query Activity Log guide in workspace settings to view your query endpoint URL and workspace ID.
3

Query the API

Use the Prometheus API to query your logs:
curl -u <workspace-id>:<token> \
  https://activity-log.bricks.tools/api/v1/label/__name__/values | jq

​
Use cases

  • User behavior analysis — Track how users interact with bricks and navigate canvases
  • Troubleshooting — Investigate what happened before an error or unexpected behavior
  • Fleet monitoring — Monitor event patterns across multiple deployed devices
  • Performance tracking — Analyze generator response times and event frequency

​
Next steps

Debug panel

Inspect runtime state in real time on the device.

Automations

Run end-to-end automation tests on devices.